Constellation - Summary Tab Not Refreshing After Adding Records Through Case-Wide Local Action

General
1

I have a requirement in a Pega Constellation application and would appreciate any suggestions.

Scenario 1

  • I have a Case-Wide Local Action called Add Note.
  • When a user submits the local action, the note is saved into a Data Type (database table).
  • In the Summary tab, I display the notes by reading data from the same Data Type.
  • The record is successfully saved to the database.

Issue: The Summary tab does not automatically display the newly added note. To see the latest data, I must either:

  • Click Refresh from the three-dot menu, or
  • Refresh the entire browser page.

Has anyone implemented an automatic refresh mechanism in Constellation so that the Summary tab immediately reflects newly added records after the local action is submitted?

Scenario 2

As an alternative approach, I considered enabling the Add (+) action directly from the Data Reference/Data Type configuration.

However, I need to pass the current Case ID while creating the record so that only records related to the current case are displayed in the Summary tab.

Challenge: From the Summary tab context, I could not find a straightforward way to access or pass the current Case ID to the Data Type record creation flow.

Has anyone implemented a similar pattern in Constellation? What would be the recommended approach to:

  1. Automatically refresh the Summary tab after record creation?
  2. Pass the current Case ID when creating records directly through the Data Type Add action?

Any guidance or best practices would be greatly appreciated.

Thank you!

2

@VemulapudiB17750633 you’ll need to invalidate the datapage behind the list view. See How to notify users to refresh an outdated List View in Constellation UI

3

If the user is already on the Summary tab, the list view does not automatically refresh when a new record is added to the underlying Data Type. The data is successfully saved, but the view continues to display the existing results until a refresh occurs.
You may want to explore the following options:

  1. How to notify users to refresh an outdated List View in Constellation UI
  2. Use the pyPublishMessageForCaseRefresh activity to publish a refresh event. We have successfully used this approach in one of our Constellation implementations to refresh the case view after updates. Depending on the scenario, it may still require the user to interact with the refresh notification or refresh action presented by the UI.
5

Thank you @MarcCheong @RameshSangili
This helps -How to notify users to refresh an outdated List View in Constellation UI - User Experience / Knowledge Share - Pega Forums for me

7

@MarcCheong @RameshSangili :
One additional observation:
Currently, the notification message is displayed for all open cases. My requirement is to display the notification only for the specific case that was updated.
“{“CaseInstanceKey”:”" + Param.CaseKey + “”}"

I tried passing the Case ID/CaseInstanceKey in the JSON payload as suggested in the article:
Java"{“CaseInstanceKey”:“” + Param.CaseKey + “”}"Show more lines
and passed the current case’s pzInsKey as the parameter value. However, I am still seeing the notification message across all open cases rather than only on the updated case.
Has anyone been able to scope the notification to a specific case instance in Constellation so that only the affected case receives the refresh notification?

8

Update / Solution Found
I was able to get the case-specific notification working.
Initially, I was using:

Java{“CaseInstanceKey”:“”}

I later realized that the JSON payload needs to match the parameter name(s) defined on the data page being refreshed.
In my case, the data page is parameterized with CaseID, not CaseInstanceKey. Once I changed the payload to:
Java"{“CaseID”:“” + Param.CaseID + “”}"
and passed the appropriate Case ID value, the notification became case-specific and started working as expected.
This helped resolve the issue where the notification was previously appearing across all open cases.

9

amazing, thanks for confirming! I didn’t know this, really handy :slight_smile: