Child case created is not getting saved in my Work table
Hi,
I am creating a parent/cover case by a 'CreateCases' shape in my flow. In this flow shape, I mention the flow to process the parent case in the 'Starting Process' dropdown. Say Flow X.
In flow X, I am again using the 'CreateCases' shape and creating a child case this time.
I can see both cases are getting created in the tracer, but only the parent/cover case is getting saved in my work table.
There are no errors or exceptions in the tracer.
Could you please let me know why the child case is not saving ?
I even tried to call an activity and use commit with error handling. The activity executes without errors, but the child case is not in the work table.
Regards,
Rashmi
Accepted Solution
Commonwealth Bank Group
IN
Hi Venkat/Sarang,
A save was happening to the Work table only when I would call a custom activity in the flow (after both parent and child cases were created) and force a commit with 'Commit with error handling'.
I resolved this issue by replacing Obj-Save instead of Commit with error handling. Now both parent and child case are getting saved now. Although I get a Locking error, the work objects are getting saved to the work table.
Regards,
Rashmi
Commonwealth Bank Group
IN
Noticed a field call pxCoveredCount in the work table. This holds the number of covered work objects within this cover.
My Parent/cover case has this count as 1. So the child case is surely created.
But still cant find the child cases in my work table. (I am validating this by writing a report definition to pick all the pyIDs from my work table. I can see that the results contain only my parent cases and not the child cases.)
Any idea where they would be stored ?
Regards,
Rashmi
Updated: 16 Jun 2016 7:14 EDT
Pega Systems
IN
It is not always true that child case resides in a table which is mapped to a class group.
Please do a Test Connectivity from Class definition rule form for a child case (to know the table name).
See, whether a record is available in a that table for a child case.
Commonwealth Bank Group
IN
Hi Sarang,
My parent and child cases (both their classes) are mapped to the same work table.
I have written a report definition on this class to fetch me the pyID among a few other details like pxCoveredCount.
I only get parent cases when I run this RD.
Regards,
Rashmi
Commonwealth Bank Group
IN
No RD was created in the parent class. Here only parent cases were fetched.
But I have also tried with a child class RD.
With the child class RD, there are zero records fetched.
Regards,
Rashmi
Commonwealth Bank Group
IN
pzInsKey is same. For Example : -
Parent: ORG-EBISAPP-WORK VB-11
Child : ORG-EBISAPP-WORK FAD-11
pxObjClass like I mentioned earlier, are different. For Example : -
Parent: Org-EBISApp-Work-VB
Child : Org-EBISApp-Work-VB-FD
Updated: 16 Jun 2016 8:24 EDT
Pega Systems
IN
We need some more information to replicate the scenario.
Can you provide exact steps to replicate the issue with PRPC version ?
Commonwealth Bank Group
IN
Hi Sarang,
Below are the sequence of actions that I am doing. Request some urgent help please !!!
1) I have hosted a REST service in pega.
2) I call this service with the Advance REST client (for simulation).
3) When the request from the external system comes, the service runs and in turn the service activity of the service runs.
4) From that service activity I start a new flow to create a cover object. I use StartFlow activity. (For Eg: I am calling the 'syStartCase' flow of my case type VB)
5) The 'syStartCase' flow is started and the first flow shape (after the start shape off course) is a 'CreateCase' shape. I have specified my case type(VB) in the 'CreateCase' shape. In the process drop down I have given the flow 'CreateCoverCase' as the start process flow. ( I have given this 'CreateCoverCase' flow as well as the default 'pyStartCase' as starter flows in the pydefault of this case VB)
6) By now the cover case is already created. Then the flow 'CreateCoverCase' is launched. Here the first step is a utility, and I use 'ReassignToWorkBasket' to transfer my VB case to a default WB (routing not working).
7) The second shape after this utility is a spin off sub flow - 'CreateFADCase'
6) Then the 'CreateFADCase' is launched and I create a child case here in this flow.
No errors on the tracer !!!
Hi Sarang,
Below are the sequence of actions that I am doing. Request some urgent help please !!!
1) I have hosted a REST service in pega.
2) I call this service with the Advance REST client (for simulation).
3) When the request from the external system comes, the service runs and in turn the service activity of the service runs.
4) From that service activity I start a new flow to create a cover object. I use StartFlow activity. (For Eg: I am calling the 'syStartCase' flow of my case type VB)
5) The 'syStartCase' flow is started and the first flow shape (after the start shape off course) is a 'CreateCase' shape. I have specified my case type(VB) in the 'CreateCase' shape. In the process drop down I have given the flow 'CreateCoverCase' as the start process flow. ( I have given this 'CreateCoverCase' flow as well as the default 'pyStartCase' as starter flows in the pydefault of this case VB)
6) By now the cover case is already created. Then the flow 'CreateCoverCase' is launched. Here the first step is a utility, and I use 'ReassignToWorkBasket' to transfer my VB case to a default WB (routing not working).
7) The second shape after this utility is a spin off sub flow - 'CreateFADCase'
6) Then the 'CreateFADCase' is launched and I create a child case here in this flow.
No errors on the tracer !!!
I can see the Work objects/cases being created both VB and FAD cases. But the work table has only VB cases and doesn't have FAD child cases.
Need urgent help as I am not able to proceed
Regards,
Rashmi
Updated: 17 Jun 2016 2:45 EDT
Pega Systems
IN
Also, check the DB Query (using Tracer by setting Event Type to trace as DB Query) that gets fired for creating Child Case.
Accepted Solution
Commonwealth Bank Group
IN
Hi Venkat/Sarang,
A save was happening to the Work table only when I would call a custom activity in the flow (after both parent and child cases were created) and force a commit with 'Commit with error handling'.
I resolved this issue by replacing Obj-Save instead of Commit with error handling. Now both parent and child case are getting saved now. Although I get a Locking error, the work objects are getting saved to the work table.
Regards,
Rashmi