Question
TECH MAHINDRA
IN
Last activity: 28 Dec 2017 1:15 EST
Dummy/orphan Work Objects
Hi ,
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.
Accepted Solution
TECH MAHINDRA
IN
Hi ,
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.
Pegasystems Inc.
IN
Hi Manikantan,
Seems to be intresting!!
Since you are not aware how are they getting created, use DB to check the pxCreateOperator, pxUpdateSystemID and pxCreateDateTime to understand how it would have been created.
Getting to know about user would be of great help(Its more likely to be a batch/Agent user I think).
After you have understanding on how it is getting created, delete these directly from DB.
Regards,
Ujjwal
Pegasystems Inc.
IN
Hi Manikantan,
Can you send some screen shot related to this.
Screen Print of clipboard should do.
Can you share pzInskey for normal Work Object and for this Work Object.
Does all the Dummy WorkObject has same pzInskey(Which it can not be) by any chance.
Regards,
Ujjwal
Pegasystems Inc.
IN
Hi Manikantan,
Its difficult to suggest as this has happen only once and also with very few info.
You can delete this WO from back-end to stop facing any further issue due to this.
Thanks,
Ujjwal
TECH MAHINDRA
IN
Hi Ujjwal,
As of now we are deleting WO , but it is getting created daily and we are unable to trace it as we are with limited data on that record.
Pegasystems Inc.
IN
Hi Manikantan,
If you are aware of the time it is getting created then you could use Global DB trace to understand all the operation that has happened during that time and get good insight on the rootcause.
Thanks,
Ujjwal
Accepted Solution
TECH MAHINDRA
IN
Hi ,
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.
Pegasystems Inc.
IN
Good Observation :)
However obj-open-by-handle will throw exception if handle given is blank.
With Obj-Open it is indeed possible.
Good to validate all the scenario where insKey can go blank.
Also apart from Obj-Open I think you can also check for Page-New, Page-Rename where a incomplete page can be created and saved.
Regards,
Ujjwal