I have an application in Production with an assignment to Update Home Address and there are one or more cases in Production that are waiting in this assignment. However, there is a new change that instead of Updating Home Address assignment, we need to replace it with a screen flow that can update other details as well?
Regards
Mokshagna.
Its not a recommended process to to update flows on inflight places. You can try to create an utility which will loop through the list. Open each case with pzInsKey/pyID and acquire a lock, then use pxRestartStage to restart the stage. In the stage, do not change the flow name, instead devise you own logic that when the flow starts it’ll move to the new screen flow inside the same flow.
Hello,
You can utilize a ticketing rule for this purpose. This approach will ensure that new changes are implemented in upcoming cases, while existing cases will continue to follow the existing flow. I hope this solution helps you. Thank you.
Hi,
In case of replacing the assignment directly with the screen flow, we can use Tickets to handle the impact to in-flight cases that are waiting in the assignment which is no longer valid.
Create a ticket and set it to the flow which had Update Home Address assignment.
Write one-time activity
Fetch all the cases in Update Home Address assignment.
Open and acquire lock on the impacted cases
Set ticket to move them to the starting of the flow.
Move the flow change along with this one-time activity change. Run the one-time activity so that all the impacted in-flight cases are moved automatically to the screen flow assignment.