Managing Flow changes for inflight Cases

User Experience
1

Our application comprises three distinct stages. Previously, approximately 90% of the code resided within the “create” stage. A new stage has been introduced between the original first and second stages, necessitating the relocation of all code from the initial stage to this newly implemented stage. Consequently, the existing “create” stage has been reconfigured as a straight-through process, with the actual intake process commencing in the new stage.

A significant issue has arisen: older cases are no longer accessible. I considered implementing a circumstance rule based on the case type; however, it appears that this approach does not support date-type property circumstances. Any guidance on resolving this situation would be greatly appreciated.

2

To ensure that this does not affect further cases in production,it is always recommended to:

  1. Assess before you change :Carefully evaluate changes, especially for active cases.
  2. Identify risks :Spot updates that could create Problem Flows.
  3. Choose the right approach: Select the safest strategy for production flow updates.
  4. Resolve & recover: Use Problem Flows to diagnose and resolve flow issues.
  5. Monitor proactively :Use the Problem Flow landing page to track and manage issues.
    There is a good article which handles changes to the case flows where the case is active Handling flow changes for cases in flight | Pega Academy