How to update flow without changing in progress tasks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2023 11:23 AM
I have an existing flow that has RITMs/SCTasks that are currently in progress. I have made a few updates to the flow in Dev and am ready to push to production. My desire is to move the updated flow without altering the flow for any of the current in progress RITMs/SCTasks.
Essentially, I want the new flow to run for any brand new submissions that are made without altering the current flow for anything already in progress.
Does anyone know if/how this can be done?
- Labels:
-
Service Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2023 11:26 AM
Hi @Bradley Marin ,
You can go ahead n push the updated flow in production.
The in progress RITM/ Task will continue with older version of flow only.
NEW UPDATE will not have any impact on the ongoing tickets. New version of flow will only come in picture when new request will be raised once u push the flow.
Mark my answer as helpful & accepted if it answers your question.
Thanks,
Danish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2023 11:32 AM
Hi @Danish Bhairag2
Is this true even if I made updates to the variables on the catalog item? I've tried completing some of the tasks in a sub prod after the flow update and they appeared to follow the updated flow instead the old one like I want.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2023 11:55 AM
Hi @Bradley Marin ,
This will be the case only for flow. For variables of catalog item it might not behave the same way.
Whenever any catalog item is submitted the current version of the flow gets attached to the RITM record. So what I mean to say is every ticket will have its own seperate instance of the flow attached to it.so pushing a updated version will not interfere with the workflow process.
You can test this in non prod environment n check like updating only the newer version of flow n checking the older tickets how do they behave.
Thanks,
Danish