Support Article
Flow action is not performed on Resume flow
SA-10318
Summary
A flow contains an flow action which is secured (not displayed to users but can be processed by the system).
When user performs any local action, newAssignPage is saved in the database. When ResumeFlow activity is called by SendCorr agent to resume flow using this secured action, the list of actions are not populated in the requestor context. Instead, it opens the newAssignPage which was saved when user performed the local action. So, the desired flow action using which the flow must resume is missing on the newAssignPage.
This action is assumed as local action and performed. As a result, the flow does not progress to the next assignment.
Error Messages
Not Applicable
Steps to Reproduce
1. A case has two assignments on two different flows.
2. The flow action AdvanceFlowThroughTickler is configured to work only with custom agent (first assignment) sends correspondence. The Send activity is configured to resume flow on the other flow using flow action AdvanceFlowThroughTickler.
3. Open the second assignment and perform Reassign local action on the case.
4.Perform the first assignment to send email correspondence. The agent activity sends the correspondence and Resume flow from the second flow using flow action AdvanceFlowThroughTickler.
Root Cause
The issue is due to persistence of pyAssignActions of the AssignmentPage. Due to this, when the other user/agent having different privileges for the Flow Actions shows up the same list of pyAsssignActions rendered by the earlier user.
Ideally, the pyAssignActions must not be persisted but repopulated.
Resolution
This issue is resolved by HFix-22219.
Published June 12, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.