Posted: 19 Dec 2018 21:26 EST Last activity: 19 Dec 2019 9:38 EST
Refresh a layout when a property change in different thread
I have observed this behaviour in Pega 7.3.
I have a Portal with a portal-header and a main section (to show the tasks/case types). The portal header is under ThreadA and the main section is under ThreadB.
I have a layout to display the value of property prop in the main section (Thread B) and a refresh condition when property "prop" changes in this layout.
But the property "prop" will be updated only in the ThreadA. This property is under a Top-Level page "Top" which is shared between ThreadA and ThreadB. So, I expect that the layout will refresh whenever the property Top.prop changes.
Here is the problem, The layout (in the main section) only refreshes when there is a reference to the property "Top.prop" in the header (Thread A). When the property "Top.prop" is not referenced in the header, the layout will not refresh. But I don't want to display the property in the header.
I have ended creating an empty layout in the header with a refresh condition on Top.prop, so I have a dummy reference in the header and, thus, refreshing the main section when the property is updated.
I want to understand this behaviour, can you explain this? Thanks.
***Edited by Moderator: Pallavi to update platform capability tags***
Yes I believe this limitation still exists. But this isn't the first time I am hearing for this feature to be supported across threads natively. A PSC moderator can help you submit an enhancement request here if you wish.
At first, I used the proposed workaround (to use an empty layout with a reference to the property). But my team didn't think of that like a long-lasting solution.
So, we came up with another solution. We are using CRM framework, so when the CSR receives a call, there is a timer. We used that timer to keep the layout refreshing. So, in the end, the layout is refreshing every second.
I hope this feature will be available in future versions.
Thanks for sharing this with us! I have submitted this for future consideration as an enhancement. I have updated your original thread with the Feedback ID that you can take to your Account Executive for next steps.