Case processing
Hi Everyone!
I have a parent case, in which on section-on click of Add button a child case gets created. But if a user clicks on Add Button and then exits by any means without entering any data a record(with a new case id) is created for the Child case that is not editable. How to stop creating a new case id until the user click on submit.
Thanks in Advance!
***Edited by Moderator: Pallavi to update platform capability tags***
Hi,
Thanks for the reply!
Yes, on click of the button- the user gets child case displayed and can enter the details and submit. if not submitted,I dont want that record to be saved.
and the configuration for skip the create harness is already disabled.
Thanks.
What Pega version are you using here (and any Pega applications)? Also, What action are you using on the button to create the sub case?
Maybe you can't disable the skip new harness for a sub case. I would suggest testing the starting flow for your sub case to be a temporary object, and then persist it later with the persist case smart shape.
Hi Divya,
Just follow as below
1. open case type(pyDefault)
2. pyDefault -first tab Process click on starting process pyStartCase
3.pyStartcase- Process tab-Case creation settings where you can set case as a temporary object
and make sure to persist the case
PFA
Hi,
Thanks for the reply,
On selecting the check box in pystartcase -> temporary object.
On click of add button on UI, i am getting a pop-up "Empty Assignment Key" , why it is seen and can you help me in resolving it?
Thanks in Advance.
Hi DivyaP,
Make sure the persist the case(persistcase smart shape), until unless data is not stored to PegaDATA you don't have assignment key and that is the reason your getting empty assignment key
Hi,
even if i persist the case, i still see "empty assignment key" in popup on click of button on UI.
Thanks.
Hi,
Adding a few points from Pega Help on temporary work objects.
- Temporary work items do not have a work item ID.
- Temporary work items cannot be members of a cover.
So this is pega feature not to support child case as temporary work objects. In my case, the assignments never loaded on checking the 'Temporary object' checkbox (when instantiating case from the parent) whereas if I run the child case as Standalone as temp object, the flow continued as normal.
When you click the button does the user get the new child case displayed? It sounds like the case may be configured to skip the create harness, so you could try disabling that in the case settings. Alternatively could you configure the child as a temporary case, and then use a persist case shape in the flow to save it once you reach the desired point in the flow?