Posted: 7 Dec 2017 2:27 EST Last activity: 28 Dec 2017 1:15 EST
Dummy/orphan Work Objects
In our application ,anonymously the dummy work object is being created i.e., having value only for pzinskey(Work pool class with out any WO id) and null in all other properties.
Due to this if any requestor does obj-open with key as null, that requestor is able to open and acquire lock on the dummy instance. Due to this lock ,we are facing many exceptions in other scenarios like creating child cases using createworkpage etc .So please suggest if some one faced similar issues before and also share the scenarios where actually these orphan work objects may get created.
Identified one scenario which can create orphan WO. i.e. when ever we try to open any WO using obj-open or obj-open-by-handle methods and unfortunately if the key is passed as null and if we are unable to handle that obj fail exception properly then the orphan WO will get created.
Did small POC and tried to replicate this scenario. Attached the document for reference.
Resolution for this issue is to we need to check if key is having value or not before opening WO.
Hope this helps and share if any other scenarios may also cause this issue.