- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-17-2019 09:19 AM
During our most recent SNUG we were told that the current Workflow Editor capability would be deprecated in the near future with Flow Designer replacing the functionality. It was advised that when possible to leverage Flow Designer now when possible in lieu of the 'legacy' Workflow Editor. At the time someone asked if there was any specific use-cases where Workflow Editor should still be used instead of Flow Designer. No clear answer was given. The main questions I have are:
1. With Knowledge Bases and Catalog Items having direct reference fields to the legacy workflows, is there a plan to migrate those over to Flow Designer, and if so, when that may be?
2. Is it possible to have these items run off of Flow Designer now instead of legacy workflows? (We are currently on Madrid with a plan to upgrade to Orlando next spring/summer)
3. Are there any clear examples of functionality that does not exist with Flow Designer but does exist with Workflow Editor that are documented to keep in mind, or at the very least some sort of best practices of when to use one over the other?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-17-2019 11:16 AM
I agree with Michael and Jeff here. You didn't ask this exactly, but I wouldn't look at converting your existing workflows to flow designer unless there is a compelling reason like taking advantage of IntegrationHub or some other flow designer capability.
I would try to use Flow Designer over workflow for any new process automation, if possible.
This subject is also addressed here: https://developer.servicenow.com/app.do#!/document/content/app_store_doc_pro_dev_guide_page5_newyork...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-07-2020 09:50 AM
Yes it does seem odd. We are building on Madrid and believe the issue is mostly caused by our scoped workflow creating global approval tasks. We are still trying out a few things to narrow it down.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-07-2020 09:32 AM
Yes it does seem odd. We are building on Madrid and believe the issue is mostly caused by our scoped workflow creating global approval tasks. We are still trying out a few things to narrow it down.
