- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
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! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
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! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
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!
