DATA PAGES

1. is it possible to call more than one source from datapage?

a) Configure multiple data sources in your data page and set parameters that determine which data source
to use, so that your application gets the right data every time. To specify more than one data sources for
the data page, on the Definition tab, in the Data Sources section, click Add alternative source for each
data source that you want to add.
The IF field is displayed above the first source in the list.
In the IF field, identify the When condition that evaluates whether the current reference to the data
page requires using the source identified in each row.
If you add additional sources, the condition for each additional source is set as ELSE IF. You cannot use
the same When condition for more than one source.
The condition for the final data source in the list is set as Otherwise. If all the preceding When conditions
evaluate to false, the data page uses the final data source.

b) You can now configure data pages to aggregate data from multiple sources. With this enhancement,
data pages load more easily, making your implementations faster and easier. For example, by
aggregating sources, you can call multiple REST connectors to load your data page, instead of using an
activity.
2. How many ways to load Datapage? (many ways)
We have method in activity called Load-Data Page to load data page asynchronously. Also you can call data
page from activity, Data transform, Sections (Layouts and dropdown) as source.
When above rules executed for the first time Data page will get loaded.
3. How many ways to clear the Datapage? (many ways)
1. Click on Clear data page button in load
2. You can remove the content of the data page through an activity by using Page-Remove with the. it
will applicable for Parameterized data pages also.
Example
Page-Remove D_YourDataPage[ParamName:ParamValue]
3. If you wish to flush all the available instances of a particular data page, call "FlushDeclarativePage"
Activity and pass page name as the parameter to be flushed along with parameter pyFlushAll as true.
c) you can invoke an OOTB function "pega.getDeclarativePageUtils().flushPage(<YourPageName>));" to
flush out data page instances
d) use java method as below to remove all instances of Data page,
@java("pega.getDeclarativePageUtils().deleteAllInstancesOfDeclarativePage(\"yourdatapagename\")")
set this to a dummy parameter like param.TempFlush to allow the DT to save.
e) @(Pega-RULES:DeclarePages).pzDeleteAllInstancesOfDeclarativePage(tools,"<Data Page Name>")
b. management tab in Data page
a)
 I. No node in scope when we select editable in mode. Why?
The purpose of editable Datapages is to manipulate the data on Datapage. Requestor 1 fetches the actual data
and modifies the data. If it is fetch by requestor 2, data inconsistency is there. Because of these issues, pega has
removed the node scope for the editable mode.
II. What is look up source option in Datapages?
The look up option for Datapage is obj-open where the look up is use in order to fetch the single record in
Datatable using clasky.
III. How to use two data sources in Datapage?
In order to use two data sources in a Datapage, we have one option called aggregate source. If we will go with
the aggregate source then we can two different sources for Datapage. Other than that in normal regular process
also we can add a when condition and add one more source which is conditional sourcing we can implement.
IV. How to call Datapage with in another Datapage?
We can call Datapage from another Datapage when we the source data transform or activity. Suppose it is data
transform, with in a data transform, anywhere if you use or refer the name of another data page, then other
Datapage will be automatically called.

You could directly use "Set" method in the data transform rule.

Action: Set

Target: Your Page/PageList were you want to store the content of DataPage.

Source: D_YourDataPageName[Param1:ParamValue1,Param2:ParamValue2]

You can use "." operator as D_YourDataPageName[Param1:ParamValue1,Param2:ParamValue2].YourPropertyValue to

fetch specific property and accordingly, you have to change the "Target"
 Similarly, in the activity also, in any of the methods if I going to refer a data page, then the data page will be
called. And also we can use the method called load Datapage.
So whenever a Datapage is being called, it execute the source rule of either data transform or activity, within
source rules we can refer another Datapage name. That also will be called.
V. We have two datapage. One is thread level datapage and another node level datapage. So we calling tread level
datapage in node level datapage. If daily 100 cases are getting created. How many times node level datapage
gets called? How many times thread level data page gets called?
Whenever a request has been made, first datapage is going to execute is node level datapage. In the node level
Datapage, thread level Datapage is being called. So usually node level Datapage means, it will executed only
once for all requestor in the server. In that case, when node level data page is getting loaded, it will make a call
to thread level Datapage. So thread level Datapage also loads for the first time. So for the first request, node
level and thread level Datapage both are loaded. And whenever the request has been made, when it is going to
request for the node level Datapage, now the node level Datapage is already been created in the previous
request. It will be copied so only when node level data page is executed, thread level also will execute. But
second requestor, node datapage is already loaded so it will copy. But in the 2nd request time, the N L DP is
already loaded, it will copy. Further any request has been made, N L or T L wont be further executed. So for this
question, N L as well as T L datapage runs only once even id you created 100 or 1000 work objects.
If we call node level datapage in thread level datapage.
In that case for the 1st request when it is been made, thread datapage will get executed in a work object. and
thread will call the node level and lode level will get loaded and tread level also will get loaded. When we are
creating second work object, the T L DP will going to execute again and with in TLDP, it make a call to NLDP. But
NLDP is already being executed in previous request right, that will be available for sharing, it will be copied. So
over all, if we are creatng 100 work object TLDP will execute 100times where as node level datapage will
execute only one time.
VI. What is use of keyed datapages?
On the page, when we select the datapage structure as list, then we will be getting one option called keyed page
access. Which means that this data page can be pass with the key. On the right side, we can choose keyed page
access check box, and we can choose the properties as keys. So keyed Datapage, we are going to passing the key
values to Datapage. It is not like parameter passing, it is like key values are passing in pagelist. This key value for
Datapage can be passed only from one place in pega that is when we calling the Datapage form page property.
So from another page property, we calling datapage, then we can pass the keys for datapage. That is only one
place where we can call keyed acess datapage.
VII. What is parameterized Datapage?
On the Datapage, we have parameters tabs, there we can find parameters. Where ever we are calling the
Datapage, it is going to prompt for the parameter values. For example, if we calling the Datapage as a source for
the dropdown, at the time calling, it will prompt for a value. Suppose if we call a Datapage, in an activity like we
are refreing the datapage name in the data transform or in the activity. Passing paramater value is something
different. That is we have to write this way, like,
datapagename[parameter name: parameter value,parameter name: parameter value]
D_page1[param1:value, param2: value] like this we need to pass values to the parametarised datapage.
VIII. What is a Data Page and what are the sources of Data Page?
IX. What are the modes of Data Page and explain each?
We have three options In the mode of the datapage. Editable, readonly and savable. Readonly datapages gets
created on clipboard under datapages category. These pages cannot be deleted. If you want to forcefully flush
this pages at the run time we need to call an OOTB activity, flushdatapage. And editable and savable datapages
gets created on clipboard under user pages itself. Where as editable datapages, its purpose is to manipulate the
 data after it is been retrieve. savable datapages purpose is , it is alternative for obj-open+obj-save which means
