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

Screenflow back button going back to workbasket

SA-24657

Summary



In a screenflow, the start shape is configured to route to a workbasket. There are two assignment shapes present in the screenflow. When clicking the "Back" button on the second assignment to route back to the first assignment then closing the workobject, the item returns to the workbasket rather than staying on the worklist.

Error Messages



Not Applicable


Steps to Reproduce


 
  1. Create a screenflow and configure the start shape to route to a Workbasket.
  2. In the screen flow add two assignment shapes.
  3. Create a work object that uses the screenflow.
  4. Complete the first assignment and navigate to the second assignment.
  5. Click the "Back" button.
  6. Click the "Close" button on top of the screen.
  7. Click "save" in the pop-up.
  8. Observe that the workobject is routed back to workbasket instead of staying in current user's worklist.

Root Cause



An issue in the custom application code or rules
Defining routing for workbasket under the Start Shape of Screen Flow is not recommended.

Resolution



Instead of defining workbasket routing in the screen flow, define it before the Screen Flow sub process shape in Main flow which will assign the item to the particular workbasket. Set the Routing option under the start shape to ‘ToCurrentOperator’.

Published June 27, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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