--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ay bundleId : - delta3ay --- # Combined Financial Services Operations Core release notes for upgrades from Yokohama to Australia # Combined Financial Services Operations Core release notes for upgrades from Yokohama to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 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 Financial Services Operations Core Release Notes for Upgrades from Yokohama to Australia This consolidated release note provides ServiceNow customers with key information about upgrading Financial Services Operations (FSO) Core from the Yokohama release to the Australia release. It covers new features, changes, deprecations, activation instructions, and other relevant upgrade considerations across the intervening releases including Zurich and Australia. Show full answer Show less ## New Features * **Zurich Release:** Introduced Payment Card Application support enabling storage and management of physical payment card details and tokenized sensitive data throughout the card lifecycle. * **Zurich Release:** Implemented Deny-Unless Access Control Lists (ACLs) on FSO tables to restrict access for non-authenticated/public users, enhancing security by allowing only authenticated users to perform read, write, delete, or create actions. * **Australia Release:** No new features introduced. ## Changes * **Yokohama Release:** Added new fields to the Claim Base \[snbomclaimbase\] table (SIU review, Claim validation decision, Claim fraud decision) for broader claim application usage. * **Zurich Release:** Made Coral the default theme for portals, web, and mobile with Next Experience or Core UI, including a new dark theme option to enhance user experience and accessibility. * **Zurich Release:** Added Payment Card field to the Financial Transaction \[snbomtransaction\] table to support payment card functionalities. * **Australia Release:** Updated the case type selector in FSO to use predefined Customer Service Management (CSM) implementation, automating migration of existing agent criteria and customer condition data from deprecated FSO tables to CSM tables, removing manual migration requirements. ## Deprecations * **Australia Release:** Deprecated FSO tables `snbomm2mservicedefinitionusercriteria` and `snbomm2mservicedefinitioncustomercondition`. Customers should transition to `sncsmcasetypesserviceusercriteria` and `sncsmcasetypesservicecustomercriteria` respectively. * **Australia Release:** The `showininterceptor` field on the `snbomservicedefinition` table is deprecated. Agent criteria in CSM tables now control service definition visibility in the case type selector, using predefined user criteria to manage visibility. ## Activation and Installation Financial Services Operations Core is available for installation via the ServiceNow Store. For all releases from Yokohama through Australia, customers should request the app from the ServiceNow Store and refer to the Store version history for cumulative release notes and installation guidance. ## Additional Information * **Accessibility:** The Zurich release introduced a dark theme option in the Coral theme to improve readability and reduce eye strain in web and mobile experiences. * **Browser Requirements, Localization, and Other Updates:** No changes or updates were noted across releases. ## Practical Implications for ServiceNow Customers * When upgrading, review and complete all pre- and post-upgrade tasks as outlined to ensure smooth transition. * Leverage the new payment card data model introduced in Zurich for comprehensive card lifecycle management and integration into FSO workflows like disputes. * Secure your FSO data by enforcing Deny-Unless ACLs to restrict access to authenticated users only. * Adopt the CSM-based case type selector introduced in Australia to simplify service definition filtering and reduce manual data migration efforts. * Plan to update any integrations or customizations referencing deprecated FSO tables or fields to use the new CSM tables and criteria to maintain compatibility and supportability. * Utilize the Coral theme and its dark mode option to enhance user experience across portals and mobile devices. Consolidated page of all release notes for Financial Services Operations Core from Yokohama to Australia. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Financial Services Operations Core release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama 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 Financial Services Operations Core to Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-financialservicesoperationscore-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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 Financial Services Operations Core. {#dfrn3-financialservicesoperationscore-summary__entry__10} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | [Payment card application](https://www.servicenow.com/docs/access?context=payment-card-application&family=zurich&ft:locale=en-US) : Store the details of physical payment cards across the entire card life cycle, from issuance to servicing. You can also store tokenized values for sensitive data, such as the primary account number (PAN). [Deny-Unless ACL](https://www.servicenow.com/docs/access?context=acl-denial-behavior&family=zurich&ft:locale=en-US) : Use Deny-Unless access control lists (ACLs) on FSO tables for non-authenticated users, such as users with public roles. With this minimum-security setting, only your authenticated users can read, write, delete, or create actions on these tables. For more information about the Deny-Unless ACLs, see the [Deny-Unless ACL](https://www.servicenow.com/docs/access?context=acl-denial-behavior&family=zurich&ft:locale=en-US) topic in the ServiceNow® Platform Security documentation. | | Australia | No updates for this release. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing Financial Services Operations Core features. {#dfrn3-financialservicesoperationscore-summary__entry__18} | Release | Release notes | |-|-| | Yokohama | [Added fields to Claim Base table](https://www.servicenow.com/docs/access?context=fso-core-insurance-tables&family=yokohama&ft:locale=en-US) : Added the following fields to the Claim Base \[sn_bom_claim_base\] table: * SIU review * Claim validation decision * Claim fraud decision | | Zurich | Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Added field to Financial transaction table](https://www.servicenow.com/docs/access?context=fso-core-banking-tables&family=zurich&ft:locale=en-US) : Added the Payment Card field to the Financial transaction \[sn_bom_transaction\] table as part of the Payment card application. | | Australia | [Case type selector](https://www.servicenow.com/docs/access?context=csm-case-type-select-modals&family=australia&ft:locale=en-US) : Filter service definitions using the case type selector in FSO with the predefined CSM implementation. For upgraded instances, existing agent criteria and customer condition data is automatically migrated from the deprecated FSO tables to the CSM tables during upgrade. No manual migration is required. To configure agent criteria or customer conditions for the case type selector, use the following CSM tables: * `sn_csm_case_types_service_user_criteria`: for agent criteria * `sn_csm_case_types_service_customer_criteria`: for customer conditions | [ ] ## Removed Between your current release family and Australia, some Financial Services Operations Core features or functionality were removed. {#dfrn3-financialservicesoperationscore-summary__entry__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some Financial Services Operations Core features or functionality were deprecated. {#dfrn3-financialservicesoperationscore-summary__entry__34} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | * The FSO tables `sn_bom_m2m_service_definition_user_criteria` and `sn_bom_m2m_service_definition_customer_condition` are deprecated. If you're on an upgraded instance, you can continue to reference these tables, but they're no longer maintained. Use `sn_csm_case_types_service_user_criteria` and `sn_csm_case_types_service_customer_criteria` instead. For more information, see [Banking tables](https://www.servicenow.com/docs/access?context=fso-core-banking-tables&family=australia&ft:locale=en-US). * The Show in Interceptor field (`show_in_interceptor`) on the `sn_bom_service_definition` table is deprecated. Use agent criteria in the `sn_csm_case_types_service_user_criteria` table to control which service definitions appear in the case type selector. User criteria mappings control the visibility of new service definitions. To hide a service definition, map it to the No User user criteria. To make it visible, map it to the Users with sn_bom.service_definition_read user criteria. Both user criteria records are predefined in Financial Services Operations Core. For more information, see [Components installed with case types](https://www.servicenow.com/docs/access?context=service-definitions-components&family=australia&ft:locale=en-US). | [ ] ## Activation information Review information on how to activate Financial Services Operations Core. {#dfrn3-financialservicesoperationscore-summary__entry__42} | Release | Release notes | |-|-| | Yokohama | Activation information : Install Financial Services Operations Core by requesting it from ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US). Important: Financial Services Operations Core is available in ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Activation information : Install Financial Services Operations Core by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=zurich&ft:locale=en-US). Important: Financial Services Operations Core is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Australia | Activation information : Install Financial Services Operations Core by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=australia&ft:locale=en-US). Important: Financial Services Operations Core is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Financial Services Operations Core we have noted them here. {#dfrn3-financialservicesoperationscore-summary__entry__50} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Financial Services Operations Core we have noted them here. {#dfrn3-financialservicesoperationscore-summary__entry__58} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Financial Services Operations Core, such as specific requirements or compliance levels. {#dfrn3-financialservicesoperationscore-summary__entry__66} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. | | Australia | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Financial Services Operations Core we have noted them here. {#dfrn3-financialservicesoperationscore-summary__entry__74} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Financial Services Operations Core we have noted them here. {#dfrn3-financialservicesoperationscore-summary__entry__82} | Release | Release notes | |-|-| | Yokohama | The Claim Base \[sn_bom_claim_base\] table has been updated in this release with additional fields. These fields were previously available only to specific applications. They're available in the Claim Base table and can be used across all other claim applications in this release. See [Financial Services Operations Core](https://www.servicenow.com/docs/access?context=financial-services-operations-core-data-model&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * Leverage a payment card data model application in FSO workflows, such as disputes, which can be used across an entire card life cycle, from issuance to servicing. * Support multiple payment card types, including credit and debit cards. See [Payment Card](https://www.servicenow.com/docs/access?context=payment-card-application&family=zurich&ft:locale=en-US) for more information. | | Australia | The case type selector in Financial Services Operations now uses the predefined Customer Service Management (CSM) implementation, replacing the previous FSO-specific override. See [Case type selector](https://www.servicenow.com/docs/access?context=csm-case-type-select-modals&family=australia&ft:locale=en-US) for more information. | [ ]