Not able to aquire lock of a child case with Obj-Refresh-And-Lock
Hi,
I am trying to do an Obj-Save of a parent case (VB-1) and a child case (FAD-1) through a custom activity called after creating both the cases through the 'CreateCase' shape in the flow.
I get a lock error for the child case while I try an 'Obj-Save' so I decided to acquire the lock of the child case by using 'Obj-Refresh-And-Lock'.
But in the 'Obj-Refresh-And-Lock' step, I get the error seen in the attachment.
I have made the locking of the parent case to optimistic locking in the settings tab and I know that the child case inherits its locking features from the parent.
I have also checked the 'Do not lock the parent case when the child case is processing' in the pydefault of the parent case.
I still get the same locking error. any suggestions ?
Regards,
Rashmi
Message was edited by: Marissa Rogers - added category
Accepted Solution
Commonwealth Bank Group
IN
Hi,
I noticed that just be create case shape, the created cases are not being saved on to my work table. That is why I am forcing a commit on them.
I have solved this issue by removing the 'WriteNow' check box from obj-Save and then using 'commit with error handling' in the next step.
Now I can see both the parent case and the child case in my work table.
Regards,
Rashmi
Pegasystems Inc.
IN
Hi Rashmi, Good morning!
>>> I get a lock error for the child case while I try an 'Obj-Save' so I decided to acquire the lock of the child case by using 'Obj-Refresh-And-Lock'.
- method Obj-Refresh-And-Lock tries to reload the workobject from DB to acquire lock
-
and while doing it is not able to find the child case in DB.
-
the primary page learnt from screenshot is iterationPage which is constructed during pxAddChildWork
- so I doubt the persistence of child object record in DB
- so I doubt the persistence of child object record in DB
-
the primary page learnt from screenshot is iterationPage which is constructed during pxAddChildWork
-
and while doing it is not able to find the child case in DB.
>>> I am trying to do an Obj-Save of a parent case (VB-1) and a child case (FAD-1) through a custom activity called after creating both the cases through the 'CreateCase' shape in the flow.
- flow smat shape 'createcase' wouldn't cause the lock issue.
- could you please help
- why do we need an Obj-Save explicitly just after the case creation?
- can we quick test by commenting the custom activity where it issues obj-save?
Please share your thoughts/comments, Thank you!
psahukaru
Accepted Solution
Commonwealth Bank Group
IN
Hi,
I noticed that just be create case shape, the created cases are not being saved on to my work table. That is why I am forcing a commit on them.
I have solved this issue by removing the 'WriteNow' check box from obj-Save and then using 'commit with error handling' in the next step.
Now I can see both the parent case and the child case in my work table.
Regards,
Rashmi