Close popover
Jack Reynolds (KayakJack)
Lead Architect
KayakJack Member since 2010 1 post
Posted: March 26, 2019
Last activity: March 29, 2019

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?

Case Management
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.