In-Flight Case Migration in Production from one version to next

I want to know the DOs/DONTs of migrating OPEN/IN-FLIGHT Cases from one version to next in production.

Is this something that is encouraged by PEGA? In my business whenever we roll out new features, our stakeholders want new features applied to existing in-flight Cases as well. This warrants a migration.

We have had discussions in our team (with our pega SMEs) around implementing a migration solution. So far, all options available appear either too arduous or in some situation there aren't any solution options at all.

I thought of reaching out to this community for guidance. Is in-flight Case Migration encourage as a pattern? And what are some of the best practices in this space?

Appreciate any guidance/inputs.


Keep up to date on this post and subscribe to comments

July 17, 2019 - 7:47am

Inflight cases generally will have problem majorly when the Flow rules involved in the case life cycle are changed. That is one of the important best practice that need to be followed. Even we have to be sure about adding new Stages or removing any existing stages.

All other rules like parties or Casetype rule configuration changes will all get applied safely even for the old cases that are created before changes.

July 17, 2019 - 9:48am

Refer LSA course > handling flow changes for cases in-flight topic. It provides information on the same. May be helpful

July 21, 2019 - 10:10pm

Thanks so much. I think have sufficient direction & guidance to finalise an approach to tackle in-flight cases. Thanks!

July 22, 2019 - 12:30am
Response to RahulS85

Glad to hear that! Do let us know back here, your approach and experience. It might help others on this community!

Lochana | Community Moderator | Pegasystems Inc.