that using the savable datapages we can insert a new record into table and we can open existing record in the
table, modify and save it back. We can call savable datapages by using flow shape called save data page. And
also a method in the activity called savedatapge.
X. Difference between Read-only and Editable data pages?
XI. What are the scopes (Thread, Requester and Node) of Data Pages? Explain the differences with an example?
XII. What is the significance of specifying the access group for Node level data pages?

Generally rule resolution will works on access group to find load activity to load data on to
data page. And generally Data page will load data only when it referenced in some place.
that time it can consume that particular requester access group to load data, there no
problem system can use that. But the point of or the utility of data page is to load one
time and share the data to all the requesters connected to particular node.

If it use every requester access group, then it has to load for every requester. Then it loose
the concept of Node level Data page.

So for this reason only we have maintain a separate access group for node level data page
to invoke load activity to load the data and it can be shared between all the requesters
connected to that particular node.

thanks, it can be helpful to others who has a confusion with this point.
Or
Node level data page acts as a separate requestor which runs in its own execution stack, which is different from
any requestor user. Since it is independent we need to specify the access group for node scoped data page.

Example: Even though you private check out data page source activity, and modify with your changes. When
you run the data page standalone from actions>> run menu, you would notice that your private ruleset changes
are not picked. This is one justification that node level data page will run in its own execution stack .
I. Explain the refresh Strategy in Data Pages?
II. How to call Data Page from different rules?
III. How to Pass Parameters to the data page from Data transform?
IV. How to flush data page dynamically?
V. Explain Savable data pages? How to configure Savable data pages?
VI. How to handle exceptions in data pages?
VII. How can we load datapage asynchronously?
Data page can be loaded asynchronously by calling the datapage from activity. In activity there is method
available, load datapage, when we use that method and provide the datapage name then data page will get
loaded asynchconously, which means that activity at the calling step will not wait. Activity will call the data page
and will proceed forward on its way. Where as datapage executed in a background in a diferent thread. Like we
are calling activity from another activity by using queue instuction how it asynchronously execute. The way load
datapage is going to execute the activity and datapage asynchronously.
VIII. If we do not mention any refresh strategy, when the D page does gets removed from server?
IX. What is Reload once per interaction?
X. What is Pool ID in Load-Data Page Method?
XI. What is Keyed Data access Page? Explain the purpose?
The advantage of using this keyed access Datapage is entire list data will retrieve and being made available in
the clipboard. So whenever you are referring a page property which is calling a Datapage and passing the key
 values. Now it will search existing Datapage from clipboard and retrieve the data from the clipboard. That data
we are getting on the screen. Datapage loaded only once hit the database one time only.

So by using keyed access pages, search will happen directly on the clipboard, not on the data type or table.

XIII. Difference between Keyed Data Pages and Parameterized data pages in one scenario?
We have search screen three, we are going to serach the customer details with customer ID. We will pass this ID
as a parameter to the datapage, in the datapage I am going to do a look up, means it is going to search for the
customer details. On the clipboard, it will get created whenever a customer ID been entered, and click on
button probably calling an activity and activity is calling datapage and datapage is getting loaded. That is case,
then datapage is going to created on clipboard for each parameter.
For parameterised datapage, for every customer search, the search is happening by hitting the database. But we
go with keyed page access, the search will happen on the clipboard. Because datapage is already fetch all the
customer details on the clipboard on the pxresults. As you are passing the customer ID as key for datapage of list
structure. Now the search will happen in the pxresults of datapage which is there on the clipboard. It going to
match with customer on the pxresults1,2,3, and retrieve that page record and that will automatically copied to
the page on which you are calling the datapage of keyed page access. That how it is going to work. This is
efficient process, there is no need to hit the database again
and again when we go with keys.