Pega Constellation UI refresh Issue

User Experience
1

On Screen having table layout which showing details of Contact.

On edit Action of that row opening popup window to have some new option and opening one more popup to add new contact.

After that Values are not displayed in the table layout on the popup screen immediately after adding. However, the data is persisted successfully and becomes visible when the edit window is reopened after submission.

2

This behaviour is typically caused by the parent table retaining a stale client-side/data-page snapshot after the nested modal saves the new contact. The database update succeeds, but the table’s source is not invalidated or refreshed until the parent edit modal is closed and reopened.

In Constellation, avoid trying to use legacy Refresh Section patterns. Instead, make sure the add-contact action updates the same page list/data page that drives the parent table, or explicitly invalidate and refresh that source after the nested modal completes. Constellation’s embedded-data modal support relies on declarative refresh and explicit save/refresh handling rather than classic UI Kit refresh actions

Since the contact is visible after reopening the Edit popup, the record is being saved correctly. The issue is that the table in the already-open parent modal is still using its existing client-side/data-page result and is not being refreshed after the nested Add Contact modal completes.

First confirm whether the table is sourced from an embedded Contact Page List or from a parameterized data page/query-

  • If it is an embedded Page List, add the newly saved Contact to the same parent Page List that the table is bound to. Avoid saving the contact only to a separate page/data source, because the parent table will not know that its list has changed.
  • If it is sourced from a data page/query, invalidate/reload the exact parameterized data-page instance after the Contact save, for example D_ContactsByParent[ParentID:], and then refresh the parent case/view. A generic invalidate without the same parameters will not refresh the page instance already used by the table.

If the update occurs outside the parent view’s direct state, publish a case-specific refresh after saving, after invalidating the Contact list data page, so that the parent modal re-queries the latest contacts. pyPublishMessageForCaseRefresh is one possible pattern for this scenario.

Also, do not use legacy Refresh Section configuration in Constellation. For embedded modal views, use the standard embedded-data/table action and relationship Create/Save Data Transforms, or use a saveable data page and refresh the same source that is bound to the table.

If you can share the Pega version and whether the table is based on an embedded Page List, Data Reference, or data page/query, the exact implementation option can be narrowed down

3

Can you confirm which Platform version you are using, and if you are on the latest patch release for that version? This sounds like an issue that I have seen before, and I believe it is fixed in the upcoming latest patch release (25.1.4) and latest platform version 26.

4

I never observed this issue on 25.1.3 version for Table View with Modal dialog for Edit/Add.

5

Currently i am using 25.1.3 version