Data Pages

When do we require a data page?

Data Page is a cached/shared page on a server’s clipboard.

Data Page Definition:

1. Structure
a. Page: If this is the data page to hold a single instance
b. List: If this is the data page that holds multiple instances.
2. Mode
a. Read only: – These Data Pages get created on the clipboard under ‘Data
Pages”.These cannot be updated or deleted.
b. Editable: These Data Pages get created on the clipboard under ‘User Pages”.
These can be updated or deleted.
3. Source

Can be activity, Lookup, RD, connector, robotic automation, and more.

Load Management:
 Page Management: clear data page button -> forceful deletion of Data page when required.
(It runs an activity internally -> FlushDeclarativePage OOTB activity)

Reload strategy: We mention the Duration of Days, hours, minutes, and seconds to refresh
the data page from the server’s clipboard. (Default = 24 hrs)

Reload once per interaction: For an interaction that a user makes requesting for the Data
page, it will be refreshed.

Scopes of Data Page:

 Thread: This Data Page will be available for sharing only within one specific work object
multiple times. But not available for other work objects. (Eg= available balance in a banking
system)

 Requestor Scope: This Data page will be available for sharing across multiple work objects
of a single requestor session. But not with other requestors. (Eg= on a single login, we can
do multiple transactions, with the same bank details we have)

 Node: Data Page will be available for sharing across multiple requestors who log on to the
same node but not with the requestors on other nodes. (Fixed Deposit Rates in a banking
server)

Advantages of Data Page:

1. Data Sharing as per the scope.

2. Number of times the source rule gets executed is reduced to ONE.

3. Number of times the data source gets hit (Database, file or service, etc. is reduced to ONE.

4. The number of pages created on the server clipboard is reduced to ONE.

As a result of all this, the performance of the application gets improved.

 Editable data pages will not be available at the node level.

The reason being editable data pages should not be modified by other operators.

Node Scope is not available for Editable Data Pages, Why? Data Modified by one requestor,
should not be shared with other requestors. That’s why the Pega PRPC environment will not
show up, Node scope or Editable data pages.

## Node Level Data Pages must need an access group to be specified.

Access Group is Required

## For other scopes thread and requestor access group is not required.

>> Why data pages are called declare pages?

Data pages are also called as declarative pages because when we refer the data page
system executes the source and get data from the source and places it in the clipboard for
usage.

>>What are the difference between Parameterised and

Keyed Data pages

Keyed Data page Parameterized Data page

Keyed pages will not hit the DB every Here Parameterized, hits the Db for
time every parameter value that we pass
As these hits multiple times the DB,
It maintains a single copy in the
multiple Data page instances are
clipboard
available
Keyed pages cannot be referenced in These can be directly referenced from
UI UI

>> Can we have multiple source for a Single Data page

Yes, conditionally (via when rule) we can execute multiple sources for a data page.

Explain how the data pages are stored in the Clipboard

All Read only data pages are stored in the “Data pages” category of the clipboard
Editable and Saveable data pages are stored under “User pages “

Difference Between Clipboard Pages vs. Datapage

Normal pages are stored in the clipboard are like static means they don’t have any
scope, no refresh strategy and etc.
Data pages in the clipboard are fetched on demand from the source and have scope
defined, have refresh strategies, and can be referred in the UI.
Keyed Data Pages: