Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Wait shape used in Split for Each flow behaves incorrectly

SA-85937

Summary



A process flow is configured with a Split For Each shape and the Wait shape is used in the Split for Each flow. However, an error occurs when the Wait deadline is reached and the ServiceLevelEvents agent resumes the flow. The pyWorkPage.ChannelList(1) displays on the Step page in the trace.


Error Messages



This assignment has been corrupted and processing cannot proceed.


Steps to Reproduce

  1. Use a Split for Each shape and invoke a flow in it
  2. Use a Wait shape in the flow with reference date time
  3. Verify whether the flow advances to the next step when the deadline is reached


Root Cause



A defect in Pegasystems’ code or rules. The error occurs since the ExecuteSLA activity uses interestPage to execute the escalation activity. In this case, interestPage is pyWorkPage.ChannelList(1) which does not have the flow data present on it.


Resolution

Perform the following local-change:
  1. Use the Assignment shape instead of the Wait shape 
  2. Route it to [email protected] that is similar to the Wait shape so that no one can access the assignment
  3. Define a Service Level Agreement (SLA) on the assignment with the Goal as 30 minutes or as per the requirement 
  4. Write an escalation activity which invokes ResumeFlow, passes the appropriate flow action and sets the Step page to pyWorkPage when invoking ResumeFlow

 

Suggest Edit

Published December 16, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us