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

Unable to attach file after deleting the existing attachment



When user tries to attach a new document to work object after deleting any of the existing document, confirm harness is displayed in the modal window instead of attachment screen. User is facing this issue after upgrading to PRPC v7.1.6.

Error Messages

Not Applicable.

Steps to Reproduce

Step-1: Create work object by launching any out of the box flow

Step-2: Click attachment on the work object and add new file attachment. Once done, try to delete the same attached file.
Step-3: Click on add attachments link to add new attachment. This time, confirm harness is displayed on the modal window instead of attachment screen.

Root Cause

When user tries to delete attachment, out of the box activity ‘DeleteAttachment’ is called. In this activity, commit method is called explicitly followed by ‘show-harness’ to refresh harness. This is an available rule and user has created a custom version of this activity where call to ‘show-harness’ method is commented.

With this changes, whenever user tries to delete attachment, commit operation is performed and harness is not refreshed. Hence existing connection is stale and whenever user tries to perform new action (attaching new document), ‘StaleTransaction’ activity is called instead of original action which will display confirm harness by default.



Changes were performed in ‘DeleteAttachment’ activity by adding new step to call ‘Show-harness’ method after performing commit operation. With this changes, reported issue is addressed. However, calling ‘show-harness’ is taking long time to reload the screen at user portal and user is not interested with reloading harness. To avoid relaoding harness, suggested user to launch the modal dialog which would ask for delete confirmation on-click of trash button and in post processing activity of ‘Delete Confirmation’ flow action, we can delete the attachment by calling ‘DeleteAttachment’ activity. This change has worked for the user. 

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