Question
Pegasystems Inc.
JP
Last activity: 29 May 2016 23:20 EDT
when user B tries to open his/her assignment, PRPC says the work is still locked and under modification by user A
Our customer (on 7.1.9 / PegaCloud production environment) is experiencing the similar issue - not sure it's the same.
After user A finishes his assignment & submits it, PRPC routes it to user B then.
The issue is that when user B tries to open his/her assignment, PRPC says the work is still locked and under modification by user A.
Is this symptom potentially the same as what's explained above, if yes, does user B need to wait for 2 hours max (or 30 sec max?)
*Default locking is selected as case lock configuration.
Message was edited by: Marissa Rogers - branched to its own thread, added category
Pegasystems
US
Pegasystems Inc.
JP
Thanks Eric.
It doesn't seem to be an issue of harness. Actually it's configured to show Confirm harness after finishing the assignment, and seems to be behaving in that way.
I'm still doubting it's caused by a time lag of lock release propagation across the nodes. Any thoughts?
Pegasystems
US
You could try turning on "lock" events in the pega tracer to see and verify when the lock is being taken and when it is released.
Also, you can get some detail about the locks from some landing pages. Try designer studio > process and rules > tools > work admin
You'll see some choices there for looking at the locks. /Eric
Pegasystems Inc.
JP
Thanks Eric! will ask customer to verify it.
if user A is still viewing the assignment in the perform harness, that's why it is still locked, and user A should get in the habit of closing the window if they expect user B to handle the work, to make sure it doesn't stay locked.
However, I'm a little puzzled about why user A is still viewing the assignment in the perform harness after routing it to user B. I would think the normal behavior after such a routing would be for user A to be viewing the assignment in the review harness. You should check what's going on with your flow-harness settings. /Eric