Page-Set-Messages method

Parameter

Description

Optional. Identify a page to contain the message. Use the keywords Primary for the primary page or Param for the parameter page. If you leave this blank, the system uses the step page, or the primary page if the Step Page column is blank.

Optional. Leave blank unless when the message text is displayed the output is intended to be localized based on field value rules in a language-specific RuleSet.

Identify a localization category. The default is pyMessageLabel. See About the Localization wizard.

Enter one of the following:

• A Message rule key, with no quotes. Click the pencil button () to open or create the message rule.
• A literal text string within double quotes.
• The third key part of a field value rule where @baseclass is the first key part and the Category value is the second key part, to support localization. Use this only when the Category field is not blank.

Optionally, if the Rule-Message identified uses one or more parameters, follow the name by a backslash character, the letter t, and a text value for each value.

For example, the standard Message rule named ActivityNotDefined references one parameter in its text definition:

The activity {1} is not defined.

To provide a value BouncedCheck for this parameter, enter the following as the value of the Message parameter

ActivityNotDefined\tBouncedCheck

If this activity is part of an application that will be localized to support multiple locales, always reference a message rule here. Do not enter literal text.

Avoid using a field value whose localized value contains property references. PRPC evaluates the field value is each time the page is read, not only when the message is first added to the page. Because the properties may have new values (or be removed) when the field value is re-evaluated, this can be a source of confusion or error, for example when debugging with the Clipboard tool or the Tracer.