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

Parent case don't show after complete local action

SA-17207

Summary


 

A flow in 7.1.8  spawning subcases in Local Actions when needed per business requirement. These subcases are routed to a different operator/workbasket. For example: operator only creates subcases, but does not own/process them. When the subcase are submitted all processes opened/completed can be seen in the Confirm Harness and returned to the main case.

 

User can't return to the parent case without showing all processes open/completed in the Confirm Harness and an extra click is needed and if the list is long. This increases the likelyhood of a user mistake because there are so many steps.


Error Messages



Not applicable


Steps to Reproduce



Add some local action to the shape and trying complete it.


Root Cause


This is normal behaviour of the harness in the application

Resolution



Perform the following local-change: 

1. Configure ticket for the assignment of the step that used to launch Local Actions spawning subprocesses
2. In the flow activity add new step after new subcase flow created:

Call @baseclass.SetTicket activity with (Parameter: <your ticket here>) 

Published January 31, 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