Lock error occurs on submitting assignment when server quiesced
When a server is Quiesced, a Lock Lost error occurs and the user is unable to submit assignments. However, on stopping the Quiesce and setting the system status to Running, the user is able to submit the case.
You have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue.
Steps to Reproduce
- Work on an assignment. The node enters the Quiesce mode.
- Finish the assignment. The lock on the case is lost.
The error occurred because the Locking mode details are stored in the pyCaseUpdateInfo embedded page property in the work page. Since the pyCaseUpdateInfo is a Transient property, the data is no longer present as a result of the Quiesce process.
Perform the following local-change to persist the property:
- Override the pyCaseUpdateInfo property in the Case class.
- Unmark the property as Transient.