I am new to Pega 7.1.8 as well as for case management and doing a POC, As part of it, there is a parent object and initiates multiple subcase of same type based on the user selection in the main flow. In the main flow, there is a UI that displays a checkbox for each of the value in the page list. Each page in the page list has the information about the subcase assignment & few other data. Each of the subflow as to be assigned to the person that is associated with the selection in the main flow. My question is how will i design such a scenario using case manager.
In the Case Explorer you will need to select the parent case from which you want to propagate properties and click the Details tab. On the Details tab you have the option to propagate from the parent case page to its subcases. You will also have the ability to apply a data transform rule which provide you with additional options.
There is a UI that displays a list of subcases that could be created.
The items in the pagelist (SubCasePageList) contain a property that holds the name of the operator (For example, AssignedOperator) that the assignment in the sub case should be routed to.
After the user checks off the subcases that should be created they submit the form.
There is a Utility that iterates through the pagelist and creates the subcases.
Is this correct? If not please provide more details.
If this is your use case then the utility that creates the subcases can copy the item in the pagelist to a page property (SubCasePage) and the data propagation in the case designer would propagate this page to a page of the same type in the subcase. In addition the assignment in the subcase would reference .SubCasePage.AssignedOperator in the assignment. Route to: Operator; instead of selecting an operator, reference the property, .SubCasePage.AssignOperator.
Thanks for everyone information and it worked finally. I followed the above steps and it worked fine.I still have two more questions w.r.t Pega 7.
In order to resolove the parent case when the subcase gets resolved. i set the ticket allcovered resolved in the resolution stage but it did not work. I found a workaround to apply that manually in each of the subcase resolve stage.
Second one i create the parent case and assign it to the another workbasket. Though i have access role define for each actor when i submit the case to the operator it gets assigned but it also shows an editiable assignment for the same operator. i checked the tracer of the pega rules and i dont feel that they check for the access when displaying the case contents for the workbasket. Am i missing something here?