Hi,we have a requirement to update the status of the child case to “Pending” from “Pending-Fulfilment” when we are updating the status of the parent case.I am calling a post processing activity in the flow action and i am using Update status activity to update the case status of the parent case but for child case i tried to use Obj browse then looping through the page results and using obj open by handle to update .It didnt work.Any suggestion please?
Iterate pxCoveredInskeys(has pzInskey for child cases) in the Parent case and use UpdateStatus OOTB activity to update the status on the child case based on your requirement.
Please find teh attached screenshots for oyur reference
Hi @TanyaS58,
Your approach should have worked, can you check if during obj open by handle you are taking the lock or not ? You need a lock on child case to update. Also see if you are doing obj-save or not . Try to trace and see what error you are facing.
- Secondly, you can improve your logic by avoiding obj-browse and using the pxCoveredInskeys value list. Just loop through this value list and do Obj-Open by handle and then update & save . Do not forget to implement exception handling
There is another way to do it and I will prefer using it:-
- In flow action post activity, I will use OOTB pzStandard Queue Processor to update the child case in background batch processing. Here, Pega will automatically take care of the case update /save & commit in the backend.
@SnehasisP0085 thanks for sharing the alternate way as well.And yes I am using the lock.However in tracer i can see that my cases are not getting opened as I can see an error in the tracer that failed open the instance “FMO-47”(which is my child case id).
@TanyaS58 Hi Tanya, you mentioned that you are using Obj-Open by handle and the failure message is "failed open the instance “FMO-47” . I think you are only passing the pyID and not the pzInsKey.
Can you share the screenshot of your configuration and screenshot from tracer ?
As I am replying after a long time, I guess you might have already fixed the problem.
@SnehasisP0085 yes apologies the issue got resolved as I used an OOTB Activity pzUpdateWrapper