--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined Classic Workflow release notes for upgrades from Zurich to Australia # Combined Classic Workflow release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated November 5, 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 Zurich to Australia This consolidated release notes document provides ServiceNow customers with essential information when upgrading Classic Workflow from the Zurich release family to the Australia release family. It combines updates, changes, and important considerations across these releases to help you prepare for and execute your upgrade smoothly. Show full answer Show less ## Key Features * **Zurich Release:** Introduced a new role `sncrequiredscriptwriterpermission` to restrict access to the Workflow Editor, enhancing security and control over workflow editing. * **Activation:** Classic Workflow is active by default as part of the ServiceNow AI Platform, so no manual activation steps are required during upgrade. ## Deprecations and Removals * Support for Classic Workflow is marked as **Planned Deprecation**, encouraging customers to transition to Workflow Studio flows and subflows for future-proof workflow automation. * Legacy workflows created and published by ServiceNow were removed for new customers starting with Zurich; however, customers upgrading from versions prior to Zurich retain these legacy workflows. ## Upgrade Considerations * **Pre- and Post-Upgrade Tasks:** Customers should review and complete specified tasks before and after upgrading to ensure a smooth transition. * No changes, new features, removals, or updates were noted in the Australia release for Classic Workflow beyond those inherited from Zurich. ## Additional Notes * There are no updates related to browser requirements, accessibility, localization, or additional requirements between Zurich and Australia for Classic Workflow. * The `sncrequiredscriptwriterpermission` role has been added to all Workflow tasks to enforce controlled access. By understanding these updates and deprecations, ServiceNow customers can plan their upgrades effectively, secure their workflow editing environment, and prepare for the eventual transition to Workflow Studio, ensuring ongoing workflow automation success. Consolidated page of all release notes for Classic Workflow from Zurich to Australia. ## 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 Zurich to Australia. 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 Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-classicworkflow-summary__entry__2} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## New features Between your current release family and Australia, new features were introduced for Classic Workflow. {#dfrn3-classicworkflow-summary__entry__8} | Release | Release notes | |-|-| | 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. | | Australia | No updates for this release. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing Classic Workflow features. {#dfrn3-classicworkflow-summary__entry__14} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Removed Between your current release family and Australia, some Classic Workflow features or functionality were removed. {#dfrn3-classicworkflow-summary__entry__20} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some Classic Workflow features or functionality were deprecated. {#dfrn3-classicworkflow-summary__entry__26} | Release | Release notes | |-|-| | 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. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate Classic Workflow. {#dfrn3-classicworkflow-summary__entry__32} | Release | Release notes | |-|-| | Zurich | Activation information : Workflow is a ServiceNow AI Platform feature that is active by default. | | Australia | No updates for this release. | [ ] ## 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 | |-|-| | Zurich | No updates for this release. | | Australia | 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 | |-|-| | Zurich | No updates for this release. | | Australia | 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 | |-|-| | Zurich | No updates for this release. | | Australia | 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 | |-|-| | Zurich | No updates for this release. | | Australia | 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 | |-|-| | 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. | | Australia | No updates for this release. | [ ]