If we are editing a screen 1 say and then instead of completing or saving our work we are calling pxChange stage activity how will this data remain as it is?because by default pega will discard this screen right so how to retain this data without getting impacted while calling pxchangestage?
In Traditional UI, this is typically handled by using a Post Value action on the fields, which immediately synchronizes the entered data to the clipboard server-side before the stage change activity is invoked.
In Constellation, there is no Out-of-the-Box (OOTB) mechanism that mirrors this behavior natively. However, you can leverage a specialized DX component from the Constellation UI Gallery designed for this scenario:
- Auto-save field: This component automatically commits field changes back to the server as the user interacts with the UI.
Note: Use this component with caution. Because it invokes a save API call on every field mutation, it can introduce noticeable performance overhead if implemented across a heavy or high-traffic form.
Hi @VVNagaSaiN in traditional pega I want to know ,how only by post value the data will not be lost if we go to another stage?
In Constellation, if you’re performing the change stage from Optional action, the data is lost. However, if you’re using pxChangeStage from PostFlowAction, then you should be able to persist the data before the change stage.
When you configure a Post Value action on a field in Traditional UI, the entered data is immediately sent and synchronized to the server-side clipboard page (pyWorkPage) as soon as the user focuses out of that field.
Unlike Constellation—which stateless-ly reloads case data directly from the database for each discrete interaction—Traditional UI relies heavily on this active state in the server memory. When you subsequently invoke the pxChangeStage activity, it operates directly on that same in-memory clipboard page containing your freshly posted values until unless there is a new Obj-Open from the DB.
Pega processes the stage transition within that thread context and executes an explicit database commit at the very end of the assignment or flow action cycle. Because the modified clipboard state is preserved throughout the execution of the change stage activity, your data is written to the database without being lost.
Hi @RameshSangili how to persist that data,that’s what i wanted to know,in traditional UI?
Hi @VVNagaSaiN so we do not need to write any DT or activity in post value?
No, you do not need to write any custom Data Transform or Activity for the Post Value action itself.
In your Section configuration, simply select the field, go to the Actions tab, and add an event (such as On Change) paired with the Post Value action. This out-of-the-box configuration is all that is required to move the UI inputs directly into the server-side clipboard session (pyWorkPage).
Keep in mind that Post Value only updates the data in memory; it does not commit it to the database on its own. However, when the user subsequently triggers the stage transition, Pega’s internal processing for pxChangeStage automatically handles the database commit at the end of that cycle.
As long as the data was successfully posted to the clipboard beforehand, it will be seamlessly persisted to the database. If a user cancels or exits the step without a stage change or assignment submission or any other action that calls Commit, the posted in-memory changes will simply be discarded.
Hi Tanya,
2 options that I can think of it,
Option1 : Call Save to save the details of the Work Object and then peform pxChangeStage
Option2: Trigger pxChangeStage on PostFlow Action of the Assignment, so the details will be saved
Trying to post the values on trigger of local action is problematic - what if those values are invalid? what if they would of failed validation?
Build your own “change stage” action
Personally, I’d be looking to combine the flow action you are in with a change stage, so that you can have a single UX using OOTB approaches. So an extension of what @RameshSangili said, in post processing (after flow action validation) then you can run the activity to change to the stage selected in the form. This means all data is saved and validated naturally.
This is very common, pretty much every project I’ve done has their own versions of change stage (its never as simple as the OOTB option provides)
Auto-save?
If the problem is saving data, UI Kit provides for autosaving forms from Infinity '25.
