Data pages can improve performance and reduce memory requirements when all or many requestors in an application need to access information.
For example, a data page might hold last night's closing U.S. stock prices in a Value Group property indexed by ticker symbol, so that the property reference D_Stock.Price("IBM") is the closing price for IBM shares. The first time each evening (after the 4:30 P.M. New York market close) that a requestor attempts to access the page, the Pega 7 Platform automatically loads the page with the latest end-of-day prices. The page can remain unmodified in memory until the next day's closing.
You can also reference data pages using parameters, and the data page can create on the clipboard unique instances of itself for each unique reference, with data related to the parameter values. For example, a single data page, D_Customer, can create many instances of itself on the clipboard as your application requires. Each instance has exactly and only the information about that particular customer.
In other situations, data values are not static but can change infrequently. The Pega 7 Platform automatically checks the data page contents (using a when condition rule) before each property access to see whether a fresh recomputation is needed. For example, a page might list the part numbers or SKU numbers of items that are out-of-stock, extracted from an inventory control system. Recomputation is needed only as often as an out-of-stock condition begins or ends, not each time the inventory changes.
Note: You cannot use the Page-Remove method or the Clipboard tool to delete a data page.
A data page with a Node scope is removed when the Pega 7 Platform is shut down for that node or when the rule is deleted.
A data page with a Thread scope is removed when the requestor of that Thread logs out.
Data pages with a specific name are removed when you save a data page rule form that has a key (Page Name field) with a matching name.
Use a data page rule to hold global resource settings. These allow service rules and connector rules to be identical in multiple Pega 7 Platform instances, such as a test system and a production system, while still using different ports, URLs, and servers.