Function pzDeleteAllInstancesOfDeclarativePage, Requestor-level Pages
Hi,
I have a reference data configuration mechanism in an application which will allow certain users to update reference data which is in the application via data pages. One of those pages depends on specific information directly tied to the currently-logged-in user. This page is defined as a Requestor-Level Data page.
When an "admin" of this reference data logs in and makes changes, I would like to be able to signal the system to invalidate all copies of this Requestor-Level Data Page, so that, upon reference, each request will re-load the page so that the newly updated configuration is available without each user having to log out and then back in.
Originally, I thought that @pzDeleteAllInstancesOfDeclarativePage() might be a good way to do this, however, general consensus amongst other Pega Professionals that I've spoken with is that, as with most processes, the @pzDeleteAllInstancesOfDeclarativePage() is governed by internal security and the request to invalidate the Data Page will not be carried out beyond the current Requestor -- which I agree makes sense, though I was hoping this was not the case.
Unfortunately, the function definition cannot be opened (or at least I have not been able to open it), and with no documentation and being unable to actually review the code, we have questions.
I believe that we have established that this function will flush Node-Level Data Pages.
So, that is my question:
Hi,
I have a reference data configuration mechanism in an application which will allow certain users to update reference data which is in the application via data pages. One of those pages depends on specific information directly tied to the currently-logged-in user. This page is defined as a Requestor-Level Data page.
When an "admin" of this reference data logs in and makes changes, I would like to be able to signal the system to invalidate all copies of this Requestor-Level Data Page, so that, upon reference, each request will re-load the page so that the newly updated configuration is available without each user having to log out and then back in.
Originally, I thought that @pzDeleteAllInstancesOfDeclarativePage() might be a good way to do this, however, general consensus amongst other Pega Professionals that I've spoken with is that, as with most processes, the @pzDeleteAllInstancesOfDeclarativePage() is governed by internal security and the request to invalidate the Data Page will not be carried out beyond the current Requestor -- which I agree makes sense, though I was hoping this was not the case.
Unfortunately, the function definition cannot be opened (or at least I have not been able to open it), and with no documentation and being unable to actually review the code, we have questions.
I believe that we have established that this function will flush Node-Level Data Pages.
So, that is my question:
Will someone from Pega Dev confirm or revise our belief that the @pzDeleteAllInstancesOfDeclarativePage() function is in fact Requestor-safe (and Thread-safe for that matter), or in fact that it will send a system-wide signal to invalidate all instances of the Requestor-Level (and/or Thread-Level) Data Page?
Assuming that the function is Requestor-/Thread-safe, it would be my supposition that, in the event of a configuration change like this, and a desire to invalidate Requestor-/Thread-Level pages across the entire system, the only way to accomplish that would be to make a call the "POST /nodes/{nodeID}/caches/declarative_page/clear" REST endpoint... forcing the entire declarative page cache to be cleared... (something we would not want to do because we rely on Data Pages for a great deal of processing power, and to invalidate the entire cache would undoubtedly cause noticeable delays on the system for users.
Will someone from Pega Dev also confirm that please?
Thank you in advance, Scott
Capgemini Financial Services
GB
@ScottW85 If I get your requirement it can be resolved by a simple data page configuration change. Since your data page is requestor level , have you tried enabling "Reload once per interaction" refresh strategy from load management tab of the data page?
If you are looking to get in to the function and see the code , you cannot directly since it is internal code. You may want to change your profile preferences and enable diagnostic feature.
Not Displayed
US
@nikhil_kumar Hi nikhil_kumar :-) thanks for the post. We have. Reload once per interaction actually causes problems with many of our data pages, and so we are forced to clear them manually. some of this is a factor of the way they are being used. this is a very complex application which unfortunately deviates from OOTB design significantly - not by our choice... lol. I am aware that the code is internal. thus the direction of my original post to the Pega Support Services/Dev group. I'd rather not open a direct support ticket for questions, and this is the kind-of information like always which is either poorly or not documented, and so when something "deeper" is needed, it is a struggle to acquire that information. and ultimately it would benefit the entire community. thanks again! :-)
Tech Mahindra Ltd
CA
@ScottW85 You may try using "Do not reload when". Inside the when rule refer a node level data page, which you should be invalidated whenever you require your requestor level data page to refresh.