Data page rules - Using the Load Management tab

This tab provides several controls for managing instances of this data page on the clipboard.

Note: Load management controls are displayed for read-only pages only. For editable data pages, the only option displayed is Clear Data Page.

Page management

Click Clear Data Page to remove from the clipboard all instances of this data page.

If the page is parameterized, you have an option to delete all instances or only those with specific parameter values.

Load management

This section is displayed for node level data pages. When a node level data page is loaded, a new requestor is created to load the data page. The access group of the requestor determines the ruleset to use and the security context for rule resolution during the load.

In the Access Group field, enter the access group of the requestor to use to load the data page.

For more information, see Data pages - Understanding the access group field on Pega Community.

Refresh strategy

The connector, report definition, or other load mechanism executes the first time any requestor within the scope references the read-only data page (such as to access the value of a property, or to test whether a property is present).

Note: A system-wide refresh can take up to five minutes.
Field Description
Reload once per interaction This option is available only for data pages with a scope of Thread or Requestor.

Select the check box to cause the Pega Platform to refresh the page exactly once per user interaction. When selected, the system ignores any values in the Reload if older than and Do not reload when fields at run time .

Note: For Repeat Grids that have Reload once per interaction enabled, and that also use data pages as sources, the sorting order is lost when the Refresh List action is triggered.
Do not reload when Optional: Identify the when rule to be evaluated when a requestor accesses a page with a scope of Thread or Requestor.

If the when rule evaluates to false, the page contents are refreshed, but never more than once per user interaction.

Reload if older than Optional: Enter the amount of time in days, hours, minutes, and seconds, after which the data page is considered expired. The timer starts when the page is first loaded, not from the time of last access.

The data page is refreshed only when another access request is made after the expiration time, and is never refreshed more than once per user interaction.

For example, assume a reload time of ten minutes:

  • The data page is accessed for the first time at 1200. The data page is loaded because this is the first access.
  • The data page is accessed for the second time at 1208. The data page is not loaded. The existing copy is returned.
  • The data page is accessed for the third time at 1211. The data page is reloaded because the time from the last reload at 1200 exceeds the Reload if older than setting of ten minutes.
Restricted feature set for high throughput Optional. By default, the complete feature set for high-speed read-only data pages is implemented on the clipboard. Select this option to use a restricted feature set when high-speed read-only data pages are impacting system performance.

For more information about the unsupported features, see High-speed data page support on Pega Community.

Page limits

For read-only data pages with a scope of Requestor or Node, select the Clear pages after non-use check box to force the system to delete the clipboard instances of the data page after an interval passes with no access. Subsequent attempts by a requestor to access the data pages cause the pages to reload. This setting does not apply to editable data pages.

When selected, this setting has different effects depending on the scope of the data page:

  • Requestor scope – The data page instance that is created when any thread refers to the data page is removed when there are no more threads referring to it.
  • Node scope – The system checks the Reload if older than fields on the Load Management tab of the data page rule. If the fields are blank, the system uses the value of the Dynamic System Setting DeclarePages/DefaultIdleTimeSeconds, which is set by default to 86400 seconds, or one day.
Note: Read-only data pages are never passivated. If a requestor or thread is idle and gets passivated, all read-only data pages in that requestor or thread are cleared and reloaded the next time they are referenced, whether or not Clear pages after non-use is selected.