Hi Rawap,

Thanks for the reply. After reviewing the options 

Approach 1: Create distinct flow rules, either by choosing new flow names or by circumstancing, leaving the old flow ones as they are.

In my case we already have a flow called X and circumstance version of X based on interaction type in the system. Is it advisable to add circumstance for both X and X (circumstance) based on effective date. If yes when we can remove the old flows at what stage we can do this clean up...if we are not able to do it then again flows looks clumpsy and many to maintain.. Please advice....

Approach 2: (In the updated flow rules, leave all the old flow wait points unchanged. (Assignment, Subprocess, Split-for-each). Drag these shapes off to one side.

To ensure that flow processing does not drop these shapes when the flow rule is saved, add a placeholder ticket that connects to these shapes. Keep their outgoing connectors intact.

This way, new work objects never reach these outdated shapes, but the work objects at older assignments will still follow the same path.

At some point later, you can run a report that checks whether the old assignments are no longer in use. If so, you can then remove the flow wait points in the next version of the flow.)

This looks ok but what is wait points we are actually referring here. Can you give me more details about this approach.

Thanks in advance..