%Message meta-HTML element
Syntax
%Message(message_set, message_num, default_msg_txt [, paramlist])where paramlist is an arbitrary-length list of parameters to be substituted in the resulting text string, in the form:
param1 [, param2]. . .Description
%Message retrieves a message from the PeopleCode Message Catalog and substitutes in the values of the parameters into the message.
The message_set and message_num parameters specify the message to retrieve from the catalog. If the message is not found in the Message Catalog, the default message provided in default_msg_txt is used. Message sets 1 through 19,999 are reserved for use by PeopleSoft applications. Message sets 20,000 through 32,767 can be used by PeopleSoft users.
The parameters listed in the optional paramlist are referenced in the message using the % character followed by an integer referencing the position of the parameter in the function call. For example, if the first and second parameters in paramlist were MONDAY and 12/5/2001, they would be inserted into the message string as %1 and %2. To include a literal percent sign in the string, use %%; %\ is used to indicate an end-of-string and terminates the string at that point, this is generally used to specify fixed-length strings with trailing blanks.
The message is obtained using the current user language code.
Note:
This function is valid for use in auxiliary style sheet files and auxiliary JavaScript files.
Parameters
| Parameter | Description |
|---|---|
|
message_set |
Specify the message set to be retrieved from the catalog. This parameter takes a number value. |
|
message_num |
Specify the message number to be retrieved from the catalog. This parameter takes a number value. |
|
default_msg_txt |
Specify the text to be displayed if the message isn't found. This parameter takes a string value. |
|
paramlist |
Specify values to be substituted into the message. |
Note:
If the message is changed (or a new language version is added) after the auxiliary file has been loaded to the web server, the auxiliary file still contains the old version of the message. It is necessary to manually delete the file from the web server cache directory to get it to re-retrieve the (unmodified) auxiliary component with the (modified) message bindings.
Related Topics