Close popover
Jonathan Kelly (Pega_Jonathan)
Director, Solutions Consulting - Healthcare
Pega_Jonathan Member since 2008 1 post
Posted: March 17, 2016
Last activity: March 17, 2016

Best design approach for a Long-running case

I am trying to determine the best approach for supporting long-running (potentially decades, yes decades) cases.

Use case:  Consider a Franchisor / Franchisee relationship.  The Franchisor would like to periodically create and track cases related to each Franchisee. 

I have chosen to support this by creating a case "Franchisee". 

That case has three basic stages:

  1. Create
  2. Active
  3. Inactive

So as a new franchisee comes on board, they would go through the Create stage, and when that is completed they would reside in the Active stage until such time as their franchise license was revoked.  At that point they would move to the Inactive stage and ultimately resolve-complete.


What is the best way to have a case sit in a 'wait state' - allowing someone to open & review it and add sub-cases to it, but then at some point choose to initiate the inactivation stage? 

Should I simply create a very high likelihood (e.g. default) flow action that connects back to it's assignment shape, and then a second, lower likelihood one that will ask some information to initiate the Inactivation process?  I can use a Validation rule to ensure we don't enter the final stage without some confirmation info being provided.



Is there a 'more correct' way to do this?

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.