We are having few Node level Data page -, in which we cache some external system’s data(Via calling external API from data page context ) , so that , these data can be used to source drop down fields in PEGA case. In Case View , we have some Thread level data page -which refers to these Node level data page to bring the filtered data ( as applicable for that respective case context ) .
We need to refresh/reload these Node level data pages , X amount of time , across a day , where we can set the X value ( like 2 /3/4 times) .
We want to put one refresh strategy on these Node level data pages , so that it never gets loaded from a User Context ( as it is going to take much time and it can create bad User experience) .
We are planning to introduce a Job schedular, which will run on the User Node and will do the refresh /reload via calling pxClearAllInstancesOfDataPage(DT) or pzFlushDataPage ( Activity ) .
I need some guidance here- In Constellation ,Does Node level data pages as well cached to User’s browser ?whether this approach will work considering we are not going to clean the D page from user cache explicitly via calling pxC11NPublishDatapageUpdate or we need to change our approach?
@AVIKCEMKnode level datapages are not available in the Constellation UI. So consider how you want to set-up your refresh strategy for the thread/requestor level DP (see methods here), which eventually will copy data from the node level DP
Thanks for clarifying that Node level data page concept is not applicable in PEGA constellation.
As per the Pega Documentation(Data Pages in Constellation) , we need to use pxClearAllInstancesOfDataPage(DT) or pzFlushDataPage ( Activity ) to invalidate Data page in server and pxC11NPublishDatapageUpdate to invalidate it in Client Side .
When as per Business terminology–say i want to refresh a data page , that means i want the loading logic to re run and as per my understanding , this needs to be happen in server side .
Need clarity --considering our business use case ( we want to reload the Data page , so that Latest API results gets available in PEGA) -should we use pxClearAllInstancesOfDataPage(DT) or pzFlushDataPage ( Activity ) ? Or we need to use pxC11NPublishDatapageUpdate ?
Also, can you please explain when we need to go for Client side data page refresh ?
You need to determine in which scenario’s do you need the datapage on the UI to be refreshed.
Given your original question about a node-level datapage. You should handle that completely from the back-end (probably-off hours) with an activity. There should not be a need to use pxC11NPublishDatapageUpdateas this will inform the UI that a DP needs to be refreshed.
For the Requestor/thread level DP, you can handle that procedurally within the requestor session (with eg pxClearAllInstancesOfDataPage) OR (if you really have to), use pxC11NPublishDatapageUpdate from the Server-side.
on your last question “can you please explain when we need to go for Client side data page refresh”, that all depends on your use-case. But given that you have a node-level DP question, I do not see a need to refresh it from the UI side