Declare Pages form
Completing the Advanced tab

Field

Description

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.

Select to force the system to delete the declarative page after an interval of at least 24 hours passes with no access. Subsequent attempts by a requestor to access the declarative pages cause the page to reload.

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

This checkbox 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 change the timeout period from 24 hours (86,400 seconds) to a larger or smaller value by adding a setting to the prconfig.xml file in the following format:

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

where nnnnn is in seconds.

As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.
See How to create or update a prconfig setting.

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.

If 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.