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:

• Connector, which you use to fetch data from an external source and integrate the data in your application. For more information see .
• Data Transform, which you use to convert data before referencing it in your application. For example, you can use Data Transform to merge two or more lists into one, and to display the new list. For more information, see Data transforms.
• Report definition, which you use when you want to source data from a query result for a particular table. For more information, see Populating a data page by using a report definition and Sourcing large data pages from a report definition.
• Lookup, which you use in a similar way to a report definition, but a lookup searches the database by a particular key to filter the search results, for example by the Employee_ID key, and populate the D_EmployeesByID data page. For more information, see Applying business logic when importing data.
• Activity, which is a multipurpose tool that provides a wide range of options. For more information, see Viewing test coverage reports and Create or Save as form in AUT test suite.
• Robotic automation, which you use to fetch data from external systems. For more information, see Using a robotic automation to populate a data page and Robotic automation as a data page source.
• Robotic desktop automation, which is robotic automation scaled down for a single user. For more information, see Robotic desktop automation as a data page source.
• Aggregate sources, which combine data from multiple sources to populate a data page. Pega Platform populates the data page from the specified sources in the listed order. For more information, see Configuring multiple data sources for a data page.

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