Question


Wellsfargo
IN
Last activity: 2 May 2025 2:52 EDT
Unable to edit the pyStage view
Getting json failure message while trying to edit the pyStages view.
Scneario:
We are running a job schedular and updating case with some property in backend. In the mean time if some has opened the case, we want them to notify with refresh message to see the updates on case( Similar to refresh outdated list views)
To achive above scenario i am trying to add the banner widget in pyStage and to update conditionally to display message.
Note: Not looking for custom DX component.
-
Reply
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!


Blue Rose Technologies GmbH
DE
In Pega Constellation, you can achieve real-time update notifications in the case UI without creating a custom DX component. Here’s how you can resolve the JSON failure message while editing pyStages
view and implement the refresh notification banner effectively.
Possible Causes of JSON Failure While Editing pyStages
View
-
Schema Mismatch:
- Ensure that the banner widget configuration follows the expected JSON schema for Constellation views.
- Any incorrect property reference or missing metadata could cause the failure.
-
Unsupported Customization in
pyStages
- The
pyStages
view is an OOTB system-generated view in Constellation. Some UI modifications may not be allowed directly.
- The
-
Job Scheduler Updates Conflict with UI
In Pega Constellation, you can achieve real-time update notifications in the case UI without creating a custom DX component. Here’s how you can resolve the JSON failure message while editing pyStages
view and implement the refresh notification banner effectively.
Possible Causes of JSON Failure While Editing pyStages
View
-
Schema Mismatch:
- Ensure that the banner widget configuration follows the expected JSON schema for Constellation views.
- Any incorrect property reference or missing metadata could cause the failure.
-
Unsupported Customization in
pyStages
- The
pyStages
view is an OOTB system-generated view in Constellation. Some UI modifications may not be allowed directly.
- The
-
Job Scheduler Updates Conflict with UI
- If the Job Scheduler is updating properties on a case, it could create a conflict when trying to edit a system-generated view (
pyStages
).
- If the Job Scheduler is updating properties on a case, it could create a conflict when trying to edit a system-generated view (
Solution Approach: Using case.processingStatus
to Display Refresh Notification
Since Constellation does not allow direct UI customization like in Traditional UI, use case-level metadata to trigger refresh messages dynamically.
Step 1: Utilize case.processingStatus
to Track Updates
case.processingStatus
is automatically updated when a case is modified in the backend.- It is referenced by the Constellation framework to determine when a refresh is required.
Step 2: Configure a Refresh Message Using a Banner Widget
Instead of modifying pyStages
, configure a banner widget inside a custom case view.
-
Navigate to your case type → Views
-
Create/Edit a case-wide view (e.g.,
pyCaseMainView
orpyCaseHeader
). -
Add a Banner Widget with a condition based on
case.processingStatus
. -
Configure Visibility Conditions:
- Show the banner only if the case is updated in the backend.
Step 3: Automatically Refresh the UI When Case Data Changes
-
Ensure
case.processingStatus
is updated in the Job Scheduler- Modify your Job Scheduler to set a property (e.g.,
UpdatePending
) when it updates the case.
- Modify your Job Scheduler to set a property (e.g.,
-
Enable Auto-Refresh in Constellation
- Constellation UI detects backend changes automatically and prompts the user.
- If needed, set up a Polling Data Page to periodically check for updates.
Alternative: Using the pyWorkPage
Metadata Approach
If case.processingStatus
does not trigger updates reliably, use a custom case property.
-
Update a property (e.g.,
.RefreshRequired
) in the Job Schedule -
Use a condition in the UI to display the banner
- Add a visibility condition:
Final Thoughts
- DO NOT edit
pyStages
directly in Constellation. - Use case metadata (
case.processingStatus
) to trigger UI refresh. - Add a Banner Widget in a case-wide view (e.g.,
pyCaseMainView
). - Ensure the Job Scheduler updates the metadata to inform UI about backend changes.
This approach ensures that users get a real-time refresh notification without breaking Constellation's architecture.
Let me know if you need further refinements!


Wellsfargo
IN
Hi @sathishsenthil,
Thanks for your reply.
Are you able to add banner component?
For me it's not visible to add.


Rabo
NL
We aim to display a message as a banner across the case. Could you guide us on creating/editing a case-wide view and configuring it within the case area? Although we managed to add a Banners widget, configure a Data page, and display the message in the Details tab, we couldn’t get it to appear in the main case area. Thanks, Hanisha


Wellsfargo
IN
Hi @HanishaP17376554 , What is your pega infinity version?


HCA Healthcare
US
@SreenivasuluV16633502 The issue with being unable to edit the pyStage
view and encountering a JSON failure message often happens because pyStage
is a final rule or system-generated rule not meant to be directly customized. Instead of modifying pyStage
, you can create a section that includes your banner message and conditionally display it based on a case-level property (like .pyIsCaseOutdated
). Include this custom section in the main harness or a custom section used in your stage layout, avoiding direct edits to system rules. To achieve real-time notification, use the case locking mechanism and declare a property that is updated via your job scheduler. When the user opens the case, use a when
rule to check this property and show the banner. Also, consider using a Declare OnChange
rule or Declare Trigger
to update the property and a browser refresh action like Refresh-Other Section
to reflect changes without needing DX components.


Wellsfargo
IN
Hi @Sairohith, we are pega constellation. and its view based configuration