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

pyWithdrawfromNav doesn't work properly



User has configured a pyWithdrawFromNav as local action over a button and followed by refresh current harness.

On click of button, everything looks fine but if when closed and open the workobject, it is getting reverted to a previous state with all the existing assignments.

Error Messages

Not Applicable

Steps to Reproduce

  1. Configure a button.
  2. In the actions use pyWithdrawFromNav followed by Refresh current harness.
  3. Click on the button and close the Work object.
  4. Open the work object again to see that the assignments are still present.

Root Cause

PyWithdrawFromNav flowaction is supposed to be used as a local action on an assignment.

If it is used in such way, a commit is issued by Pega automatically and thus committing the changes with out any explicit commit in pyWithdrawFromNav flow action.

As it has been used on a button, user need to have an explicit commit for the changes to reflect properly.


Perform the following local-change steps:
  1. Save as pyInvokeForceWithdraw activity into your application RuleSet.
  2. Expand step 3 and add an extra property set as below:
Param.Commit to true

The above change should cause the activity to issue a commit explicitly thus solving the issue.

Published March 22, 2018 - 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