Support Article

Error message comes on Harness after displaying lock popup



When user drags an assignment or WorkObject to a workbasket, redundant locking messages are shown.

This happens when Users refresh the WorkObject using Out-of-the-box (OOTB) Refresh button in the Dashboard. 

Error Messages

Label:** Cannot obtain a lock on instance ------- AA-27, as Requestor -------  already has the lock

Steps to Reproduce

1. User A, logs in the manager portal and opens workobject1 (Open WO A-8). 
2. User B, logs into the manager portal and opens User A's Worklist. 
3. User B, now tries to drag the same WO A-8 and tries to put it into another Workbasket. A pop us comes stating that the lock on WO A-8 is acquired by some one else(expected). 
4. Now, User B, refreshes the worklist and they observe the the Harness displays the same error. 
5. Observe that the error persist on the clipboard. 

Root Cause

When the user does drag and drop, then Pega sets a property set messages on PrimaryPage in pxTransferAssignment on failure.

And when control returns to pxTransferAssignmentWrapper Pega shows the failure on alert window. 



Apply HFix-30030.

Change that is included in the HFix: After the messages are copied to alert window and when control is returned back to pxTransferAssigmentWrapper activity, user can clear the messages if the transfer fails.


Published October 28, 2016 - Updated November 21, 2016

Have a question? Get answers now.

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