Hi everyone, I have a requirement that whenever the property in the Pagelist (A) changes, refresh has to be happened. (Clear all the values in Single page (B))
So here,
Is there any suggestion or any method to achieve this requirement?
pyRefreshData will work, but for Pega to trigger the refresh API call automatically, the UI needs a dependency to track.
A common workaround for this is to add a visibility When condition to at least one field on the screen (you can configure a simple expression or set a When rule to always evaluate to true). However, keep in mind that this approach forces the UI to evaluate and trigger a refresh API call for every field change on that screen, which can impact performance depending on the form’s complexity.
Alternatively, a cleaner approach is to design your page list records to be editable within a modal dialog. This allows you to handle the data clearing logic cleanly inside the post-processing data transform of that local action, executing the logic only when the modal is submitted.
@VVNagaSaiN Actually its a nested list structure,
Where the Pagelist (A) is a list property, which is opened in the modal dialog, and inside the modal dialog there is a pagelist(B), so on refresh of that (B) property the action has to be performed.
When pyRefreshData is used → It depend on the other flat property to get refreshed, only then the condition gets passed.
Instead of Post DT, Is there any possible solution to get cleared on demand of changing the property in list.
Could you please confirm the Platform version? If you’re are 25.1, then you could use Form refresh settings on the modal dialog for Property in Page List B to trigger the Data transform?
Create pyRefreshData in the class of Pagelist(A) and in that modal dialogue view, for atleast one field, set visibility when condition. You need not configure any form refresh settings. The refresh will be triggered automatically on change of any field.
Yes im in version 25.1, form refresh accepts only flat property?
This seems like a known gap, Form refresh settings do not support properties inside a Page List, so your observation is expected. many articles point towards**pyRefreshData** as the supported workaround for non-scalar properties, but it only works when the UI has a dependency that causes the refresh request to fire.
You can try to Create or extend pyRefreshData in the relevant class and place the logic there to clear all values in single page B when the Page List property in A changes. However, if pyRefreshData appears “not working,” the issue is often that the UI is not issuing the refresh call automatically
A practical workaround would be to implement the Page List editing in a modal dialog and clear page B in the modal’s post-processing logic when the user submits. This keeps the clearing logic explicit and avoids forcing refresh evaluation on every field change.
However, if you wanted to still continue with your current implementation of pyRefreshData, then use pyRefreshData plus a field-level visibility dependency so the UI performs the refresh request. Be careful, because this can affect performance if the screen is large.
Do not expect Form refresh to work directly on a Page List property, because it is meant for scalar properties and embedded properties inside a single page, not Page List items.
If you’re data model is something similar to this, then it should work
If you’re expecting to trigger Form Refresh settings based on Property3 or Property4 changes, that can be done using Modal dialog in 25.1 version.