Data Propagation topics covered

1. Populating Data
from Data Pages
Team Actualizers

2. Data Pages
Data pages define the data associated with a data object and contain the
data object's connection configuration to a system of record, separating
your application from the integration with the system of record. Because of
this separation, your application can easily adapt to integration changes
and access data from a range of sources on demand. With data pages,
you can connect a data page of one object type to a data source of
another, incompatible type, enabling data virtualization.

4. How to source your data into data page?
In the Data Sources section, in the Source field, select a data source for your data
page:
● Connector – Use the response of a connector as the data source.
● Data Transform – Specify a data transform to use to populate the data page.
● Report definition – Use the results of a report definition as the data source.
● Lookup – Use an instance of the specified object type as the data source.
● Activity – Execute an activity that creates and populates the page.

5. Connectors
The data page or activity invokes the connector:
The connector is initialized based on its type. The type is the protocol the connector supports.
Pega provides connectors for a wide range of industry-standard protocols and standards. Standard
connectors include SOAP, REST, SAP, EJB, JMS, MQ, File, and CMIS.
The connector maps the request data to the protocol-specific format using the mapping rules specified for the
connector. Do not confuse this mapping with data transforms. This mapping is between the clipboard and the
format required by the protocol.
Connector rule – Uses the integration clipboard pages to build the request according to the protocol and
service definition, invokes the service, and parses and places the response on the integration clipboard pages
Finally, a data transform maps the response data from the integration clipboard data structure to your
application.

6. Data Transform
A data transform defines how to convert data that is in one format and class (the source) into data of another format
and class (the target). The supported formats are clipboard and JSON. Using a data transform instead of an activity to
set property values speeds up development and makes application maintenance easier.

7. How Data Transform Works?
Optional data mapping on the property form – On the Edit Property form, the Optional Data Mapping field
appears when you select Copy data from a data page. Use this data transform to copy a subset of the data
from the data page to the property. If you do not specify a data transform, the system copies all of the data
from the data page to the property.
Request data transform – When a data source for a data page is a connector (an integration with an external
data service), the request data transform lets you map Pega Platform data to the fields that the connector
needs to communicate with the data service. Select the data transform to use in the Request Data Transform
field on the Data Page rule form on the Definition tab, in the Data sources section.
Response data transform – Response data transforms normalize data provided by the data sources into the
common application data model. A response data transform is required when the data source class is
incompatible with the data page class . Select the data transform to use in the Response Data Transform field
on the Data Page rule form on the Definition tab, in the Data sources section.

8. What is Report Definition?
Report definition is a type of rule in pega that is used to interact with the database tables and fetch the
information based on the business need.
Report definition are rule instance of class Rule-obj-Report-definition.
Report definition can be found under the Report category in the Records explorer.
Each report definition rule has 5 main sections to configure
-QUERY
-CHART
-REPORT VIEWER
-PARAMETER
-DATA ACCESS

9. Report Definition

10. Look Up
the "Lookup" option is available to populate a data page as long as you choose "Page" as the Data Page
structure. When using this you are populating the data page with an instance of a class. So you will configure
this by inputting the class name and a parameter to identify which instance to use at runtime. This is very
handy when you need to update the data page with an entire page of data that is conveniently found in an
existing instance of a class.
A List type data page is used typically to retrieve multiple records for the dropdown, radio buttons, checkbox
controls, whereas the Lookup data page will then use the selected value from these controls to retrieve the
details of a specific record.

11. Different Scopes
● Thread – The page is created in a single requestor thread and can be accessed as often as needed by
processing in that thread.
● Requestor – The requestor can access the pages loaded across all threads.
● Node – Any requestor executing on the current node can access the pages.

12. Thread scope
Use case: Caching stock pricing and volume data during a purchase or sale transaction.
Solution: Set the scope of the data page to Thread to ensure that each transaction references current pricing and volume
data for the appropriate stock when creating the transaction request.
Requestor scope
Use case: Caching a list of preferred shipping addresses for customer orders.
Solution: Set the scope of the data page to Requestor to use the list of shipping addresses for each order placed by a
single customer. The customer can select the appropriate shipping address for each order without needing to reload the
entire list each time.
Node scope
Use case: Caching a list of automobile makes and models to populate a set of searchable fields for an automobile insurance
quote.
Solution: Set the scope of the data page to Node, because the list of automobile makes and models is common to all
quotes.