Theme Cosmos flow action displays in popup after local action
Pega Infinity '24.1.1 & Theme Cosmos 05.01
We have a case type that has multiple stages and each stage contains a screen flow. We have also defined the case-wide action 'Change Stage' on the case definition.
When the user selects 'Change Stage', a popup is presented that allows the user to select the target stage. On selecting the stage and submitting it, the stage is changed correctly but the flow action from the new stage is displayed in the popup, not in the main harness.
What SHOULD happen is that the popup closes and the flow action from the new stage is displayed in the main area.
Any ideas on how to overcome this?
As an aside, what I have seen is that:
- if the work object is opened from the Go icon on the home screen, then the change stage action and the subsequent flow action are displayed in the main area
- if the work object is displayed in 'review' mode and the assignment is opened from the Go icon in the assignment list then the change stage action and the subsequent flow action are displayed in the popup, as per the issue
- if the change stage is actioned from the 'review' screen, the action is displayed in the popup and when submitted, it closes and the review screen is refreshed, showing the new stage. The new flow action is not opened
So at least 3 different outcomes for the user when doing the same thing. Way too confusing.
Pega Infinity '24.1.1 & Theme Cosmos 05.01
We have a case type that has multiple stages and each stage contains a screen flow. We have also defined the case-wide action 'Change Stage' on the case definition.
When the user selects 'Change Stage', a popup is presented that allows the user to select the target stage. On selecting the stage and submitting it, the stage is changed correctly but the flow action from the new stage is displayed in the popup, not in the main harness.
What SHOULD happen is that the popup closes and the flow action from the new stage is displayed in the main area.
Any ideas on how to overcome this?
As an aside, what I have seen is that:
- if the work object is opened from the Go icon on the home screen, then the change stage action and the subsequent flow action are displayed in the main area
- if the work object is displayed in 'review' mode and the assignment is opened from the Go icon in the assignment list then the change stage action and the subsequent flow action are displayed in the popup, as per the issue
- if the change stage is actioned from the 'review' screen, the action is displayed in the popup and when submitted, it closes and the review screen is refreshed, showing the new stage. The new flow action is not opened
So at least 3 different outcomes for the user when doing the same thing. Way too confusing.
Updated: 13 Aug 2024 11:44 EDT
Pegasystems Inc.
GB
@andwww It seems like the issue you're experiencing is related to the handling of the Ajax container in Theme Cosmos. According to the Pega Platform 8.7.6 Patch Resolved Issues, there was a similar issue where the screen flow was displayed inside a pop-up box instead of full screen. This was resolved by updating the harness handling so the Ajax container would close and the second stage would open in the main action area within the Cosmos Portal. You might want to ensure that your configuration aligns with this update.
Additionally, in Theme Cosmos, case-wide local actions and flow actions are typically opened in the tertiary Ajax container in a dialog container for assignment processing. You may need to review your configuration to ensure that the flow action from the new stage is set to open in the main area rather than the tertiary Ajax container.
The variations in the behavior of flow actions and local actions in Theme Cosmos are due to the different contexts in which the work object (wo) is opened. Here are the reasons for the different outcomes you are experiencing:
@andwww It seems like the issue you're experiencing is related to the handling of the Ajax container in Theme Cosmos. According to the Pega Platform 8.7.6 Patch Resolved Issues, there was a similar issue where the screen flow was displayed inside a pop-up box instead of full screen. This was resolved by updating the harness handling so the Ajax container would close and the second stage would open in the main action area within the Cosmos Portal. You might want to ensure that your configuration aligns with this update.
Additionally, in Theme Cosmos, case-wide local actions and flow actions are typically opened in the tertiary Ajax container in a dialog container for assignment processing. You may need to review your configuration to ensure that the flow action from the new stage is set to open in the main area rather than the tertiary Ajax container.
The variations in the behavior of flow actions and local actions in Theme Cosmos are due to the different contexts in which the work object (wo) is opened. Here are the reasons for the different outcomes you are experiencing:
1. **Work Object Opened from Go Icon on Home Screen**: When a work object is opened from the Go button on the home todo worklist, it opens in perform mode directly. The harness used is the perform harness, and both case-wide local actions and flow actions are opened in the main area inside the primary ajax container for assignment processing. This is expected behavior as the Go button uses the 'OpenAssignment' action API.
2. **Work Object Displayed in 'Review' Mode**: When a work object is opened in review mode (e.g., using 'OpenWorkByHandle' action), the top-level harness is the review harness. In this mode, flow actions are opened in the main area inside the primary ajax container, while case-wide local actions are opened in the tertiary ajax container in a dialog container. This is why the change stage action and subsequent flow action are displayed in a popup.
3. **Change Stage Actioned from 'Review' Screen**: When the change stage action is performed from the review screen, it is displayed in a popup. Upon submission, the popup closes, and the review screen is refreshed to show the new stage. However, the new flow action is not opened automatically in this context.\n\nThese variations are due to the different configurations and expected behaviors of the harnesses and containers used in Theme Cosmos for different actions and contexts
To ensure the flow action from the new stage is displayed in the main harness, modify the Navigation Rule and update the Action API to target the primary AJAX container (acprimary).
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Platform 8.7.6 Patch Resolved Issues
Case wide local actions/flow actions behaviour in theme cosmos
Cases/work objects processing behavior and configuration in theme cosmos applications
If you need a more detailed analysis please log a support issue via the msp and provide th INC id here.