@SravyaK This is a great question. The behavior you’re seeing is expected because the method you are using is a holdover from the traditional UI architecture.
Let me explain why it’s happening and show you the correct, modern way to achieve this in Constellation.
The Issue: Server-Side vs. Client-Side Actions
The pxCreateTopCase activity is a powerful server-side tool. When your local action’s post-processing runs it, the Pega server correctly creates the case, saves it to the database, and adds it to your worklist.
However, in the Constellation architecture, the user interface is decoupled from the server. The server-side activity does not automatically send a command back to the user’s browser to open the newly created case. You are missing the client-side instruction to open the work object.
Not unique to Constellation
I lost count of the time spent trying to get this kind of UX working even in Traditional UI apps (modal templates, tertiary containers, different activities etc.). It is one of the reasons I enjoy Constellation more, logic built into the model = faster time to value.
The Solution: Using Constellation’s “Create a case” Action
To get the behavior you want, you need to replace the pxCreateTopCase activity with the out-of-the-box Create a case action in your button’s action set. This action is specifically designed for Constellation and bundles the server-side creation with the client-side navigation.
- I would return to OOTB instead of using a DX component, there you can use a case wide action that is a process, which can have the “create case” smart shape. That would then naturally take on the OOTB UX for case creation.
Alternative solution: DX Component + “change stage”
You could look at other ways to trigger native case processing in the model. Look at the local action in the button changing stage (pxChangeStage activity), that changes to a stage that uses the “create case” smart shape. That should return you back to native OOTB UX for creating cases, which would return you to native Constellation components that would navigate to the open case.
IF you find a technical activity based solution, or someone else knows, please share with the community