--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-yokohama-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3by bundleId : - delta3by --- # Combined Third-party Risk Management release notes for upgrades from Yokohama to Brazil # Combined Third-party Risk Management release notes for upgrades from Yokohama to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 38 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 Third-party Risk Management release notes for upgrades from Yokohama to Brazil This consolidated release notes document provides ServiceNow customers with comprehensive information and guidance for upgrading Third-party Risk Management (TPRM) from the Yokohama release through to Brazil. It covers upgrade instructions, new features, changes, removals, deprecations, activation, and accessibility considerations relevant to each release version in this upgrade path. Show full answer Show less Sequential upgrading through each release version is essential to ensure data integrity and proper execution of upgrade scripts. The document also highlights important preparatory and post-upgrade tasks and emphasizes thorough testing, especially when enabling new features like the Smart Assessment Engine. ## Upgrade Guidance and Important Considerations * **Sequential Upgrade Required:** Upgrades must be performed sequentially from one release to the next (e.g., Yokohama to Zurich to Australia to Brazil) to avoid data inconsistencies or broken functionality. * **Smart Assessment Engine (SAE):** Introduced in Zurich and later releases, enabling the SAE property replaces the legacy assessment engine irreversibly. Testing in non-production environments is strongly recommended before production deployment. * **Data Migration:** Industry data in the Company table migrates to a new column automatically after certain versions. Customers must update any customizations referencing the old field accordingly. * **Role Changes:** Role inheritance has changed in Australia release; manual role review is necessary for users with custom role combinations. * **Read-only Field Security:** Enhanced protections for read-only fields improve instance security without breaking backward compatibility. ## Key Features Introduced Between Yokohama and Brazil * **Standardized Information Gathering (SIG) Questionnaires:** Updated SIG templates for 2025 and 2026 provide improved regulatory compliance and risk governance coverage. * **TPRM Personalized Dashboards:** Customizable dashboards and analytics enable role-based insights and reporting to improve decision-making. * **Document Management System (DMS):** Centralized repository for third-party documents with metadata, version control, and access permissions enhances audit readiness. * **Register of Information (RoI) Reporting and Validation:** Tools to generate regulator-ready packages and validate data formats support EU DORA compliance. * **Smart Assessment Engine Enhancements:** Improved navigation, questionnaire organization, auto-save, risk rating scales, bulk template migration, and versioning improve assessment effectiveness and consistency. * **AI Capabilities (ServiceNow Otto for TPRM):** Support for multiple AI models, AI-assisted questionnaire pre-fill, and generative AI issue recommendations streamline assessment and issue identification processes. * **Software Bill of Materials (SBOM) Support:** Enables collection and management of SBOM data to meet regulatory disclosure requirements. * **Third-party Element Assessments and Risk Scoring:** Element-level risk assessments and scoring rollups improve granularity and accuracy of risk monitoring. * **Internal Task Management:** Ability to create internal tasks for due diligence and risk processes, visible only to internal users. * **Enhanced Vendor Management Workspace:** Vertical navigation, new related lists for contracts, Coral theme with dark mode option, and workspace improvements enhance usability and workflow clarity. * **DORA Regulatory Support:** Automated supply chain updates, duplicate detection, LEI validation, currency conversion, and data quality warnings improve compliance and reporting accuracy. * **Excel Questionnaire Templates and Portal Improvements:** Support for Microsoft Excel questionnaire import/export facilitates third-party response collection outside the portal environment. ## Changes and Removals * Terminology updates rename assessments and fields for clarity (e.g., "Third-party assessments" to "External assessments"). * Role inheritance changes require manual review for some users. * Some deprecated fields and features, such as scoringrule fields and assessments using entities, require updating custom scripts or integrations. * Third-party elements are now linked to single third parties only; sharing across parties is removed. * Issue generation rules do not create issues for hidden questions anymore to avoid irrelevant alerts. ## Activation and Additional Notes * TPRM is available for installation via the ServiceNow Store for all releases covered. * No additional browser or accessibility requirements were introduced beyond those noted (e.g., Coral theme includes dark mode; accessibility improvements in Australia release). * Localization updates include externalization and translation of portal strings with some incomplete translations in newer features. * ServiceNow AI Platform now offers three licensing tiers (Foundation, Advanced, Prime) to access varying AI capabilities within TPRM. ## What ServiceNow Customers Can Expect By following the upgrade guidance and leveraging new features introduced from Yokohama to Brazil, customers can: * Enhance third-party risk assessment accuracy and efficiency using the Smart Assessment Engine and AI-assisted tools. * Improve regulatory compliance with updated SIG questionnaires, DORA reporting tools, and Consolidated page of all release notes for Third-party Risk Management from Yokohama to Brazil. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Third-party Risk Management release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Brazil. 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 Third-party Risk Management to Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-thirdpartyriskmanagement-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | Upgrade information : Starting with the Vancouver release, if you're a VRM user upgrading to TPRM, from an earlier release, you must run each upgrade sequentially to ensure that fix scripts run correctly. This means upgrading from one release to the next rather than skipping to the latest release. Not running scripts in the correct order can result in data inconsistencies, broken functionalities, and conflicts. For more information on upgrading from VRM to TPRM, see [Third-party Risk Management upgrade information](https://www.servicenow.com/docs/access?context=grc-tprm-upgrade-info&family=yokohama&ft:locale=en-US). For existing TPRM customers, after upgrading to version 20.2.4, data from the Industry column in the Company \[core_company\] table is automatically migrated to the tprm_industry column. Migration can take several hours depending on the number of records in the Company \[core_company\] table. After migration, a system log message confirms that the migration is complete. Review the Company \[core_company\] table content and update any customizations referencing the Industry field to use tprm_industry. After verifying the migration and updating customizations, you can drop the Industry column. | | Zurich | Upgrade information : If you're a VRM user upgrading to TPRM and upgrading to Vancouver or a later release from an earlier release, you must run each upgrade sequentially to ensure that fix scripts run correctly. For example, you must upgrade from Utah to Vancouver, Vancouver to Washington DC, and so on. If the scripts don't run in the correct order, you can get data inconsistencies, broken functionalities, and conflicts. After upgrading to version 21.0.x, you can enable the Smart Assessment Engine (SAE) by setting the Smart Assessment Engine enabled (sn_vdr_risk_asmt.sae_enabled) property. After setting this property, Smart Assessment Engine (SAE) becomes the default assessment engine and replaces the legacy experience. The transition isn't reversible. Warning: Set this property in your non-production instances and conduct thorough testing before changing your production instances. Failure to do so may result in unexpected issues. For more information on upgrading from VRM to TPRM and the differences between the Smart and Classic Assessment engines, see [Third-party Risk Management upgrade information](https://www.servicenow.com/docs/access?context=grc-tprm-upgrade-info&family=zurich&ft:locale=en-US). For existing TPRM customers, after upgrading to version 21.0.3, data from the Industry column in the Company \[core_company\] table is automatically migrated to the tprm_industry column. Migration can take several hours depending on the number of records in the Company \[core_company\] table. After migration, a system log message confirms that the migration is complete. Review the Company \[core_company\] table content and update any customizations referencing the Industry field to use tprm_industry. After verifying the migration and updating customizations, you can drop the Industry column. The Zurich release introduces enhanced protections for read‑only fields across the ServiceNow AI Platform®. These changes include a new "read_only_option" field with granular control levels, including "strict_read_only" and "client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to [KB2718122](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2718122) for additional technical details on how to identify affected fields and adjust their settings. | | Australia | Upgrade information : If you're a VRM user upgrading to TPRM and upgrading to Australia from an earlier release, you must run each upgrade sequentially to ensure that fix scripts run correctly. For example, you must upgrade from Xanadu to Yokohama, Yokohama to Zurich, and so on. If the scripts don't run in the correct order, you can get data inconsistencies, broken functionalities, and conflicts. After upgrading to version 21.0.x, you can enable the Smart Assessment Engine (SAE) by setting the Smart Assessment Engine enabled (sn_vdr_risk_asmt.sae_enabled) property. After setting this property, Smart Assessment Engine (SAE) is set to the default assessment engine and replaces the legacy experience. The transition is irreversible. Warning: Set this property in your non-production instances and conduct thorough testing before changing your production instances. Failure to do so can result in unexpected issues. For more information on upgrading from VRM to TPRM and the differences between the Smart and Classic Assessment engines, see [Third-party Risk Management upgrade information](https://www.servicenow.com/docs/access?context=grc-tprm-upgrade-info&family=australia&ft:locale=en-US). For existing TPRM customers, after upgrading to version 21.0.3, data from the Industry column in the Company \[core_company\] table is automatically migrated to the tprm_industry column. Migration can take several hours depending on the number of records in the Company \[core_company\] table. After migration, a system log message confirms that the migration is complete. Review the Company \[core_company\] table content. Update any customizations that reference the Industry field to use tprm_industry. After verifying the migration and updating customizations, you can drop the Industry column. After upgrading to version 22.3.3, the `grc_business_user` and `grc_reader` roles are no longer directly inherited by TPRM roles. During upgrade, most users are automatically migrated to new feature‑specific roles. Users with custom role combinations may not be migrated automatically and require manual review before the grace period ends. | | Brazil | Upgrade information : If you're upgrading from an earlier release, upgrade sequentially through each release rather than skipping versions. Upgrade scripts depend on running in order, and skipping releases can cause data inconsistencies or broken functionality. Enabling the sn_vdr_risk_asmt.sae_enabled property makes the Smart Assessment Engine (SAE) the default assessment engine and replaces the legacy experience. Warning: Enabling the sn_vdr_risk_asmt.sae_enabled property is irreversible. Set this property in a non-production instance and test thoroughly before enabling it in production. | [ ] ## New features Between your current release family and Brazil, new features were introduced for Third-party Risk Management. {#dfrn3-thirdpartyriskmanagement-summary__entry__12} | Release | Release notes | |-|-| | Yokohama | [New Standardized Information Gathering (SIG) questionnaire content](https://www.servicenow.com/docs/access?context=grc-sig-integration&family=yokohama&ft:locale=en-US) : Use the updated SIG templates for 2025 after upgrading to version 20.1.x as part of the Third-party Risk Management application. The latest SIG questionnaires help your organization stay aligned with stricter regulatory compliance and emerging third-party risk governance, covering a wide range of security and privacy concerns. [TPRM personalized dashboards](https://www.servicenow.com/docs/access?context=tprm-monitor-dashboards&family=yokohama&ft:locale=en-US) : Improve your decision-making process by exploring and analyzing your assessment data at various levels by using the Third-party insights dashboard and the TPRM custom analytics dashboard. If you have the Third-party risk manager \[sn_vdr_risk_asmt.vendor_risk_manager\] or Third-party risk assessor \[sn_vdr_risk_asmt.vendor_assessor\] role, you can create and share your own dashboards and reports. If you're a third-party risk manager, you can also customize the report layouts, widgets, and data views to prioritize key metrics and workflows that align with your individual roles and risk programs. [Quick start tests for TPRM](https://www.servicenow.com/docs/access?context=quick-start-tests-grc-vrm&family=yokohama&ft:locale=en-US) : Verify that TPRM works as expected after upgrades and deployments of new applications or integrations by running quick start tests. If you customized TPRM, copy the quick start tests and configure them for your customizations. | | Zurich | [ServiceNow Otto for Third-party Risk Management (TPRM) release notes](https://www.servicenow.com/docs/access?context=now-assist-for-tprm-rn&family=zurich&ft:locale=en-US) : Review the ServiceNow Otto for Third-party Risk Management (TPRM) release notes for full descriptions of the features. [Use the Document Management System](https://www.servicenow.com/docs/access?context=tprm-dms&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, you can use the Document Management System (DMS) in TPRM, which provides a centralized repository for storing, organizing, and managing third-party documents throughout the vendor life cycle. It can be used by third-party risk managers \[sn_vdr_risk_asmt.vendor_manager\], third-party assessors \[sn_vdr_risk_asmt.vendor_assessor\], and third parties to upload, categorize, track, and review documents with metadata, version control, and access permissions. This feature streamlines evidence tracking, reduces duplication, and improves audit readiness by enabling document reuse across assessments, contracts, issues, and tasks. For information on Now Assist skills for TPRM and Document Management, see [ServiceNow Otto for Third-party Risk Management (TPRM) release notes](https://www.servicenow.com/docs/access?context=now-assist-for-tprm-rn&family=zurich&ft:locale=en-US) and [Now Assist in Document Intelligence release notes](https://www.servicenow.com/docs/access?context=now-assist-document-intelligence-rn&family=zurich&ft:locale=en-US). [Register of information regulatory packages](https://www.servicenow.com/docs/access?context=tprm-dora-roi&family=zurich&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 21.1.x, third-party assessors \[sn_vdr_risk_asmt.vendor_assessor\] can now generate regulator-ready Register of Information packages using the Plain-CSV Report Package option on the download page. The ZIP file includes metadata and report folders structured to regulator specifications, with file names containing LEI, entity ID, and release version. This format helps ensure EU DORA compliance and supports automated validation workflows. You can follow the user guide on the Download/Upload request page for suggested steps and permissions. [Validation framework for RoI](https://www.servicenow.com/docs/access?context=tprm-validation-roi&family=zurich&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 21.1.x, third-party risk managers \[sn_vdr_risk_asmt.vendor_manager\] can now validate downloaded Register of Information packages using the Plain-CSV Report Package option on the download page against requirements. File format, structure, encoding, naming conventions, and field-level data are validated across multiple tables. If any validation warnings are detected, a validation report is automatically attached, including mappings to regulator fields such as Template Code, Row Code, and Column Code. Validation reports include real-world field labels, rule expressions, and record identifiers. You can cross-reference validation errors using a downloadable Excel master template that mirrors the CSV structure, making it easier to locate and address issues. Additional enhancements include support for "Not applicable" values, enforcement of file size limits, and clearer error messages for malformed data. [New sn_vdr_risk_asmt.sae_enabled property](https://www.servicenow.com/docs/access?context=tprm-properties-configure&family=zurich&ft:locale=en-US) : Use the new and improved Smart Assessment experience after you upgrade to version 21.0.x and set the Smart Assessment Engine enabled (sn_vdr_risk_asmt.sae_enabled) property. [Smart Assessment Engine](https://www.servicenow.com/docs/access?context=tprm-sae-using&family=zurich&ft:locale=en-US) : Create Smart Assessment Engine assessments for your organization: * Enhanced navigation: Use the improved navigation for a better user experience. * Assessment support: Conduct assessments for both internal and external parties. TPRM questionnaire templates include additional attributes such as the risk area and the option to include previous responses, which aren't available in SAE. TPRM templates must be created directly within the Vendor Management Workspace to ensure that they include the necessary attributes. * Organize questions: Group questions into subsections for better organization. * Add attachments: Attach the files directly to the individual questions. * Add reference information: Add reference information to a questionnaire template to help ensure that assessors can access the information they need while responding. * Filter questions: Quickly identify and filter unanswered questions. * Auto-save for questionnaires: Auto-save each question automatically after changes are made to them. * Standardized risk rating scale definition: Define the risk rating scales at the template level for both internal and external assessments. * Assessment duration: Define the duration of an assessment when creating a questionnaire template. * Combine assessments: Respond to questionnaires by using the same SAE template in a single, streamlined view. * Bulk template migration: Migrate classic templates in bulk to the Smart Assessment format. To ensure the templates work correctly in TPRM, you must migrate them by using the Third-party Risk Management application. * Risk score normalization: Standardize the risk scores for a consistent evaluation. * Support for the GRC and third-party portals: Use the GRC portal to access and complete internal assessments and the third-party portal to complete external assessments. | | Australia | [Extended AI model support for Now Assist for TPRM](https://www.servicenow.com/docs/access?context=supporting-information-now-assist-tprm&family=australia&ft:locale=en-US) : After upgrading to version 22.3.4, ServiceNow Otto for Third-party Risk Management (TPRM) supports Google Gemini 3.5 Flash, OpenAI GPT 5.1, and OpenAI GPT 5.4 mini models in addition to previously supported models. Model availability depends on your ServiceNow Otto for Third-party Risk Management (TPRM) subscription, providing greater flexibility when selecting the AI model that meets your requirements. [AI-assisted questionnaire pre-fill](https://www.servicenow.com/docs/access?context=tprm-dms-sae&family=australia&ft:locale=en-US) : After upgrading to version 22.3.3 and activating the ServiceNow Otto for Third-party Risk Management (TPRM) application, you can use uploaded documents and responses from previous assessments to generate suggested questionnaire responses with source citations. For internal assessments, the snc_internal role is required. For external assessments, primary contacts can complete all assessment response actions; secondary contacts must be assigned read and write access. [Software Bill of Materials (SBOM) support](https://www.servicenow.com/docs/access?context=tprm-sbom-exploring&family=australia&ft:locale=en-US) : After upgrading to version 22.3.2 and installing the required SBOM applications, if you have the third-party risk manager role \[sn_vdr_risk_asmt.vendor_risk_manager\] or third-party risk assessor role \[sn_vdr_risk_asmt.vendor_risk_assessor\], you can collect and manage SBOM data to support regulatory disclosure requirements. [Standardized Information Gathering (SIG) 2026 questionnaires](https://www.servicenow.com/docs/access?context=tprm-sig-use-and-support&family=australia&ft:locale=en-US) : After upgrading to version 22.3.0, if you have the third-party risk manager role \[sn_vdr_risk_asmt.vendor_risk_manager\], you can use updated SIG Full, SIG Core, and SIG Lite templates for 2026 with expanded coverage across major security and privacy frameworks. Existing SIG questionnaire versions remain available. In‑flight assessments aren't affected. [Smart Assessment template versioning](https://www.servicenow.com/docs/access?context=tprm-sae-using&family=australia&ft:locale=en-US) : After upgrading to version 22.3.3, if you have the third-party risk manager role \[sn_vdr_risk_asmt.vendor_risk_manager\], you can manage SAE template lifecycles using explicit versioning so that in-flight assessments use the version that was active when they were created. [Legal Entity Identifier (LEI) validation for DORA reporting](https://www.servicenow.com/docs/access?context=tprm-valid-lei&family=australia&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 22.3.1, if you have the third-party risk manager role \[sn_vdr_risk_asmt.vendor_risk_manager\], you can validate Legal Entity Identifier codes against the GLEIF database to support regulatory accuracy in Register of Information reporting. For descriptions of validation results and report columns, see [Level 4 LEI Validation Report columns](https://www.servicenow.com/docs/access?context=tprm-lei-validation-report&family=australia&ft:locale=en-US). [Generate TPRM issue recommendations](https://www.servicenow.com/docs/access?context=create-recommendation-tprm-issue&family=australia&ft:locale=en-US) : After upgrading to version 22.0.8 if you have the third‑party assessment reviewer role \[sn_vdr_risk_asmt.vendor_assessment_reviewer\] and have installed the ServiceNow Otto for Third-party Risk Management (TPRM) application, you can use generative AI to automatically identify and recommend issues based on assessment responses. The TPRM issue management recommendation skill recommends issues with rationalized summaries. Recommended issues are presented for review and are created as standard TPRM issues only after user confirmation. [Generate aggregate regulatory reports in local currencies](https://www.servicenow.com/docs/access?context=tprm-dora-currency-aggregation&family=australia&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 22.0.3, third‑party risk (TPR) managers \[sn_vdr_risk_asmt.vendor_manager\] can standardize annual expense values during Register of Information report generation by enabling currency conversion and third‑party total expense aggregation. To support this process, the generated reporting package includes summary and detail reports that indicate successful conversions, aggregation results, and any skipped providers. [Centralized repository for TPRM SAE templates](https://www.servicenow.com/docs/access?context=tprm-integrating-ucm&family=australia&ft:locale=en-US) : After upgrading to version 22.0.2 and installing the Unified Content Management application, TPR managers \[sn_vdr_risk_asmt.vendor_risk_manager\] can help ensure consistent and comprehensive assessments by activating and updating ready‑to‑use Smart Assessment Engine questionnaire templates through a single, managed repository in the Vendor Management Workspace. | | Brazil | [Support for AI assets in element collection](https://www.servicenow.com/docs/access?context=tprm-monitor-tp-elements&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, you can add, review, and manage third-party elements, including AI use cases and AI models, in the Elements grid. The grid is available directly on a third-party or engagement record in the Vendor Management Workspace, or embedded in a collection task in the Vendor Management Workspace or third-party portal. Elements linked to multiple engagements reuse existing assessment evidence across linked engagements without requiring a new assessment. [Internal tasks for due diligence and risk processes](https://www.servicenow.com/docs/access?context=tprm-internal-tasks&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, and if you have the TPR assessor \[sn_vdr_risk_asmt.vendor_assessor\] role, you can create internal tasks to assign follow-up work to internal users for due diligence and risk processes. Internal tasks aren't visible to third-party contacts and don't appear in the third-party portal. [DORA register-of-information terminology definitions](https://www.servicenow.com/docs/access?context=tprm-dora-roi-terminology-definitions&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, and if you have the TPR assessor \[sn_vdr_risk_asmt.vendor_assessor\] role, you can document register-of-information terminology directly in the Vendor Management Workspace. Term definitions are included in the `B_99.01` CSV export when you generate a Register of Information report. [Document version comparison for third-party documents](https://www.servicenow.com/docs/access?context=tprm-compare-document-versions&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, and if you have the TPR assessor \[sn_vdr_risk_asmt.vendor_assessor\] role, you can use the Document Management System to compare two versions of the same document type collected during third-party assessments. Only DOCX-to-DOCX and DOC-to-DOC formats are supported. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Third-party Risk Management features. {#dfrn3-thirdpartyriskmanagement-summary__entry__22} | Release | Release notes | |-|-| | Yokohama | [Multiple legal entities making use of the services for contracts](https://www.servicenow.com/docs/access?context=tprm-drtp-reg-contract&family=yokohama&ft:locale=en-US) : If you have the third-party assessor role \[sn_vdr_risk_asmt.vendor_assessor\], add multiple legal entities that are using services as part of a contract record in the digital resilience third-party registers within the Vendor Management Workspace. Including all entities that are using services associated with a contract is essential for maintaining transparency, helping ensure compliance, and enhancing operational resilience. [Codes and additional identification information for ICT third-party service providers](https://www.servicenow.com/docs/access?context=tprm-create-ICT-thirdparty-serv-prov-form&family=yokohama&ft:locale=en-US) : If you have the third-party assessor role \[sn_vdr_risk_asmt.vendor_assessor\], help ensure compliance with DORA regulations by adding additional code types and a legal name to third-party and third-party engagement records in the digital resilience third-party registers within the Vendor Management Workspace. Include this information when the legal name of a third party differs from its commonly recognized name, or when you need to record multiple identification codes like a EUID, LEI, or Country code. When supply chain, assessment, or contract records are associated with a third party or third-party engagement using the EUID code type, all relevant fields will be automatically populated. [Function types for ICT third-party service providers](https://www.servicenow.com/docs/access?context=tprm-create-new-function-form&family=yokohama&ft:locale=en-US) : If you have the third-party assessor role \[sn_vdr_risk_asmt.vendor_assessor\], help ensure compliance with DORA regulations by using Business capability as an additional function type for function records in the digital resilience third-party registers within the Vendor Management Workspace. [TPRM personalized dashboards](https://www.servicenow.com/docs/access?context=tprm-monitor-dashboards&family=yokohama&ft:locale=en-US) : The Third-party insights dashboard and the TPRM custom analytics dashboard are now available from the Dashboards page of the Vendor Management Workspace. [Third-party portal import modal](https://www.servicenow.com/docs/access?context=tprm-excel-template-support&family=yokohama&ft:locale=en-US) : The import modal now enables you to respond to questionnaires by using a Microsoft Excel template. You can download the questionnaire, complete it according to the included instructions, and import the final version into the Third-party portal. [Pre-populate responses using questionnaires](https://www.servicenow.com/docs/access?context=tprm-assessing-tpr&family=yokohama&ft:locale=en-US) : If you have the Third-party risk assessor \[sn_vdr_risk_asmt.vendor_assessor\] or Third-party risk manager \[sn_vdr_risk_asmt.vendor_risk_manager\] role, you can enable third-party and engagement contacts to review and update responses only if necessary by pre-populating questionnaires for engagements and entities with responses from completed questionnaires that are associated with the same third party. The attachment, duration, and signature type responses are excluded. This feature also helps ensure data consistency and accuracy. [Microsoft Excel questionnaire template](https://www.servicenow.com/docs/access?context=tprm-excel-template-support&family=yokohama&ft:locale=en-US) : Streamline the due diligence process by enabling third-party and engagement contacts to respond to questionnaires using a Microsoft Excel template by downloading the questionnaire as a template, completing it according to the included instructions, and importing the final version into the Third-party portal. This feature update enhances flexibility by enabling third-party and engagement contacts to provide information outside the third-party portal. Third-party risk assessors \[sn_vdr_risk_asmt.vendor_assessor\] and Third-party risk managers \[sn_vdr_risk_asmt.vendor_risk_manager\] can access this feature and respond to questionnaires on behalf of Third-party and engagement contacts through the Vendor Management Workspace. | | Zurich | [Vertical navigation in the Vendor Management Workspace](https://www.servicenow.com/docs/access?context=tprm-monitoring-tpr&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, the legacy horizontal tab-based layout in the Vendor Management Workspace has been replaced with a structured vertical navigation panel with groups of related lists, organizing access to third-party records, assessments, and performance pages in a way that supports clearer workflows and is consistently available to all internal users. [Third-party information register download option renamed to Excel master template](https://www.servicenow.com/docs/access?context=tprm-excel-upload-download-request&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, the option to download the Third-party Information Register is renamed to Excel Master Template. This change improves clarity and aligns with regulator terminology. [DPM business validation rules and properties](https://www.servicenow.com/docs/access?context=tprm-validation-roi&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, the DPM business validation rules and report.json, reportPackage.json, FrameworkCodeModuleVersion properties are now included. These modules enable Third-party risk admins \[sn_vdr_risk_asmt.vendor_admin\] to view and maintain validation logic and configuration settings for CSV reporting and automated validation. [Choice field for ICT third-party service provider identification](https://www.servicenow.com/docs/access?context=tprm-drtp-reg-contract&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, the field Type of code to identify the ICT third-party service provider is now updated to be a choice field in the Digital Resilience Third-party Information Register in the contract record. This update aligns the field with regulator-defined options for selecting identification systems when creating new providers. In the Specific Information section of the contract record, the field is read-only and auto-populated based on upstream selections, such as the third-party or engagement record. [Risk areas extended to internal assessments](https://www.servicenow.com/docs/access?context=create-sae-q-template&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, if you have the third-party risk admin \[sn_vdr_risk_asmt.vendor_admin\] role, you can now configure risk areas with weighted questions and scored responses for internal assessments using the Smart Assessment Engine in the Vendor Management Workspace. Risk scores can be aggregated at the engagement level using customizable methods such as max, min, or average, and mapped to risk ratings based on business rules. Risk managers can override system-generated ratings with required justification, enabling expert judgment and helping ensure transparency in risk decisions. [Smart Assessment Engine advanced plugins](https://www.servicenow.com/docs/access?context=tprm-migrate-asmnt-sae&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, the following Smart Assessment Engine advanced plugins are automatically installed: Post Assessment Actions for Smart Assessments \[com.sn_smart_imp_auto and com.sn_impact_fwk\] and Advanced Response Automation for Smart assessments \[sn_smart_resp_auto\]. The Post Assessment Actions for Smart Assessments plugin lets Third-party risk admins \[sn_vdr_risk_asmt.vendor_admin\] automate follow-up tasks, like notifications or workflow launches, after an assessment is completed. The Advanced Response Automation for Smart Assessments plugin automatically fills in assessment responses based on prior data or logic, streamlining and standardizing the assessment process. Feature-specific administrator role enhancements : Starting with version 21.1.x, if you have a feature admin role you can now complete tasks that were initially reserved for users with the broader administrator role. * Assign sn_vdr_risk_asmt.vendor_risk_admin to users who need to configure and manage vendor risk features. * Assign sn_vdr_risk_asmt.vendor_assessment_reviewer to users who perform assessments, manage dashboards, and require operational access. * Assign sn_vdr_risk_asmt.external_assessment_responder to users who need access to the third-party portal and to complete assessments. Note: Administrator privileges no longer grant access to TPRM features. Users must be assigned an appropriate feature-specific role to access relevant functionality. Read-only field enhancements : Starting with version 21.1.x, the following Third-party Risk Management plugins have security enhancements for read-only fields in this release: * Third-party Risk Due Diligence \[com.sn_tprm_onboarding\] * Third-party Risk Management \[com.sn_vdr_risk_asmt\] * GRC: Vendor Portal \[com.sn_grc_vendor_portal\] * GRC: Profiles \[com.sn_grc\] * GRC: Compliance Assessment \[com.sn_comp_asmt\] * GRC: SIG Questionnaire Integration \[com.sn_sig_asmt\] * GRC: Performance Analytics Premium Integration \[com.sn_grc_pa\] * Vendor Risk Management integration with EcoVadis \[com.sn_app_grc_ecovadis\] * ITAM applications \[com.snc.vendor_core\] [Fourth-party assessment support in SAE](https://www.servicenow.com/docs/access?context=tprm-monitor-fourth-parties&family=zurich&ft:locale=en-US) : Starting with version 21.1.x, Fourth-party assessments are now supported after you enable the Smart Assessment Engine enabled (sn_vdr_risk_asmt.sae_enabled) property. Global TPRM changes : * Assessments and Third-party assessments are now renamed as External assessments. * Tiering assessments are now renamed as Internal assessments. * The Tier-level column is now renamed as Risk rating. * The Tiering assessors column is now renamed as Respondents. * The Owner field is now renamed as Assigned to on the internal assessment, external assessment, tiering assessment, and due diligence request forms. [Changes made to the list view in Vendor Management Workspace](https://www.servicenow.com/docs/access?context=tprm-ws-list-page&family=zurich&ft:locale=en-US) : * The Assessment setup section has been added. From this section, you can create assessment templates, Smart Assessment questionnaire templates, and issue generation rules. * The Questionnaire requests section has been added. * The Tiering assessments and Inherent risk questionnaires (IRQ) are combined in the Internal assessments section. Changes made to internal assessment pages : * Tier-level scales are renamed as Scales. * Tiering assessment schedule and Schedules are combined and renamed as Assessment schedule. Changes made to assessment related lists : * Assessment instances is renamed as Questionnaire requests. * Questionnaires is renamed as Questionnaire templates. * Document requests is renamed as Document templates. * Fourth-party questionnaires is renamed as Fourth-party templates. * Repeating assessments is renamed as Assessment scheduling. [Smart Assessment integration changes](https://www.servicenow.com/docs/access?context=tprm-sae-using&family=zurich&ft:locale=en-US) : * The Assessment engine column has been added to the Internal and External assessment list views in Vendor Management Workspace. You can track the assessment type as you transition to using the Smart Assessment Engine for all active questionnaires. * The Assessment engine field has been added to related forms for internal risk assessments, external risk assessments, and assessment templates. * The Support smart assessment column has been added to the Assessment templates and Issue generation rules list views. * The original TPRM Classification field has been replaced with the Purpose field on all assessment templates. * The external assessment status Responses received is now Submitted to third party when SAE is enabled. * The external assessment status Returned is now In progress when SAE is enabled. [Changes made to Digital Resilience Third-party Information Register contract records in Vendor Management Workspace](https://www.servicenow.com/docs/access?context=tprm-drtp-reg-contract&family=zurich&ft:locale=en-US) : The General info related list has now been renamed as Details and the following related lists have been added: * Entities signing contract to use service * Entities making use of services * Entities providing services * Third parties signing contract to provide services * Third-party engagements signing contract * ICT service supply chains * Assessments of the ICT services Coral theme : Coral is now the default theme for Vendor Management Workspace, portal, and mobile experiences. 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. Note: When you're upgrading from Xanadu or Yokohama to Zurich with version 20.1.x of the GRC: Vendor Portal, the application UI themes might not match. The Vendor Management Workspace uses the Polaris theme by default, and the Third-party portal uses the Coral theme by default. Upgrading to Xanadu or Yokohama with version 20.1.x of the GRC: Vendor Portal results in both the Vendor Management Workspace and Third-party portal using the Polaris theme. Upgrading to version 21.x or higher results in both the Vendor Management Workspace and Third-party portal using the Coral UI theme. [Enhanced contract records for Digital Resilience Third-party Information Register in Vendor Management Workspace](https://www.servicenow.com/docs/access?context=tprm-drtp-reg-contract&family=zurich&ft:locale=en-US) : If you have the third-party assessor role \[sn_vdr_risk_asmt.vendor_assessor\], you can now associate multiple entities with a single contract record. This association indicates that all entities have signed the contract and are providing services that are associated with the contract. You can also configure contracts that are based on the supply chain and assessment, upload contract records, and generate reports in Microsoft Excel. To better track these entities and help ensure compliance with Digital Operational Resilience Management (DORA) regulations, related lists have been added to the existing contract records, and existing fields have been reorganized for better usability. | | Australia | [Australia Patch 5](https://www.servicenow.com/docs/access?context=australia-patch-5&family=australia&ft:locale=en-US) : Starting with Australia Patch 5, Now Assist for Third-party Risk Management is now ServiceNow Otto® for TPRM. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. [Default AI model for issue recommendation skill](https://www.servicenow.com/docs/access?context=supporting-information-now-assist-tprm&family=australia&ft:locale=en-US) : After upgrading to version 22.3.4, the issue recommendation skill in ServiceNow Otto for Third-party Risk Management (TPRM) uses Azure OpenAI gpt-4-5-mini as the default model. This update changes the default model for issue recommendations. You can select alternative models, including the newly supported Google Gemini 3.5 Flash, OpenAI GPT 5.1, and OpenAI GPT 5.4 mini, based on your requirements. [Large language models on the ServiceNow AI Platform](https://www.servicenow.com/docs/access?context=exploring-large-language-models&family=australia&ft:locale=en-US) : The Now LLM Service is no longer the default model provider for new or inactive AI assets. A third-party LLM is now selected by default, while existing configurations using the Now LLM Service continue unchanged. The Now LLM Service is still available for manual selection. [Improved handling of skipped conditional questions in SAE assessments](https://www.servicenow.com/docs/access?context=tprm-sae-using&family=australia&ft:locale=en-US) : After upgrading to version 22.3.3, Smart Assessment Engine assessments hide conditional questions that are skipped based on response logic. Sections that contain skipped questions are visually de‑emphasized, and assessments render in a continuous scroll layout.This change affects the assessment review experience only and does not change assessment logic, scoring, or response data. [Comments field in the third‑party portal saves when you leave the field](https://www.servicenow.com/docs/access?context=vendor-portal&family=australia&ft:locale=en-US) : After upgrading to version 22.3.2, the comments field in the third‑party portal saves when you leave the field rather than on every keystroke. [Issue indicators in the third-party portal shown only after submission](https://www.servicenow.com/docs/access?context=vendor-portal&family=australia&ft:locale=en-US) : After upgrading to version 22.3.2, issue indicators appear in the third‑party portal only after an issue is submitted to the third party and the Visible in third‑party portal field is selected. Previously, indicators were visible before submission when the field was selected. [Consolidated assessment email notifications](https://www.servicenow.com/docs/access?context=set_sys_props_for_email&family=australia&ft:locale=en-US) : After upgrading to version 22.3.3, external assessment‑related email notifications are sent as a single consolidated summary instead of individual per‑event messages. Users can configure notification frequency, detail level, and delivery channel in their notification preferences. Multi‑language templates are available. [Assessment count mechanism updated in the third-party portal](https://www.servicenow.com/docs/access?context=vendor-portal&family=australia&ft:locale=en-US) : After upgrading to version 22.3.3, engagement assessment counts in the third-party portal include only active, pending, and in‑progress assessments. Previously, counts included inactive and canceled assessments. [Inactive metrics excluded when copying assessment responses](https://www.servicenow.com/docs/access?context=tprm-assessing-tpr&family=australia&ft:locale=en-US) : After upgrading to version 22.3.3, inactive and retired metrics are excluded when copying responses between assessments. Previously, copying responses could include inactive metrics, causing scoring errors. [Type of ICT services changes cascade to supply chain in DORA reporting](https://www.servicenow.com/docs/access?context=tprm-drtp-reg-contract&family=australia&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 22.3.1, when the Type of ICT services value is updated on a Contractual Arrangements -- Specific Information (B.02.02) record, the ICT service supply chain (B.05.02) is now updated automatically. If a Type of ICT services value is removed from a Specific Information record, the corresponding supply chain records for Rank 1 and higher ranks are also deleted automatically. Previously, Rank 1 supply chain records were generated when the Specific Information record was first created, but subsequent changes or removals did not propagate to the supply chain, requiring manual correction. [Duplicate contractual arrangements detected and warned in DORA Register of Information](https://www.servicenow.com/docs/access?context=tprm-drtp-reg-contract&family=australia&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 22.3.1, duplicate records in the Contractual Arrangements -- Specific Information (B.02.02) table are now detected and handled across three scenarios. When saving a contractual arrangement from the UI, a business rule checks eight composite key fields and blocks the save if a duplicate is found. During Excel upload, duplicate rows are rejected and logged to the upload error report. During CSV package download, duplicate rows in B.02.02 are flagged in the DORA request record's error log; duplicates are warned but not removed from the generated CSV. [Duplicate supply chain rows warned during DORA CSV package download](https://www.servicenow.com/docs/access?context=tprm-drtp-roi-packages&family=australia&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 22.3.1, during CSV package download, duplicate rows in the ICT service supply chains (B.05.02) table are now detected and a warning is added to the request record. This applies to both Rank 1 supply chain records, which are auto-generated from Specific Information records, and higher-ranked records. Additionally, when the Storage of data field is set to No on a contractual arrangement, associated location field values are now cleared automatically. [ServiceNow product tiers](https://www.servicenow.com/docs/access?context=ai-native-sku-overview&family=australia&ft:locale=en-US) : The ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available: * Foundation: AI basics to deliver insights * Advanced: AI to boost productivity across relevant use cases * Prime: Act autonomously with all AI assets, and create your own Depending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents. [Fields added to Create New Excel download/upload request form](https://www.servicenow.com/docs/access?context=tprm-create-report-aggregate-expenses&family=australia&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 22.0.3, the Enable currency conversion and Enable third‑party total expense aggregation fields are available on the Excel download/upload request page. When creating Excel Master Template or Plain‑CSV Reporting Package requests, you can configure these options directly on the form. [TPRM Unified content management page](https://www.servicenow.com/docs/access?context=tprm-ws-ucm-page&family=australia&ft:locale=en-US) : After upgrading to version 22.0.2 and installing the Unified Content Management application, the unified content management module is available in the Vendor Management Workspace. [Simplified third-party element process](https://www.servicenow.com/docs/access?context=tprm-workflow-in-workspace&family=australia&ft:locale=en-US) : After upgrading to version 22.0.1, third‑party elements are now linked to a single third party and can no longer be shared across third parties. Scoring rollups calculate results from element‑level assessments rather than entity records. | | Brazil | [Third-party and engagement element assessments](https://www.servicenow.com/docs/access?context=tprm-monitor-tp-elements&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, you can review element-level assessments across all engagements for a third party. Element-level assessments are no longer scoped to a specific engagement. When you scope an assessment, issue, or task to an element, the Element field is required. This option is available only when the third party uses the Smart Assessment Engine. Third-party and engagement contacts respond to element-scoped assessments in the third-party portal the same way they respond to engagement-scoped assessments. [Risk scoring for third-party elements](https://www.servicenow.com/docs/access?context=tprm-monitor-tp-elements&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, element assessment scores roll up through relationship scores calculated from questionnaire-level evidence, replacing the previous entity-based rollup calculation. Engagement and third-party risk-area calculations include assessments sent on linked elements. Linking an element with existing assessment evidence to a new engagement calculates a risk rating for that link automatically, without requiring a new assessment. [Access external and internal tasks from separate modules](https://www.servicenow.com/docs/access?context=tprm-ws-list-page&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, you can access external and internal tasks from separate modules. The Tasks module is split into External Tasks and Internal Tasks on the list page. This separates external tasks from the internal task functionality added in element collection. [Expanded access to reassign Smart Assessment Engine questionnaires](https://www.servicenow.com/docs/access?context=tprm-portal-questionnaire-ownership&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, the TPR administrator \[sn_vdr_risk_asmt.vendor_risk_admin\], TPR assessor \[sn_vdr_risk_asmt.vendor_assessor\], and TPR manager \[sn_vdr_risk_asmt.vendor_risk_manager\] roles now include the sn_smart_asmt.reassign role. Users with these roles can reassign Smart Assessment Engine questionnaires. [Decimal precision for DORA monetary values](https://www.servicenow.com/docs/access?context=tprm-dora-roi&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, and if you have the TPR administrator \[sn_vdr_risk_asmt.vendor_risk_admin\] role, you can set decimal precision to -6, -3, 0, or 2 for monetary value fields. Previously, only -6, -3, and 0 were supported. This applies to Master Template and CSV downloads. The default precision remains 0. This change doesn't affect UI display, upload and validation, individual table downloads, or database storage. [CSV download applies only filtered records when all records are selected](https://www.servicenow.com/docs/access?context=tprm-excel-upload-download-request&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, when a filter is applied to a list and you select all records for CSV download, only the filtered records are included. Previously, all records were downloaded regardless of the applied filter. [Issue generation rules no longer create issues for hidden questions](https://www.servicenow.com/docs/access?context=tprm-generate-issue-rule&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, an issue generation rule that targets a question with a visibility condition no longer creates an issue when that question is isn't visible to the respondent. Previously, the rule could create an issue for a question the respondent never saw. [Product model record created after SBOM document processing](https://www.servicenow.com/docs/access?context=sbom-activate&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, after a third party submits an SBOM file and processing completes, a product model record is created on the third-party record. The record is visible in the Product Models related list. A plugin dependency is added to support parallel processing. [Legal person identifier validation warns instead of blocking for non-LEI/EUID codes](https://www.servicenow.com/docs/access?context=tprm-dora-roi&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, after a third-party service provider record with a legal person type and a non-LEI/EUID identification code is submitted, you receive a warning. The save is no longer blocked. This applies to both the Vendor Management Workspace and Excel Upload. [Notice period fields accept a value of zero](https://www.servicenow.com/docs/access?context=tprm-validation-roi&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, the notice period fields (`B_02.02.0100` and `B_02.02.0110`) now accept a value of 0. Previously, a value of 0 was rejected as if the field were empty. [Data quality warnings CSV added to CSV ROI report package](https://www.servicenow.com/docs/access?context=tprm-validation-roi&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, the CSV report package includes a Data_Quality_Warnings.csv file in the Consolidated_Reports.zip archive. This file provides supplementary data quality checks beyond the Level 3 (DPM) and Level 4 (LEI) validations. These warnings flag potential data inconsistencies --- such as duplicate rows, missing assessments, orphaned contracts, supply chain gaps, and criticality conflicts --- but don't prevent submission. Addressing them helps maintain data accuracy. Each warning includes the sheet name, row number, contract reference, and a descriptive message. [Parent record navigation added to DORA third-party, third-party engagement, and contract records](https://www.servicenow.com/docs/access?context=tprm-dora&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, a reference field is available on DORA third-party, third-party engagement, and contract records. Use it to navigate back to the related parent record after arriving from a related list. Previously, there was no way to return to the parent record from these pages. [Excel export for DORA Functions requests no longer fails on large datasets](https://www.servicenow.com/docs/access?context=tprm-dora&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, exporting a Functions-type Excel drop-down download and upload request no longer fails when drop-down fields reference large CMDB or reference tables. Results are capped at 10,000 records per drop-down field. [Automated quarterly CSV download for Register of Information reports](https://www.servicenow.com/docs/access?context=tprm-dora-roi&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, a quarterly scheduled job (DORA: Quarterly CSV download) generates the CSV Register of Information report for the previous quarter automatically, copying settings from the most recent download request. Previously, a TPR administrator generated this report manually each quarter. The scheduled job is inactive by default; a TPR administrator \[sn_vdr_risk_asmt.vendor_risk_admin\] can navigate to AllSystem DefinitionScheduled Jobs and activate it before it runs. [Rank 1 supply chain records update automatically when a contract's service provider changes](https://www.servicenow.com/docs/access?context=tprm-dora&family=brazil&ft:locale=en-US) : After upgrading the Digital Resilience Third-party Information Register application to version 23.0.3, and if you change the service provider on a DORA contract record, the associated Rank 1 supply chain records update automatically. The records reflect the new provider or recipient. [Third party field pre-populated when creating an element from an engagement](https://www.servicenow.com/docs/access?context=tprm-tpe-form&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, the Third party field is auto-populated when you create a third-party element from either the third-party record or an engagement's Elements tab. Previously, the field was editable and empty in both cases. [Smart Assessment Engine rating scale available from workspace navigation](https://www.servicenow.com/docs/access?context=tprm-risk-rating-scales-config&family=brazil&ft:locale=en-US) : After upgrading to version 23.0.7, the SAE default rating scale table is available from the Vendor Management Workspace navigation, under Assessment Setup. Previously, this table wasn't accessible from workspace navigation. | [ ] ## Removed Between your current release family and Brazil, some Third-party Risk Management features or functionality were removed. {#dfrn3-thirdpartyriskmanagement-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Third-party Risk Management features or functionality were deprecated. {#dfrn3-thirdpartyriskmanagement-summary__entry__42} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. We're committed to bringing you the latest industry advancements while maintaining sovereignty-focused options, all hosted and governed by ServiceNow with the infrastructure and data protections you rely on today. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the [KB3066214: ServiceNow Otto Model Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3066214) article in the Now Support Knowledge Base. | | Australia | Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. We're committed to bringing you the latest industry advancements while maintaining sovereignty-focused options, all hosted and governed by ServiceNow with the infrastructure and data protections you rely on today. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the [KB3066214: ServiceNow Otto Model Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3066214) article in the Now Support Knowledge Base. * The `grc_business_user` and `grc_reader` roles are no longer directly inherited by TPRM roles. * The `scoring_rule` and `scoring_rule_ref` fields are removed from assessment forms and UI sections. Custom scripts or integrations that reference these fields must be updated. * Assessments using entities are no longer supported. | | Brazil | Now LLM Service : Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. The latest industry advancements are available alongside sovereignty-focused options. All models are hosted and governed by ServiceNow with the same infrastructure and data protections. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the [KB3066214: ServiceNow Otto Model Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3066214) article in the Now Support Knowledge Base. Now LLM Service : Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. The latest industry advancements are available alongside sovereignty-focused options. All models are hosted and governed by ServiceNow with the same infrastructure and data protections. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the [KB3066214: ServiceNow Otto Model Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3066214) article in the Now Support Knowledge Base. | [ ] ## Activation information Review information on how to activate Third-party Risk Management. {#dfrn3-thirdpartyriskmanagement-summary__entry__52} | Release | Release notes | |-|-| | Yokohama | Activation information : Install Third-party Risk Management 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: Third-party Risk Management is available in ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Activation information : Install Third-party Risk Management 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=zurich&ft:locale=en-US). Important: Third-party Risk Management is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Australia | Activation information : Install Third-party Risk Management by requesting it from 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). Note: Third-party Risk Management is available in ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Brazil | Activation information : Install Third-party Risk Management 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=brazil&ft:locale=en-US). Note: Third-party Risk Management 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 Third-party Risk Management we have noted them here. {#dfrn3-thirdpartyriskmanagement-summary__entry__62} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Third-party Risk Management we have noted them here. {#dfrn3-thirdpartyriskmanagement-summary__entry__72} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Third-party Risk Management, such as specific requirements or compliance levels. {#dfrn3-thirdpartyriskmanagement-summary__entry__82} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for the Vendor Management Workspace and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. | | Australia | Accessibility information : The Vendor Management Workspace and the third-party portal include accessibility improvements in this release, including improved color contrast, enhanced focus indicators, skip navigation links, and full keyboard navigation. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Third-party Risk Management we have noted them here. {#dfrn3-thirdpartyriskmanagement-summary__entry__92} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | Localization information : Third-party portal strings are externalized and translated for supported languages. Newly introduced features may have incomplete translations. | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Third-party Risk Management we have noted them here. {#dfrn3-thirdpartyriskmanagement-summary__entry__102} | Release | Release notes | |-|-| | Yokohama | * Pre-populate questionnaires for entities and engagements that are associated with the same active third party by using responses from complete questionnaires. * Respond to questionnaires by using a Microsoft Excel questionnaire template. * Explore and analyze assessment data at various levels by using the Third-party insights dashboard and the TPRM custom analytics dashboard. * Stay aligned with stricter regulatory compliance and emerging third-party risk governance by using the new Standardized Information Gathering (SIG) questionnaire content available for 2025. See [Third-party Risk Management](https://www.servicenow.com/docs/access?context=third-party-risk-mgt-landing-page&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * Use the Document Management system in TPRM to centralize third-party documentation in a searchable repository with metadata, and versioning, access controls. * Use vertical navigation in the Vendor Management Workspace through a customizable panel grouped by related lists for improved access to third-party records, assessments, and performance pages. * Configure risk areas with weighted questions and scored responses for internal assessments using the Smart Assessment Engine in the Vendor Management Workspace. * Use the latest Smart Assessment Engine questionnaire templates to perform internal and external assessments. * Use the enhanced Digital Resilience Third-party Information Register features in the Vendor Management Workspace. See [Third-party Risk Management](https://www.servicenow.com/docs/access?context=third-party-risk-mgt-landing-page&family=zurich&ft:locale=en-US) for more information. | | Australia | [Australia Patch 5](https://www.servicenow.com/docs/access?context=australia-patch-5&family=australia&ft:locale=en-US) Starting with Australia Patch 5, Now Assist for Third-party Risk Management is now ServiceNow Otto® for TPRM. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. * Reduce manual data entry by using AI to pre‑fill questionnaires for third-party contacts and business owners. * Use updated Standardized Information Gathering (SIG) questionnaire content for 2026. * Automate Software Bill of Materials (SBOM) collection, integration, and vulnerability correlation with Unified Security Exposure Management (USEM) integration. * Manage SAE assessment template versions to prevent changes from affecting in‑flight assessments. * Add question-level comments and follow-up capabilities during SAE reviews. * Maintain DORA Register of Information accuracy with automatic supply chain cascading updates and duplicate record detection for contractual arrangement and supply chain tables. * Validate Legal Entity Identifier (LEI) codes against the GLEIF database during Register of Information reporting to identify format errors, checksum failures, and inactive or unissued entities. * Enhance DORA Register of Information reporting with optional currency conversion and third‑party expense aggregation to generate consistent, regulator‑ready reports. * Review the simplified third‑party elements process in the due diligence workflow. * Access the unified content management module in the Vendor Management Workspace to view a centralized library of smart assessment templates. [Australia Patch 1](https://www.servicenow.com/docs/access?context=australia-patch-1&family=australia&ft:locale=en-US) Review the updated AI experience with three licensing tiers. See [Third-party Risk Management](https://www.servicenow.com/docs/access?context=third-party-risk-mgt-landing-page&family=australia&ft:locale=en-US) for more information. [Early availability](https://www.servicenow.com/docs/access?context=australia-all-other-fixes&family=australia&ft:locale=en-US) Use generative AI to recommend TPRM issues for reviewer validation. | | Brazil | * Assess, score, and monitor risk across your third-party relationships, from initial due diligence through ongoing engagement. * Centralize third-party assessments, issue tracking, and remediation in a single workspace. * Manage third-party engagements throughout their life cycle with workflows for ongoing oversight and risk management. See [September 2026](https://www.servicenow.com/docs/access?context=grc-tprm-rn-2026-09&family=brazil&ft:locale=en-US) for more information. | [ ] *[\>]: and then