Back Forward Declare Pages form
Completing the Advanced tab

About Declare Trigger rules

Use this tab to allow two additional ways to refresh or delete the declarative page.

Field

Description

Allow external expiration requests?

Select to allow a function call to mark the declarative pages created by this rule as expired, so that the load activity is called the next time a requestor attempts to access them.

If selected, other parts of your application can call the standard function @ExpireDeclarativePage(tools, PageName) to mark a page as expired.

Allow idle timeout?

Select to force the system to delete the declarative page after an interval or at least 24 hours passes with no access. Subsequent attempts by a requestor to access the declarative pages cause a Java exception, noted in the Pega log.

If cleared, declarative pages of scope Node remain until the system is shut down on that node.

This check box affects only pages of scope Node, and only if the Refresh if Older Than field on the Definition tab is blank. Declarative pages of scope Thread remain until the requestor session that created them ends.

You can specify a longer or shorter timeout period in the Refresh if Older Than field on the Definition tab.

You can change the timeout period to a different period by adding a setting to the prconfig.xml file in the following format:

<env name="DeclarePages/DefaultIdleTimeSeconds" value="nnnnn" />

where nnnnn is in seconds.

Administration  
Flush Page

As a debugging aid, click to mark the declarative page produced by this rule as style. The page is recreated whenever it is next accessed.

NoteIf this rule defines a Node scope page, clicking Flush Page marks for deletion only the page on the current node. Pages (if any) on other nodes are not affected.

zzz About Declare Pages rules