Losing locks on open work objects
I am working on an application that has a parent work object, with a tree of many child work objects. It is set up so that the parent is not locked when the children are opened - so that different users can work on different children in parallel. At the end of processing some of the children, an activity runs that opens and updates the parent very briefly.
If the parent is already opened by another user, Obj-Open-By-Handle reports a locking error, which we catch and create a page-error (so the user can re-try after the other user is finished). This works well and the users are happy with the results.
But we have problems when the parent object is open in another Tab of the same browser. In this case Obj-Open-By-Handle in the child thread does not report an error, so we go ahead and update the parent object, and save it. The flow commits the change & the lock is lost when we return to the tab with the parent object.
Is there any way to detect this condition in advance?
Accepted Solution
PEG
GB
I'm not too sure whether retaining the lock would be a good thing to do.
If you've already loaded the work object on a tab, and there is a lock then it may be the case that the operator has already changed some of that data in the browser.
If you subsequently try to run some activity as the same requestor, and that is presumably updating some data, then this would mean that the information on the tab is now stale.
So if you still had the lock for the work object opened in the tab, and you saved the data, then there is a risk that you'll be overwriting some of the data that you'd set in the activity.
Unless I've misunderstood the scenario.
Pegasystems Inc.
IN
While calling Obj-Open-By-Handle you can also pass LockInfoPage param and check the value on that page for which requestor and user actually holds the lock. If it is the same then you can apply some logic.
Let us know if this helps :)
Accenture Australia
AU
Hi Talb,
Please refer this below link for more about the locking concepts in pega.
https://pdn.pega.com/about-pega-7-case-locking
Thank you
Accepted Solution
PEG
GB
I'm not too sure whether retaining the lock would be a good thing to do.
If you've already loaded the work object on a tab, and there is a lock then it may be the case that the operator has already changed some of that data in the browser.
If you subsequently try to run some activity as the same requestor, and that is presumably updating some data, then this would mean that the information on the tab is now stale.
So if you still had the lock for the work object opened in the tab, and you saved the data, then there is a risk that you'll be overwriting some of the data that you'd set in the activity.
Unless I've misunderstood the scenario.
Pegasystems Inc.
JP
When we open the second PRPC tab, we want to know if the parent object is locked (by us) but PRPC doesn't tell us. It lets us re-lock it without telling us that we already have a lock on it & then when we commit the object the lock is closed. When we return to the first tab, we no longer have a lock. How can we get PRPC to stop letting us move the lock to the second tab? If we already have an object locked in one tab, we don't want to be able to open it in another tab at the same time.