LinkedIn
Copied!

Table of Contents

Elements of a data page

Version:

Only available versions of this content are shown in the dropdown
Applicable to Theme Cosmos applications

Use data pages to ensure on-demand and accurate data sourcing for your UI elements.

Data pages enable users to define a set of named clipboard pages for an application, which are created and refreshed on demand whenever needed by other rules. Data pages are cached and remain on the clipboard until further notice, based on the refresh strategy defined on the load management tab of the data page rule form, which improves system performance.

You create data pages in Dev Studio by configuring the following key components of a data page:

Content structure
Determines the number of items that a data page contains. For example, you can select page structure for a data page that contains pricing information for a single stock, or list structure for a page with all the stocks in an investment portfolio.
Object type of the data page content

Identifies the information that a data page contains. The class of the object defines the object type. The object type allows the data page to reference any property defined for the class. For example, a data page that lists dental insurance plans provided by an insurer contains the plan name, cost, and deductible, while a data page that lists recent orders placed by a customer contains the order number, order date, total cost, and shipping address.

Edit mode
Indicates whether an application can modify the information on a data page, and if so, how. For example, when you configure savable mode, after a customer updates a shipping address, the application copies the updated address to a savable data page configured to update the customer database.

Edit mode options include:

  • Read-only mode, which prevents users from editing information sourced from a system of record and ensures that the data page content always matches the content loaded from the system of record.
  • Editable mode, which enables users to edit the data page content.
  • Savable mode, which enables users to modify and push the page content back to the data source. For more information, see Savable data pages.
Data page scope
Determines the visibility of the page content within the application.

Scope options include:

  • Thread, which you select when the content of a data page is unique to a single case. For example, the D_TerritoryList data page, which loads territory information into the portal as soon as the user logs in. The data page is available in the portal context.
  • Requestor, which you select when the content of a data page is common to all of the cases created by a single user or in one system session. The data is not shareable between users. A requestor-level data page, for example, can contain credentials, personal information, customized user preferences, and information about the current process or activity.
  • Node, which you select when all users and system tasks share the content of a data page. When you define a data page at the node level, you ensure data integrity between multiple users because all requestors share these pages on a given system node. Node pages store common data in one place that multiple users of an application share. For example, node pages contain lookup lists, tables, organizational information, system settings, and any other application-wide information that you want to share.
Data page sources
Specifies how Pega Platform populates the content of a data page when an application references the page.

You can use any of the following options to configure a data source for a data page:

To learn more about the configuration of a data page, see Creating a data page.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.