OOTB Flow action version

[RishitaG7077067]

Hi All,

By mistakenly i added a space in one of the OOTB flow action in production and saved it which changed the state of flow action to draft , is there any way i can get it back to published? Also our instance is going to be upgraded so will it generate a skipped record? Please help me here as i cannot any old version to revert it from version table (because it was Ootb). Is there any way i can fix this??

Thanks,

Ri**bleep**a

[NavinAgarwal]

Hi @RishitaG7077067 ,

To fix the OOTB flow action, you'll need to open the action in Flow Designer, correct the space, and then re-publish it to restore it to the Published state. Regarding the upgrade, if you have modified an OOTB record, it will likely be skipped by the upgrade process. However, this does not directly relate to getting the action back to Published, only to future upgrades.

Fixing the Flow Action:

1. Open the Action: Navigate to the specific OOTB flow action in Flow Designer.
2. Edit the Action: Edit the action to remove the mistakenly added space from its content or configuration.
3. Publish the Action: After removing the space, click the Publish button within the action's header to change its status from Draft back to Published.

Regarding the Upgrade
Skipped Records: Modifying an Out-Of-the-Box (OOTB) record, such as an action in Flow Designer, will generally cause it to be skipped during an instance upgrade. This is because the upgrade process is designed to only update the standard, unmodified components.
No Direct Impact on Publishing: The upgrade process skipping this customized record does not directly affect your ability to publish the action. You just need to perform the publishing step as described above.

Impact of Skipping: The primary impact is that any further updates to the OOTB component by a new version will not be applied to your instance. You would then have to manually re-apply those changes after the upgrade, if desired.

If you found my response helpful, could you please mark it as ‘Accept as Solution’ and ‘Helpful’? This small action goes a long way in helping other community members find the right answers more easily and supports the community.

[RishitaG7077067]

Hi @NavinAgarwal ,

If I publish this version then the subflow will be considered as customization which is highly avoided in our organization and also because for future upgrades we do not want to miss any new changes that might come, is there any other way to revert it to base version? Or if i leave it in draft state without publishing will it generate a skipped record?

[Ankur Bawiskar]

@RishitaG7077067 

you can revert the flow version to OOTB and you need not worry on Upgrade.

Since after reverting it will be the base version, skipped records will not be generated for that item, because the upgrade process only flags records as skipped if they differ from the new OOTB baseline.

this article explains it

ServiceNow Learning 74: Revert the Flow Designer to its previous version in ServiceNow 

sharing the steps here as well

1- Navigate to sys_update_version.list

2- Search with flow/subflow sys_id.

3- Click on the previous version.

4- Click on Form context menu UI action "revert to current' version.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@RishitaG7077067 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.