Do I need a parent case just to initiate subcases? Can I drop the parent case or its wo?
I currently have a 'Start Communication' application that creates a 'communication' case and work object as soon as a user accesses the system. This user would select a customer and initiate any number of sub cases, all of which are worked/processed/resolved in separate Pega applications. There is no need for an SLA on this 'communication' parent case. There is no coming back to this parent case if there is an issue with a subcase.
All the subcases have their own workflow and SLA's.
Our architect (non-Pega) wants to remove the parent case and/or its work object.
Is this doable?
I can see no benefit or need for this 'communication' parent case. It serves no purpose.
Can we remove this parent case?
What would be a general level of effort to do that?
What gotcha's or issues could I run into?
Can I keep the parent case and just remove it's work object, so we aren't writing to the database for this parent case?
Independent
US
There is some minor inheritance in that:
User comes in and Case A is created. User selects customer and that is saved to Case A (parent case).
one at a time, user selects subcase(s) he will create for that customer. The parent case's customer info is propagated down to the child cases. That is the only inheritance.
It just seems like the parent case is doing absolutely nothing besides passing down the selected customer. I can do that outside of a case.
Pegasystems Inc.
FR
I don't have the overall picture of your configuration and business requirements but I think I would keep this parent case. It might be useful to have one in the future maybe.
I don't know. this is just a thought.