Flow designer - ability to revert to previous versions

SatheeshKumar
Kilo Sage

Hi All,

 

we are trying to implement a requirement using flow designer.

 

while working we don't find a way to revert the flow back to previous versions! Any one has any suggestions on this?

 

Thanks,

satheesh

11 REPLIES 11

@Anas Hanif ,

Where is the sys_id of the flow found?  Is that in the URL at the top of the flow designer?

When I search for that in the table you mentioned, I get "No records".  Any idea why that would be?

find_real_file.png

@GeoffreyOptumOptumCare 

Do a contains search on the Name field:

find_real_file.png

For a Flow, the name will be "sys_hub_flow_<sys_id of the flow>.

 

The sys_id field in your search is the id of the actual update version record.

 

Thanks. I accidentally deleted one if which resulted in deleting the entire nested if below. Recovered back using this method.

ServiceNow Flow Designer does not have a built-in version control system to revert back to previous versions of a flow. However, there are some workarounds you can consider:

1. Manual Version Control: You can manually save versions of your flow by duplicating it at key stages of development. This way, you can revert back to a previous version by using the duplicate.

2. Use Update Sets: You can use update sets to capture changes to a flow. This way, you can revert back to a previous version by reverting the update set.

3. Use Source Control: ServiceNow supports integration with Git-based source control repositories. You can use this feature to manage versions of your flow. However, this requires some setup and may not be suitable for all situations.

4. Use the Revision History: ServiceNow keeps a revision history of all changes made to a record. You can use this feature to view previous versions of a flow. However, this is not a full version control system and may not be suitable for all situations.

5. Use a Custom Solution: You can develop a custom solution to manage versions of your flow. This could involve creating a custom table to store versions of a flow, or using a third-party version control system. However, this requires development effort and may not be suitable for all situations.

Remember, always test any changes in a non-production environment before applying them to your production environment.


nowKB.com

If you want to know any information about Service Now . Visit to https://nowkb.com/home

BobPaterno
Giga Contributor

If it is an application, consider using Github or Bitbucket to snapshot your app (including all flows/actions).

Then when you have to make changes, you can create a new branch to work off of and test.  If anything goes wrong, you can revert to the main branch or back up to a previous commit on the branch you're working on.