Question
IBM
CN
Last activity: 5 Feb 2024 10:24 EST
"Wait" step stuck at a flow gen by split for each
"Wait" step stuck at a flow gen by split for each
Scenario:
split for each: gen several flows per a page list, then, in each flow, I add a Wait step (before an assignment step), however, the Wait step can not wake up after time expired.
Wait step works normally in a standard flow that in a stage of case type.
May I know if any one else meet such issue? Any solution? Thanks.
Accepted Solution
IBM
CN
Solved, pls refer the solution in this topic:
also this topic:
https://support.pega.com/question/wait-shape-issue-split-each-flow-assignment-getting-corrupted
Details:
the recommended solution is:
///
Perform the following local-change:
- Use the Assignment shape instead of the Wait shape
- Route it to [email protected] that is similar to the Wait shape so that no one can access the assignment
- Define a Service Level Agreement (SLA) on the assignment with the Goal as 30 minutes or as per the requirement
- Write an escalation activity which invokes ResumeFlow, passes the appropriate flow action and sets the Step page to pyWorkPage when invoking ResumeFlow
///
Important supplement: need set para calledFromServiceLevel to true for ResumeFlow.
What I have done:
Follow above steps 1 to 3 in the flow MySplitForEach that generated by split for each: In the flow I add an assignment with [email protected] before my original assignment, with SLA MyTestSplitSLA, followed by flow action pyContinueAfterWait.
In SLA MyTestSplitSLA, goal expire: do nothing, deadline expire: run activity ResumeFlowWrapper in which only one step:
Solved, pls refer the solution in this topic:
also this topic:
https://support.pega.com/question/wait-shape-issue-split-each-flow-assignment-getting-corrupted
Details:
the recommended solution is:
///
Perform the following local-change:
- Use the Assignment shape instead of the Wait shape
- Route it to [email protected] that is similar to the Wait shape so that no one can access the assignment
- Define a Service Level Agreement (SLA) on the assignment with the Goal as 30 minutes or as per the requirement
- Write an escalation activity which invokes ResumeFlow, passes the appropriate flow action and sets the Step page to pyWorkPage when invoking ResumeFlow
///
Important supplement: need set para calledFromServiceLevel to true for ResumeFlow.
What I have done:
Follow above steps 1 to 3 in the flow MySplitForEach that generated by split for each: In the flow I add an assignment with [email protected] before my original assignment, with SLA MyTestSplitSLA, followed by flow action pyContinueAfterWait.
In SLA MyTestSplitSLA, goal expire: do nothing, deadline expire: run activity ResumeFlowWrapper in which only one step:
In step page pyWorkPage (defined as case type class in "Pages & Classes"), call ResumeFlow, parameters:
flowAction: pyContinueAfterWait
flowName: MySplitForEach
calledFromServiceLevel: true
Need further test how about if the case is locked (one assignment is open) when SLA deadline expire. Not sure if this will prevent the flow is advanced.
Accepted Solution
IBM
CN
Solved, pls refer the solution in this topic:
also this topic:
https://support.pega.com/question/wait-shape-issue-split-each-flow-assignment-getting-corrupted
Details:
the recommended solution is:
///
Perform the following local-change:
- Use the Assignment shape instead of the Wait shape
- Route it to [email protected] that is similar to the Wait shape so that no one can access the assignment
- Define a Service Level Agreement (SLA) on the assignment with the Goal as 30 minutes or as per the requirement
- Write an escalation activity which invokes ResumeFlow, passes the appropriate flow action and sets the Step page to pyWorkPage when invoking ResumeFlow
///
Important supplement: need set para calledFromServiceLevel to true for ResumeFlow.
What I have done:
Follow above steps 1 to 3 in the flow MySplitForEach that generated by split for each: In the flow I add an assignment with [email protected] before my original assignment, with SLA MyTestSplitSLA, followed by flow action pyContinueAfterWait.
In SLA MyTestSplitSLA, goal expire: do nothing, deadline expire: run activity ResumeFlowWrapper in which only one step:
Solved, pls refer the solution in this topic:
also this topic:
https://support.pega.com/question/wait-shape-issue-split-each-flow-assignment-getting-corrupted
Details:
the recommended solution is:
///
Perform the following local-change:
- Use the Assignment shape instead of the Wait shape
- Route it to [email protected] that is similar to the Wait shape so that no one can access the assignment
- Define a Service Level Agreement (SLA) on the assignment with the Goal as 30 minutes or as per the requirement
- Write an escalation activity which invokes ResumeFlow, passes the appropriate flow action and sets the Step page to pyWorkPage when invoking ResumeFlow
///
Important supplement: need set para calledFromServiceLevel to true for ResumeFlow.
What I have done:
Follow above steps 1 to 3 in the flow MySplitForEach that generated by split for each: In the flow I add an assignment with [email protected] before my original assignment, with SLA MyTestSplitSLA, followed by flow action pyContinueAfterWait.
In SLA MyTestSplitSLA, goal expire: do nothing, deadline expire: run activity ResumeFlowWrapper in which only one step:
In step page pyWorkPage (defined as case type class in "Pages & Classes"), call ResumeFlow, parameters:
flowAction: pyContinueAfterWait
flowName: MySplitForEach
calledFromServiceLevel: true
Need further test how about if the case is locked (one assignment is open) when SLA deadline expire. Not sure if this will prevent the flow is advanced.