--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/delta-yokohama-zurich Release : - zurich ft:locale : - en-US ft:publication_title : - zurich Combined Product Files ft:clusterId : - delta3zy bundleId : - delta3zy --- # Combined Classic Workflow release notes for upgrades from Yokohama to Zurich # Combined Classic Workflow release notes for upgrades from Yokohama to Zurich {#ariaid-title1} Release version: Zurich Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Classic Workflow release notes for upgrades from Yokohama to Zurich This consolidated release notes document assists ServiceNow customers in preparing for upgrades of the Classic Workflow product from the Yokohama release to the Zurich release. It provides a comprehensive summary of new features, changes, deprecations, and activation details relevant to this upgrade path. Show full answer Show less ## Key Features * **Access Control Enhancement:** In Zurich, access to the Workflow Editor is now restricted by assigning the `sncrequiredscriptwriterpermission` role to users, enhancing security and control over workflow editing. ## Deprecations and Removals * **Planned Deprecation:** Classic Workflow is under planned deprecation in Zurich. Customers are advised to transition to using Workflow Studio flows and subflows instead of Classic Workflow for future-proofing their automations. * **Legacy Workflows:** For new customers starting on Zurich, legacy workflows created and published by ServiceNow, Inc. have been removed. Existing customers upgrading retain their legacy workflows to ensure continuity. ## Activation and Requirements * **Activation:** Workflow is an AI Platform feature in ServiceNow and is activated by default in the Zurich release. * **Additional Requirements:** No new additional requirements or browser changes have been introduced between Yokohama and Zurich for Classic Workflow. ## Other Notes * There were no updates or changes to Classic Workflow in the Yokohama release. * The `sncrequiredscriptwriterpermission` role has been added to all Workflow tasks in Zurich to standardize permissions. * No accessibility or localization changes have been introduced for Classic Workflow in this upgrade. Consolidated page of all release notes for Classic Workflow from Yokohama to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Classic Workflow release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Zurich. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Classic Workflow to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-classicworkflow-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## New features Between your current release family and Zurich, new features were introduced for Classic Workflow. {#dfrn3-classicworkflow-summary__entry__8} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | [Restrict access to Workflow Editor with a new role](https://www.servicenow.com/docs/access?context=r_WorkflowRoles&family=zurich&ft:locale=en-US) : Grant access to the Workflow editor by giving users the snc_required_script_writer_permission role. | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing Classic Workflow features. {#dfrn3-classicworkflow-summary__entry__14} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Removed Between your current release family and Zurich, some Classic Workflow features or functionality were removed. {#dfrn3-classicworkflow-summary__entry__20} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Deprecations Between your current release family and Zurich, some Classic Workflow features or functionality were deprecated. {#dfrn3-classicworkflow-summary__entry__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | * Support for classic workflows is in Planned Deprecation. For more information about application and plugin deprecation, see [KB0867184 on Support](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0867184). * Use Workflow Studio flows and subflows instead of classic Workflow. * Removed the legacy workflows created and published by ServiceNow, Inc. for new customers who start on the Zurich release. * Retained the legacy workflows created and published by ServiceNow, Inc. for customers who upgraded from versions prior to the Zurich release. | [ ] ## Activation information Review information on how to activate Classic Workflow. {#dfrn3-classicworkflow-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Activation information : Workflow is a ServiceNow AI Platform feature that is active by default. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Classic Workflow we have noted them here. {#dfrn3-classicworkflow-summary__entry__38} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Classic Workflow we have noted them here. {#dfrn3-classicworkflow-summary__entry__44} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Classic Workflow, such as specific requirements or compliance levels. {#dfrn3-classicworkflow-summary__entry__50} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Classic Workflow we have noted them here. {#dfrn3-classicworkflow-summary__entry__56} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Classic Workflow we have noted them here. {#dfrn3-classicworkflow-summary__entry__62} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | * Added the snc_required_script_writer_permission role to all Workflow tasks. * Removed the legacy workflows created and published by ServiceNow, Inc. from new customer installations. See [Classic Workflow](https://www.servicenow.com/docs/access?context=c_WorkflowOverview&family=zurich&ft:locale=en-US) for more information. | [ ]