Disable old-style Workflow

Ishi
Giga Expert

Hi everyone,

I’m currently using the old-style Workflow for Change Requests, and I’m trying to replace it with Flow Designer.

This may be a basic question, but how can I disable the old-style Workflow?

What I tried was going into Workflow Editor (workflow_ide.do) and attempting to set the Published property of the workflow associated with the change_request table to false. In the UI, this is located at Workflow > Properties > General tab > Published. However, the Published field is grayed out, so I’m unable to change it.

Could the experts here please share your advice?

Thank you in advance.

Ishi_0-1776076375286.png

 



4 ACCEPTED SOLUTIONS

Ankur Bawiskar
Tera Patron

@Ishi 

Starting from Zurich all OOTB workflows are migrated to Flow

ServiceNow Will Not Ship OOB Legacy Workflows Starting in Zurich 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

@Ishi 

OOTB change workflows are migrated to Flow by ServiceNow from Zurich onwards

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

For what it's worth - our OOTB change workflows were not migrated to Flow when we upgraded to Zurich from Yokohama... I think you just mean new Z instances.

 

View solution in original post

Ishi
Giga Expert

Sorry for the late reply.
I made the following changes to the instance and confirmed that the new-style flow was working:
- Installed the plugin "com.snc.change_management.change_model.foundation".
- Changed the system property com.snc.change_management.change_model.hide from true to false.
- Changed the system property com.snc.change_management.change_model.type_compatibility from true to false.
- Changed the system property com.snc.change_management.change_model.manage_workflow from true to false.

And what I learned is that the difference between the old-style workflow and the new-style flow, for what ServiceNow has migrated, is only the UI; the underlying program or process is the same.
Thank you!

View solution in original post

5 REPLIES 5

Ankur Bawiskar
Tera Patron

@Ishi 

Starting from Zurich all OOTB workflows are migrated to Flow

ServiceNow Will Not Ship OOB Legacy Workflows Starting in Zurich 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Hi @Ankur Bawiskar 

Thanks for the helpful link! I realized that my case is what is described there as a "custom legacy workflow."

To restate my issue, I want to disable the custom legacy workflows associated with Change Requests.

As a practical workaround, I could replace those workflows with dummy logic that does nothing. However, that would obviously be a hack, and I’m concerned about possible side effects in the future.
Best Regards,

@Ishi 

OOTB change workflows are migrated to Flow by ServiceNow from Zurich onwards

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

For what it's worth - our OOTB change workflows were not migrated to Flow when we upgraded to Zurich from Yokohama... I think you just mean new Z instances.