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

Assignments are not getting deleted though the case is resolved



Users observe that after canceling a flow running in a modal window, and then re-entering the flow and submitting, an extra assignment is being left behind.

Error Messages

Not Applicable

Steps to Reproduce

  1. Launch a work object.
  2. Click on a link to open a flow on the current work page.
  3. Click on a button configured as a modal button for the action cancel.
  4. Observe the launched flow still exists on the work page.

Root Cause

An issue in the custom application code or rules. The modal button (Cancel) is designed to clean up after launching a flow action but it doesn't properly clean up a flow launched in a modal window.


Perform the following local-change:
Update the cancel button for your ModalTemplate to be configured as follows:
  • The full text in the OnClick is : "pega.u.d.launchFlow.handleModalCancel()"

Suggest Edit

Published June 17, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

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