Declare Pages form
Completing the Definition tab

Field

Description

Select to determine the scope of requestors that can access the declarative pages created by this rule:

• Node — Any requestor executing on the current node can access the pages.
• Thread — The page is created in a single requestor Thread, and can be accessed as often as needed by processing in that Thread. Accesses by separate requestors cause the rule to create distinct pages, which may have different contents.

Select the class of the top level page to be created. In most cases, select Code-Pega-List.

Identify the Activity Name key part of an activity that the system uses to create and update (refresh) declarative pages. At runtime, the system uses the value in the Page Class field as the Applies To key part to find the activity with rule resolution.

Select an activity that has LoadDeclarativePage as the Activity Type (on the Security tab). Confirm that this activity adds property values to the page; it is not otherwise unrestricted. See More about Declare Pages rules.

If the Page Scope field is set to Node, the system uses the RuleSet list provided by the access group in the Access Group field with rule resolution to find the activity (not the RuleSet list of the requestor). If the Page Scope field is set to Thread, the system uses the RuleSet list of the requestor to find the activity.

At runtime when searching for this activity, rule resolution excludes checked-out rules in a personal RuleSet. The system selects and executes the current checked-in version.

If the activity accepts input parameters, click  Params and enter literal constant values or property references as parameter values. To reference a property value, enter the fully qualified reference, starting with a top-level page name. In addition, Include the name and class of clipboard pages you reference here on the Pages & Classes tab of this rule form.

• Page — To create a single top-level page of class Code-Pega-List, containing embedded pages — typically named pxResults(1), pxResults(2), and so on
• List — (Do not use. Reserved for future use.)

Select an access group that provides temporary access to the RuleSets and versions needed to access the load activity. This field appears only when the Page Scope is set to Node.

The requestor that executes this activity uses this access group only during execution of the activity. RuleSets made available by this access group may not be available to the requestor at other times.

The load activity executes the first time any requestor within the scope (Node or Thread) references the page (such as to access the value of a property, or to test whether a property is present).

Optionally, you can define one or two criteria that can cause the system to delete the declarative page or pages and rerun the load activity, creating them again with possibly fresher contents.

Optional. Enter positive integers in one or more of these fields to define an expiration time interval in days, hours, minutes, and seconds. If not blank, any attempt by a requestor to access the page after a period of no accesses equal to or greater than the timeout causes the system to refresh the page.

Optional. Identify the When Name key part of a when condition rule to be evaluated when a requestor accesses a page with a Page Scope of Thread.

If the when condition rule evaluates to false, the page is recomputed.

To find this rule at runtime, rule resolution uses the class in the Page Class field as the Applies To class, and the RuleSet list of the requestor. This field appears only when the Page Scope is set to Thread.