Lock on case is not released even after creating WO
User A creates a contact and tries to submit that contact and results that on the confirm harness.
At the same time when the user B logs in to the same portal from other browser and opens the WorkObject (WO) that is created earlier by user A, perform edit and try to submit the changes on the WO, then the error comes up saying that the work object is being modified by User A.
"WO is currently being modified by User A"
WO is currently being modified by User A
Steps to Reproduce
1. Create a contact from User A.
2. Create and observe the confirm harness for the contact created.
3. Login into the same portal in different browser with user B.
4. Open the contact that was created by User A, try editing and saving the same contact.
5. Observe the error on screen.
ROOT CAUSE & RESOLUTIONIdeally, if there is any assignment in confirm harness, then the user will have the lock on that particular object for specific time based on the locking mechanism specified in the case type rule either default or optimistic.
In the above case, since the user configured it as default locking, the user who is on the assignment will have lock on the work object for around 30 minutes.
Behavior of confirm harness
There will be an entry in sys_locks table for that particular user because the confirm harness displays the form details in read-only but has the user actions such as Submit and Cancel to perform which processes the assignment or case.
Therefore it acquires the lock on Confirm harness whether or not the check box "Look for an assignment after create" in the flow is checked.
But then it all depends on how the flow is configured.