{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":43205,"path":"release-notes/rn-summary-changes.md","title":"Changes to Australia features and products","bundle":null,"doc_type":null,"release":"australia","body":"\n# Changes to Australia features and products\n\nCumulative release notes summary on changes to Australia features and products.\n\nExisting products were updated and changed in Australia. This includes the renaming of certain buttons or features.\n\n\n
\n\nApplication or feature\n\n\n\nDetails\n\n
\n\nAI Admin Center\n\n\n\n- **[Updated AI Admin Center experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-admin-center-lux-user-experience.md)**\n\nThe Lux experience provides a fresh look and feel for AI Admin Center, featuring revised pages and navigation to enhance your user experience.\n\n\n- **[Calculate savings projections for automation opportunities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-admin-center-set-up-data-source.md)**\n\nUse a single savings profile formula when configuring custom data sets for automation opportunity discovery. Multiple savings projections are no longer supported.\n\n- **[Daily recommendation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-admin-center-set-up-data-source.md)**\n\nThe daily recommendation is no longer visible. Only three default configurations are available for custom data sets.\n\n\n- **[Now Assist Center renamed to AI Admin Center](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-assist-center-landing-page.md)**\n\nThe Now Assist Center application \\(sn\\_na\\_center\\) is now named AI Admin Center. The application navigation and store application listing is updated to reflect the new name.\n\n\n- **[AI Agent Advisor enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-assist-center-view-automation-opportunities.md)**\n\nSeveral features are updated to improve the user experience.\n\n - The AI Agent Advisor section of the AI Admin Center home page is renamed to Automation opportunities.\n - The automation opportunities cards display the record type. Hours time saved is changed to Est cost savings per year. Estimated savings is changed to Est time saved per year. A Review opportunity link displays on the card.\n - The summary on the Resolution Steps page is updated with a description of the problem and source, last updated date, and metrics for records analyzed and estimated time saved per year. The number of resolution steps and AI agents are moved to the respective tabs.\n\n\n
\n\nAI Admin Hub\n\n\n\n- **[Default model provider updated to third-party LLM](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Conversational Help](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/conversational-help-skills.md)**\n\nThe discovery of Conversational Help Skills from the Now Assist panel is no longer configured as auto-enabled.\n\n\n
\n\nAI Agent Advisor\n\n\n\n- **[Updated AI Admin Center experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-admin-center-lux-user-experience.md)**\n\nThe Lux experience provides a fresh look and feel for AI Agent Advisor in the AI Admin Center user interface, featuring revised pages and navigation to enhance your user experience.\n\n\n- **[Calculate savings projections for automation opportunities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-admin-center-set-up-data-source.md)**\n\nUse a single savings profile formula when configuring custom data sets for automation opportunity discovery. Multiple savings projections are no longer supported.\n\n- **[Daily recommendation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-admin-center-set-up-data-source.md)**\n\nThe daily recommendation is no longer visible. Only three default configurations are available for custom data sets.\n\n\n- **[AI Agent Advisor enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-assist-center-view-automation-opportunities.md)**\n\nSeveral features are updated to improve the user experience.\n\n - The AI Agent Advisor section of the AI Admin Center home page is renamed to Automation opportunities.\n - The automation opportunities cards display the record type. Hours time saved is changed to Est cost savings per year. Estimated savings is changed to Est time saved per year. A Review opportunity link displays on the card.\n\n
\n\nAI Agent Studio\n\n\n\n- **[New setup processes for agentic AI assets in redesigned AI Agent Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aias-landing.md)**\n\nThe redesigned AI Agent Studio reimagines the creation and deployment processes for agentic AI assets. New features include automated evaluations built in to the application and easy creation of AI agents for automation opportunities. See [Configure AI Agent Studio settings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/config-aias-settings-new.md) for how to access the previous UI.\n\n\n- **[Platform Analyze task trends agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/incident-trends.md)**\n\nThe Analyze task trends agentic workflow now includes citations for representative records associated with a pattern. Configure the workflow to include open tickets in its analysis by enabling the setting and running a Group Action Framework job to reindex with the new records.\n\n\n- **[Create an external AI agent with the Agent2Agent protocol](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-a2a-agent.md)**\n\nThe name of the button on the agent selection pop-up in the Discover and activate section of the external agents guided setup has been renamed to **Selected**.\n\n\n- **[Set up AI agents](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/set-up-na-aia.md)**\n\nUse GPT-5.4 as the default model for the Orchestrator when Azure OpenAI is the selected LLM.\n\n- **[Select the LLM for AI agents and agentic workflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/select-aia-llm.md)**\n\nThe default third-party \\(3P\\) models have been upgraded to the latest versions - GPT 5.2 to GPT 5.4 to use AI agents and AI Agent Studio.\n\nThe new generative AI Config property records **sys\\_generative\\_ai\\_config** and **sys\\_generative\\_ai\\_prompt\\_config** have been introduced for the following model providers:\n\n - Amazon Bedrock: claude-sonnet-4-6\n - Azure OpenAI: gpt 5.4\n- **[Platform agentic workflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/platform-use-cases.md)**\n\nThe following platform agentic workflows had updates to their admin configurations and behavior in user-generated sessions.\n\n - [Analyze task trends](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/incident-trends.md): Admin configurations for additional filters such as category and service have been added.\n - [Generate my work plan](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/generate-work-plan.md): Additional reasoning information for the generated work plan is now displayed after the plan is created.\n - [Identify ways to improve services](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/service-improvement.md): Admin configurations for additional filters such as category and service have been added.\n\n- **[Manually test the execution of an AI agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/test-ai-agent.md) and [Manually test the execution of an agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/test-aia-use-case.md)**\n\nThe **AI Native** radio button in the Choose a testing mode section on the AI agent and agentic workflow manual testing playgrounds has been renamed to **Premium Chat**.\n\n\n- **[Enable UI validation for agentic AI processes and generative AI skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/na-aia-reference.md)**\n\nThe glide.ai\\_record\\_activity.validation.feature.enabled system property enables UI rule validation \\(such as required fields\\) for AI‑initiated record updates. You can selectively apply this validation based on execution context using additional system properties. For example, glide.ai\\_record\\_activity.ai\\_detection.nap.enabled applies validation to record updates triggered from the ServiceNow Otto panel. Similar properties control validation for AI skills, Virtual Agent, and agent‑initiated actions, as listed in the [Reference for AI agents](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/na-aia-reference.md). This feature is opt‑in and inactive by default.\n\n- **[Create an external AI agent with the Agent2Agent protocol](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-a2a-agent.md)**\n\nThe agent to agent flow actions no longer inject an `Authorization: Bearer` header automatically. If your endpoint requires a Bearer token, include the prefix directly in the API Key credential value.\n\n\n- **[Create an external AI agent with the Agent2Agent protocol](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-a2a-agent.md)**\n\nUse the A2A Protocol integration for creating external agents in the AI Agent Studio to connect with the ServiceNow AI Platform.\n\n- **[Updates to platform agentic workflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/platform-use-cases.md)**\n\nSeveral platform agentic workflows have seen updates to how they work and what configurations are available for AI admins. [Analyze task trends](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/incident-trends.md) and [Identify ways to improve service](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/service-improvement.md) now have post-analysis actions, including the option to download analysis and ask additional information. [Generate my work plan](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/generate-work-plan.md) can run as a scheduled job.\n\n- **[Agentic evaluation offer issue tracing and suggested optimizations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/agentic-evals.md)**\n\nAfter an automated evaluation of an agentic AI asset, you can receive a list of issues and suggested optimizations to address those issues. Issues come with individual record node-by-node traces to pinpoint the exact source of problems. Optimizations are suggested, and you can apply them and run a reevaluation from a single guided flow.\n\n\n
\n\nAI Control Tower\n\n\n\n- **[View input and output in trace details](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/mon-ai-session-details.md)**\n\nToggle between input and output when viewing trace details.\n\n- **[Usability improvements to Security Overview metrics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-reference.md)**\n\nSee only actionable items in your top recommendations on the Security Overview tab. In addition, the recommendations rank AI agent insights by number of critical security events and show the agent name, critical event count, and top threat categories. The security events list now matches the list on the Post-runtime tab. The Access issues detailed view includes a description that explains each access issue in plain language—identifying the agent, the operation, the resource, and the denial count.\n\n- **[Domain separation and AI Control Tower](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-domain-separation.md)**\n\nReview sensitive data metrics for ServiceNow AI systems in a domain-separated instance. Available on the Runtime tab in Security.\n\n- **[Configure Excessive Agency in Security](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-configure-event-metrics.md)**\n\nControl whether Excessive Agency is enabled in Post-runtime configuration in Security. This setting controls data for Access issues and Privileged AI agents metrics, as well as post-runtime metrics. The setting is off by default.\n\n- **[Post-runtime Security probabilistic metrics and AI agent disabled by default](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-configure-event-metrics.md)**\n\nTo reduce token consumption, screening for data integrity incident detection, system prompt leakage, correctness detection, prompt injection, and agent goal deviation is disabled by default. In addition, the Security Analyzer agent that determines security event severity and insights is disabled by default. The default sampling rate for all metrics is 1%. If you're upgrading, your Detection enabled setting for each metric isn’t affected. After upgrading, check your settings in **Settings** > **Rules and templates** > **Security** and adjust if needed.\n\n\n- **[Domain separation and AI Control Tower](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-domain-separation.md)**\n\nUse AI Control Tower on a domain-separated instance. In Security, detail pages for some metrics include a Domain column that shows the domain the AI asset belongs to, or shows `global` or is empty if domain separation isn't configured.\n\n- **[Domain separation and AI Control Tower](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-domain-separation.md)**\n\nUse AI Control Tower on a domain-separated instance. In Security, detail pages for some metrics include a Domain column that shows the domain the AI asset belongs to, or shows `global` or is empty if domain separation isn't configured.\n\n- **[Governing AI asset security](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-ai-asset.md)**\n\nAgent status is renamed to Access posture on the Security tab for an AI asset. Also, Detection time is now the first column in the list of events.\n\n- **[Design-time metrics reorganized into subtabs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-reference.md)**\n\nDesign-time metrics are organized into three subtabs: AI security posture, AI vulnerabilities, and AI validation. If the AI Security Exposure Management plugin isn't installed, use the source dropdown to filter the metrics by asset source \\(for example, ServiceNow or AWS Bedrock\\).\n\n- **[Governing AI asset security](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-ai-asset.md)**\n\nOn the Security tab for an AI asset, a metric isn't shown if there's no data available for the asset. Also, access issues and access posture don't appear for AI models.\n\n- **[Governing AI asset security](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-ai-asset.md)**\n\nAI agent containment using kill switch protocol is now available directly from an AI asset's Overview tab, not just its Security tab, for security events of any severity. It also supports retrying a failed or partial containment operation. You can also deactivate any managed AI agent directly from its asset record, whether or not it has an associated security event.\n\n- **[Configuring security connections](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-configuring-security-connections.md)**\n\nThe Security tab under **Settings** > **Integrations** is renamed to Control Enforcement Points.\n\n- **[Add a Gemini Enterprise Agent Platform connection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-configure-gcp-vertex-ai-security-connection.md)**\n\nThe GCP Vertex AI security connector is renamed to Gemini Enterprise Agent Platform.\n\n- **[Agent containment list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-review-kill-switch-protocol-log.md)**\n\nThe Kill Switch Protocol Log is renamed the Agent containment list, and the **View details** option on the containment banner is renamed **View containment options**. The list now includes Domain and Actions columns. Containment details now show how the containment was initiated \\(Manual or Automated\\) and identity and enforcement details. The list can be filtered using the All, In progress, or Contained options, which replace the previous Show all link.\n\n- **[AI Gateway](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-gateway.md)**\n\nStarting in the September 2026 release, AI Gateway is available in AI Control Tower.\n\n- **[Configuring connectors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-configuring-connectors.md)**\n - The GCP Vertex AI connector is renamed to Gemini Enterprise Agent Platform.\n - The application AI Service Graph Connector for GCP is renamed to AI Service Graph Connector for Google.\n - The Salesforce connector is renamed to AI Connector for Salesforce.\n\n- **[New AI Control Tower experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-ai-portfolio-overview.md)**\n\nThe new AI Control Tower provides a more efficient, streamlined way for you to work. For information about how to upgrade, see the [AI Control Tower Migration \\[KB3144679\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3144679) article in Now Support. Note that the legacy AI Control Tower workspace is still supported in this release.\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n- **[Discover your agent network with the map](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-use-map.md)**\n\nThe access map is renamed to agent map and shows Veza access intelligence and node details for AI assets, giving you a holistic view of your enterprise.\n\n- **[Configure post-runtime security metrics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-configure-event-metrics.md)**\n\nYou can now adjust the sampling rate for more Post-runtime metrics.\n\n- **[Managing AI asset security reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-reference.md)**\n\nImproved accuracy of AI threat metrics and evaluation datasets that use Traceloop for continuous monitoring in Overview and Runtime metrics. Access issues metrics now support external agents. Azure, Google Cloud Platform \\(GCP\\), and Google Vertex AI assets are now supported.\n\n- **[Governing AI asset security](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gov-sec-ai-asset.md)**\n\nThe Security tab of the AI asset record shows the AI asset security score and metrics for an individual asset.\n\n- **[AI Service Graph Connector for GCP Vertex AI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/gcp-vertex-ai.md)**\n\nThe Service Graph Connector for GCP Vertex AI now displays as \"AI Connector for Google\" to align with the AI Connector naming convention.\n\n- **[Risk Management tasks for Asset owner](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/aict-activity-center.md)**\n\nUsers with the AI Asset Owner \\[sn\\_ai\\_asset\\_mgmt.ai\\_asset\\_owner\\] role can access and act on risk and compliance lifecycle tasks, such as impact assessments and control attestations, from the Activity Center. The Activity Center surfaces AI asset tasks, issues, policy exceptions, and AI cases for the asset owner. On the asset record page, all lifecycle tasks specific to the assigned assets can be accessed and performed.\n\n- **[Unifying lifecycle tasks for Risk and Compliance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/risk-compliance-lifecycle-tasks-aict.md)**\n\nIn the legacy AI Control Tower workspace, users with the AI Steward \\[sn\\_ai\\_governance.ai\\_steward\\] and AI Risk and Compliance Analyst \\[sn\\_grc\\_ai\\_gov.ai\\_risk\\_and\\_compliance\\_analyst\\] roles can take and manage risk assessments directly from the Playbook. This eliminates the need to switch between workspaces.\n\n\n- **[AI record type label](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/view-ai-assets-lifecycle-stage.md)**\n\nThe AI assets \\(sn\\_grc\\_ai\\_gov\\_ai\\_system\\) table has been renamed to AI records \\(sn\\_grc\\_ai\\_gov\\_ai\\_system\\). The **Record type** field on AI system, AI model, and dataset records in the AI Control Tower inventory now displays **AI record** instead of the previous asset-specific labels.\n\n\n- **[Drop-down menu for associating AI assets with related assets](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/view-ai-assets-lifecycle-stage.md)**\n\nIn both the AI asset creation forms and AI asset records, the **Add new** button that previously enabled you to associate AI assets with other related assets has changed into an Add from inventory drop-down menu with the **Add from inventory** and **Create** options. The **Add from inventory** menu option enables you to associate AI assets with related assets that are currently available in your asset inventory. The **Create** menu option enables you to associate AI assets with related assets that aren't currently available in your asset inventory.\n\n- **[Editable asset details fields on the Details tab of AI asset records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/view-ai-assets-lifecycle-stage.md)**\n\nYou can now modify asset details fields directly on the **Details** tab of your AI asset records.\n\n- **[Related asset lists in AI asset records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/view-ai-assets-lifecycle-stage.md)**\n\nThe lists of related assets in each AI asset record has moved from the **Related assets** tab to the **Details** tab.\n\n\n
\n\nAI Desktop Actions\n\n\n\n- **[Claude Sonnet 4.6 supported](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-llm-model-updates.md)**\n - Adaptive desktop actions now support version 4.6 of Claude Sonnet. It is now the default model for adaptive desktop actions.\n - Use function keys \\(F1–F12\\) and combo keys \\(cmd+a, alt+F4, ctrl+c\\) in desktop automation without manual intervention.\n\n- **[Browser startup and tab behavior](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/na-ai-wa-access-using-nap.md)**\n\nBrowser session now opens to an empty page instead of Google's homepage. Automation actions within the same chat window now reuse the existing browser tab instead of opening a new tab for every action. A new tab opens only when a new chat session starts or you close the current tab.\n\n- **[Improved security for adaptive desktop actions system properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/components-installed-with-agentic-desktop.md)**\n\nAdaptive desktop actions system properties now require appropriate read and write roles. This change prevents unauthorized users from viewing or modifying the configuration settings, while automation continues to work as expected.\n\n\n- **[Renamed ServiceNow AI experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/agentic-desktop-landing-page.md)**\n\nServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including AI Desktop Actions. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n\n- **[Optional Application name field](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/add-details-desktop-action-ad.md)**\n\nThe Application field in the Details tab is now optional, enabling you to save and run desktop actions without entering an application name.\n\n- **[Improved connectors descriptions for non-UI block desktop actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/desktop-actions-designer-workspace-ad.md)**\n\nDescriptions for Excel, Word, PDF, and System Actions connectors are enhanced to improve accuracy and selection.\n\n\n
\n\nAI Risk and Compliance\n\n\n\n- **AI record labels**\n\nThe AI assets \\(sn\\_grc\\_ai\\_gov\\_ai\\_system\\) table has been renamed to AI records \\(sn\\_grc\\_ai\\_gov\\_ai\\_system\\). Two field labels on AI system, AI model, and dataset record pages in the AI Risk and Compliance Workspace have changed. The **Record type** field now displays **AI record** instead of the previous asset-specific labels. On AI system records, the **Asset type** field has been replaced by **Parent category**, which displays **AI system**.\n\n\n- **[Smart Assessment Engine template versioning](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/airc-assessment-templates.md)**\n\nAfter upgrading to version 22.3.5, if you have the AI risk and compliance admin \\[sn\\_grc\\_ai\\_gov.ai\\_risk\\_and\\_compliance\\_admin\\] role, you can use Smart Assessment templates that support versioning. A new version is created automatically when you edit and save a template. Publishing a new version retires the previously published version. Existing templates are set to Version 1.\n\n- **[Assessment scope context in task and work queue lists](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tasks-ai-risk-compliance.md)**\n\nAfter upgrading to version 22.3.5, if you have the AI risk and compliance analyst \\[sn\\_grc\\_ai\\_gov.ai\\_risk\\_and\\_compliance\\_analyst\\] or AI risk and compliance manager \\[sn\\_grc\\_ai\\_gov.ai\\_risk\\_and\\_compliance\\_manager\\] role, assessment task list and work queue views display additional columns that show the governance scope \\(related entity such as AI asset, model, or dataset\\) of each control attestation-based assessment. These columns let you identify which AI asset, entity, and control an assessment belongs to without opening the individual record.\n\n- **[Impact assessment field auto-population](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/airc-intake.md)**\n\nAfter upgrading to version 22.3.5, if you have the AI asset owner \\[sn\\_ai\\_asset\\_mgmt.ai\\_asset\\_owner\\] or AI risk and compliance business user \\[sn\\_grc\\_ai\\_gov.ai\\_risk\\_and\\_compliance\\_business\\_user\\] role, the screening question responses that capture the AI system's intended use and operational context from the Use and Purpose section of the AI use case request form are automatically populated in the corresponding Use and Purpose fields of a new impact assessment. This synchronization reduces manual entry and helps ensure that impact assessment responses are consistent with the information submitted at intake.\n\n- **[AI Risk and Compliance Content Pack regulatory frameworks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/airc-content-pack.md)**\n\nAfter upgrading to version 22.3.0, if you have the AI Risk and Compliance Content application installed and the admin role, the AI Risk and Compliance content pack includes additional authority documents, agency mappings, and citations for the following regulatory frameworks: the Transparency in Frontier Artificial Intelligence Act \\(SB 53\\) and the Colorado Artificial Intelligence Act \\(SB 205\\). When at least one regulatory framework is activated, control objective records display citations from all activated authority documents in the **Citations** tab. This enables you to assess cross-framework regulatory coverage from a single control objective record without navigating each framework separately.\n\n\n- **[Operations tab](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/operations-tab.md)**\n\nOn the Operations tab in the AI Risk and Compliance Workspace, the AI systems by state section includes an Offboard state to track AI systems in retirement or offboarding and the AI systems by department section now supports grouping by Risk classification from the Show by drop-down list to view the distribution of AI systems in each department.\n\n- **[AI use case request form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/airc-intake.md)**\n\nA Use and Purpose section containing screening questions has been added to the AI use case request form to capture contextual information about how an AI system will be used and supports automated risk‑based classification during submission.\n\n- **[AI system record page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/ai-system-airc.md)**\n\nA Use and Purpose section has been added to the AI system record page, which you can access from the AI asset inventory list in the AI Risk and Compliance Workspace.\n\n- **[Anonymous AI case reporting](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/airc-cases-inquiries.md)**\n\nA Visit Anonymous Reporting Center card is available in the Support resources section of the AI assets page in the Employee Center, enabling you to navigate to the Anonymous Reporting Center to submit an anonymous AI case.\n\n\n
\n\nAI Search\n\n\n\n- **[Summary Genius Results](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/now-assist-multi-content-qna-genius-results.md)**\n\nIf you have Now Assist in AI Search installed, Now Assist Multi-Content Response Genius Results are supported in global and workspace search. Activating Now Assist Multi-Content Response Genius Results in global or workspace search profiles overrides all other Genius Result configurations, so that global and workspace searches only display Genius Result answers from Now Assist Multi-Content Response Genius Results. Virtual Agent topic citations from Now Assist Multi-Content Response Genius Result answers in global or workspace search open the selected topic in the Now Assist panel so the user can continue their conversation on that topic.\n\n- **[Search Suggestions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/search-suggestions-overview.md)**\n\nSearch administrators with the ais\\_admin granular admin role can access all Search Suggestions tables. Assign search administrators this role to eliminate needless propagation of full admin access.\n\n- **[Gain insights into search behavior with a refreshed and updated Search Preview UI.](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/search-preview-ui-new.md)**\n\nPreview search query results using settings from a search application configuration or a search profile. Choose between keyword and hybrid search modes. Display search results as individual EVAM cards or as a JSON-format search query response object, with search and syntax highlighting. Review search query behavior and results and specify search query settings with the new Summary, Genius Results, Details, and Profile admin tools.\n\n\n
\n\nAPI\n\n\n\nThe following tables lists changed API classes and methods in Australia and ServiceNow Store.\n\n
\n\nAccess Management\n\n\n\n- **[Query ACLs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/query-acl-rule.md)**\n\nQuery ACLs now load automatically during plugin installation for most platform plugins. These preconfigured ACLs reduce the need to run the QueryRangeACLAuditor tool to generate query ACLs. Store app query ACLs aren't included in preconfigured query ACLs. For more information about preconfigured query ACLs, see the [Maintenance Information \\[KB2046494\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2046494) article in the Now Support Knowledge Base.Existing custom query ACLs are preserved and loaded as inactive. To view inactive ACLs, use this command: `/sys_security_acl_list.do?[query_parameters]`QueryRangeACLAuditor tool modifications are preserved.\n\n- **[ACL types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/acl-rule-types.md)**\n\nCore field and datatype ACLs are replaced with more comprehensive rules to optimize ACL volume.\n\n\n
\n\nActivity Management\n\n\n\n- **[Correct identification of sent emails](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/associate-email-crm-outlook.md)**\n\nDistinguish sent emails from received emails in your CRM activity history. Sent emails associated through the ServiceNow CRM for Outlook add-in now appear correctly classified as sent in the associated record's Emails tab. Previously, all emails associated through the add-in classified as received in the CRM workspace. When you create a new lead or contact from a sent email, the form now pre-populates with the recipient's details instead of your own.\n\n- **[Tab visibility follows write permissions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/associate-email-crm-outlook.md)**\n\nShow the Accounts, Contacts, Leads, and Opportunities tabs in the ServiceNow CRM for Outlook add-in based on a user's write permission for the underlying entity table rather than fixed role assignment.\n\n- **[Session timeout recovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/associate-email-crm-outlook.md)**\n\nReturn to the ServiceNow CRM for Outlook add-in home page after re-authenticating when your session times out. The add-in opens its own sign-in form and brings you back to the home page on successful authentication, instead of redirecting you to the ServiceNow platform home page as in previous releases.\n\n- **[Pre-applied filters on entity tabs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/associate-email-crm-outlook.md)**\n\nFind relevant CRM records faster when associating an email. Each entity tab in the ServiceNow CRM for Outlook add-in pre-applies filters based on the email's sender or recipient name and domain, so you see only the records most likely to match instead of every record in the table.\n\n\n- **[Account and Contact field auto-population](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/create-crm-touchpoint.md)**\n\nReduce manual data entry when creating touchpoints by automatically populating the Account and Contact fields when you select an Associated Entity and Associated Record of type Contact, Account, Lead, or Opportunity. Associated Entity and Associated Record fields become read-only after the touchpoint record is created.\n\n\n
\n\nAdoption Services\n\n\n\n- **[genai\\_admin role in Dynamic Guidance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure.md)**\n\nThe sn\\_dyn\\_guidance\\_user role now includes the role. When you assign sn\\_dyn\\_guidance\\_user to a user, the genai\\_admin role is automatically granted.\n\n\n
\n\nAdvanced Risk\n\n\n\n- **[Risk event enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/manage-risk-events.md)**\n\nRisk event administrators can manage the entire risk event workflow. This update grants permissions aligned with the Risk Manager role, including the ability to reopen closed risk events.\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n
\n\nAgent experience for CSM\n\n\n\n- **Knowledge article link insertion from Recommended Actions**\n\nSelecting any of the three attach knowledge article options for work notes, comments, or email from the Recommended Actions panel now automatically switches to the relevant target tab, so the inserted link is immediately visible without manual navigation. Inserted links also now display the article title alongside the article number as a hyperlink, replacing the previous article-number-only display. This enhancement applies to the Front-line case page and CSM default record page.\n\n\n- **[Editable record headers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-workspace-agent-actions.md#section_hhb_1tj_23c)**\n\nEnables agents to edit the short description of a record directly from the header field. This feature is available on the following record pages:\n\n - Front-line case page\n - CSM Interaction record page\n - CSM default record page\n- **[Collaborate component in CRM Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-config-ws-collaborate-component.md)**\n\nUse the Collaborate component in the contextual side panel in CRM Workspace to communicate and collaborate with stakeholders in real time to resolve cases.\n\n- **[SLA component on the Front-line case page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-front-line-case-page.md)**\n\nUse the Service Level Agreement \\(SLA\\) component in the contextual side panel on the Front-line case page to view SLAs. The SLA cards appear in the Record Information tab below the record information card.\n\n- **[Email Interaction record page enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-email-interaction-record-page.md)**\n\nMinimize drafts to a dock at the bottom of the workspace page in the inline modeless composer. View activities in the activity feed at the top of the page in reverse order, with the newest entries displayed at the bottom.\n\n- **[Lookup component added to the Email Interaction record page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-email-interaction-record-page.md)**\n\nEnable agents to look up contacts and consumers by name, phone number, or email address and link them to a record.\n\n- **[Create actions on the Front-line case page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-config-ws-action-layout-groups.md)**\n\nCreate different types of records by using the **Create** button on the Front-line case page. Selecting an action from the Create button, such as creating an incident or a knowledge gap, opens the form in a modeless dialogue.\n\n- **[View attachments in modeless dialogs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-front-line-case-page-modeless-dialogs.md#section_sk4_drr_23c)**\n\nEnable agents to access and review attachments in modeless dialogs instead of workspace tabs. Agents can easily view attachments while also viewing case information and drafts of emails, comments, or work notes.\n\n- **[Auto-dismiss alerts in CSM Configurable Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/auto-dismiss-alerts-in-csm-configurable-workspace.md)**\n\nReduce visual clutter through auto-dismissible alerts, which are enabled by default for Info, Low, and Moderate alerts, with a default timer of five seconds. Critical and High alerts remain persistent to ensure important notifications stay visible.\n\n- **[Maximum number of active tabs in CSM Configurable Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-config-workspace-interface.md)**\n\nAgents can open up to 20 active tabs \\(previously 10\\) in CRM Workspace to handle multiple tasks simultaneously without losing context.\n\n- **[Open multiple lists in separate primary tabs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-config-workspace-list-views.md)**\n\nAgents can now open multiple lists in different CRM Workspace primary tabs, enabling seamless context switching between lists without losing their current workspace view.\n\n- **[Granular admin roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/r_RolesInstalledWithCustomerService.md)**\n\nEnhance security, reduce over-privileged accounts, and enable flexible, task-focused permission management by assigning granular, feature-specific roles to replace broad admin access.\n\n\n
\n\nApp Engine Management Center\n\n\n\n- **[Filter and search for requests in AEMC](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/filter-search-aemc.md#section_kvc_43q_dtb)**\n\nFilter by key fields, such as status, owner, type, environment, and date, with the option to apply multiple filters simultaneously for the **Requests** tab. Filtered results update in realtime, and active filters are clearly indicated. Remove individual filters, reset the list to its default state, and save your commonly used filter combinations to reuse later.\n\n\n
\n\nApplication Manager\n\n\n\n- **Coral theme**\n\nThe Coral theme has been improved to enhance usability across web, mobile, and portal experiences that use Next Experience and Core UI:\n\n - A fully overhauled color system for smoother gradients and better contrast.\n - Softer outlines and more rounded components for a modern, accessible look.\n - A significantly improved dark mode with deeper blue tones for reduced eye strain.\n - New AI gradient styles and subtle animations to highlight intelligent features.\n - Smarter focus behavior that reduces visual clutter for mouse users.\n\n- **[Unlicensed application information](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/available-for-you-app-mgr.md)**\n\nIn addition to details about applications that are already licensed, the \"Available for you\" tab of the Application Manager now includes information about applications that haven't been procured from the ServiceNow Store yet.\n\n\n
\n\nAsset Audit Response\n\n\n\n- **[Now Assist to ServiceNow Otto® name change](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-products.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n
\n\nAuthentication\n\n\n\n- **[OAuth enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/api-inbound-and-outbound.md)**\n\nFollowing are the OAuth enhancements:\n\n - Use **Opaque** or **JWT** token option for your inbound integration endpoints.\n - Use the **Allow access only to APIs in selected scope** option to enable access to the APIs that are explicitly listed in the selected scopes for your inbound integrations.\n - Use the OAuth Entity Resource tab for outbound integrations to configure resource parameters so they flow into the OAuth token request and are reflected in the token from your OAuth provider.\n\n
\n\nAutonomous Workforce\n\n\n\n- **Advanced search turned on by default**\n\nSee more richer and more relevant results to searches performed by the AI specialist.\n\n- **Follow-up metric added to AI specialist performance dashboard**\n\nMonitor where requests stall and where guidance can be clearer by tracking the follow-ups necessary after an initial response by the AI specialist.\n\n\n
\n\nBuild Agent and Autonomous Engineer\n\n\n\n- **Autonomous Engineer Test Agent settings enabled by default**\n\nThe Test Agent settings for Autonomous Engineer are enabled by default.\n\n- **Larger input box for extended prompts**\n\nThe input field for Build Agent and Autonomous Engineer prompts and instructions now expands to accommodate longer text entries.\n\n\n- **[Build Agent in ServiceNow Studio UI updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/access-build-agent.md)**\n\nSeveral changes have been made to how you access Build Agent in ServiceNow Studio:\n\n - The central chat area on the ServiceNow Studio home page is the starting point for new Build Agent conversations.\n - To open an existing conversation, select the Conversations icon \\[Omitted image \"ba-sns-otto-nav-icon.png\"\\] Alt text: in the Navigator panel.\n - The Build Agent panel now opens on the Navigator panel of ServiceNow Studio.\n\n- **[Organized settings with tabs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/ba-configure-settings.md)**\n\nFind Build Agent easier now that the Settings panel has tabs: **General**, **Skills**, **Rules**, and **MCP**.\n\n\n- **[ServiceNow Otto rebrand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/exploring-build-agent.md)**\n\nServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including Build Agent. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n- **[Licensing change for in-app agents and skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/ba-about-creating-in-app-agents.md)**\n\nOnly users with Build Agent - Prime can create agents and skills.\n\n\n- **[Enhanced semantic metadata search tool](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/build-agent-tools.md)**\n\nAn updated semantic metadata search tool improves performance replaces the previous semantic search tool.\n\n\n- **[New button prompt to add AI to an app](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/create-a-new-application-using-build-agent.md)**\n\nA new **Add AI** button when you first open the Build Agent chat panel starts a guided conversation to help you define and generate a skill or agent.\n\n**Note:** You must have a ServiceNow Otto for Creator license for the new button to appear.\n\n- **[Open Build Agent from ServiceNow Studio banner](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/access-build-agent.md)**\n\nA new icon in the ServiceNow Studio application banner provides another way to access Build Agent.\n\n\n- **[Improved checkpoint and update set management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/ba-conversational-change-log.md)**\n\nBuild Agent handles checkpoints and update sets differently in the following ways:\n\n - Checkpoint 0 no longer creates an update set.\n - Checkpoint 1 is the base update set for all subsequent changes.\n - Update sets use human-readable naming.\n\n- **[Generated artifact preview](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/edit-an-existing-application-using-build-agent.md)**\n\nPreview generated tables, flows, and scripts that Build Agent creates in ServiceNow Studio so you can review and approve changes inline before saving or committing them to the application.\n\n\n\n- **[Build Agent version parity for PDIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/exploring-build-agent.md)**\n\nPersonal development instances \\(PDIs\\) are now updated to match the latest Build Agent version, delivering a consistent experience across both personal and production-track instances. Developers testing and building on PDIs have access to the same capabilities available in production environments.\n\n- **[Updated interaction limits](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/exploring-build-agent.md)**\n\nTo provide developers more room to iterate, the following Build Agent limits have been increased:\n\n - Build Agent \\(Trial\\): 100 prompts per instance per 30-day cycle\n - PDIs: 25 prompts per instance per cycle\n**Note:** Limits are per-instance, not per-user. Only submitted prompts contribute to the limit. Plan approvals are not counted.\n\n\n- **[Support for global scope](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/exploring-build-agent.md)**\n\nBuild apps and metadata in the global scope.\n\n\n
\n\nBusiness Continuity Management\n\n\n\n- **[Recovery strategy templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/configure-recovery-strategy-template-uib-ws.md)**\n\nThe Recovery strategy template form is used to create reusable templates that can be applied to recovery strategies across loss scenarios and business continuity plans.\n\n- **[Task template integration in plan templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/configure-a-bcp-template-uib-ws.md)**\n\nPlan templates support two synchronization options: Plan scope asset synchronization and Loss scenario asset synchronization with recovery strategy assets.\n\n- **[Related lists for Plan templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/plan-template-form.md)**\n\nThe Plan templates record has the following related lists:\n\n - Task template groups\n - Task templates\n- **[Related lists for Loss scenarios](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/add-loss-scenario-recovery-task-bcp-uib-ws.md)**\n\nThe Loss scenarios record has the following related lists:\n\n - Task template groups\n - Task templates\n - Recovery strategies\n - Plan templates\n- **[Related lists for Recovery strategies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/create-new-recovery-strategy-for-loss-scenario-uib-ws.md)**\n\nThe Recovery strategies record has the following related lists:\n\n - Task template groups\n - Task templates\n - Loss scenarios\n - Plan templates\n- **[Recovery tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/create-quick-recovery-task.md)**\n\nThe recovery task list includes four additional columns: Plan loss scenario, Plan recovery strategy, Tag, and Task group. Use these columns to filter, group, and report on recovery tasks by scenario, strategy, or template group.The recovery task list toolbar includes **Insert** \\(with Select task template groups\\), **Save as group** \\(with Add to group and Save tasks sub-options\\), and **Add groups** for bulk insertion of task template groups.The Create a quick recovery task panel includes Phase, Plan recovery strategy, All assets from plan, and a Planned duration field accepting hours, minutes, and seconds. The All assets from plan field can be narrowed to a subset of assets when a task applies to only part of the plan.A Gantt view is available on the **Recovery tasks** tab of a plan record.\n\n- **[Event task list toolbar](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/export-import-event-tasks-using-excel.md)**\n\nThe event task list toolbar adds **Export to Excel** and **Import from Excel** actions for managing tasks in bulk and switching between list and Gantt views.\n\n- **[Loss scenario Recovery tasks tab](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/add-loss-scenario-recovery-task-bcp-uib-ws.md)**\n\nEach loss scenario record includes a **Recovery tasks** tab that lists only the recovery tasks scoped to that scenario.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n
\n\nCard data security\n\n\n\n- **[Attachments panel](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/manage-attachments-in-card-data-security.md)**\n\nA UI builder page has been added to display external documents from card networks, acquirers, and merchants at the transaction level when Card data security is installed.\n\n\n
\n\nCase management for CSM\n\n\n\n- **[Granular viewer roles for Case Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/customer-service-management-roles.md)**\n\nAdded new read-only roles within Case Management. These include the following:\n\n - Customer Service All Case Viewer \\[sn\\_customerservice.all\\_cases\\_viewer\\]\n - Case Playbook for Complaint Viewer \\[sn\\_complaint.viewer\\]\n - Case Playbook for Onboarding Viewer \\[sn\\_onboarding.viewer\\]\n - Action Status Viewer \\[sn\\_action\\_status.viewer\\]\n - Customer Service Document Template Viewer \\[sn\\_csm\\_doctemplate.viewer\\]\n - Case Digest Viewer \\[sn\\_csm\\_case\\_digest.viewer\\]\n - Customer Project Management Viewer \\[sn\\_csm\\_ppm.viewer\\]\n - Case Type Configuration Viewer \\[sn\\_scm\\_case\\_type.config\\_viewer\\]\n - Case Line Viewer \\[sn\\_case\\_line.viewer\\]\n- **[Major Issue Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/major-issue-management.md)**\n\nCase Type consistency improvements: This update ensures case type consistency when creating and managing major cases and their related child cases, improving accuracy and reducing manual correction.\n\n - Create major cases automatically upon approval, and major cases now inherit the same case type as the originating case.\n - Promote the proposed case directly to a major case I-if no account or consumer or partner exists on the originating major case.\n - Use the major case's case type and inherit the fields defined in \\(sn\\_customerservice.case\\_fields\\_to\\_sync\\) property or defined through extension point for child cases.\n- **[Task plan templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/task-plan-templates.md)**\n\nAdd flexible task dependency management to task plan templates, and support for attachments.\n\n - Schedule offsets can be defined when creating dependencies, allowing tasks to start within a specified time period \\(minutes, hours, days, or weeks\\).\n - Configure and manage task dependencies directly from task dependency list and view layouts.\n - Built‑in validations prevent circular dependencies, ensuring task plans remain accurate and reliable.\n - Ability to attach documents to tasks or cases.\n - Select **Apply Template** for any published task plan templates to automatically add all document references from the original template items to the newly created tasks, ensuring seamless access for task owners to all required documents.\n- **[Case type selector for creating cases](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/create-case-of-specific-case-type.md)**\n\nThe case type selector is now activated by default when creating cases of these types:\n\n - Interaction\n - Account\n - Contact\n - Consumer\n - Sold product\n - Install base item\n - Related lists: child case, case task\n - List view\n - Case task list view\n\n
\n\nClone Admin Console\n\n\n\n- **[Updated authentication model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/configure-target-instance.md)**\n\nClone Admin Console now uses JWT certificate-based authentication instead of username and password authentication, improving security and simplifying cross-instance authentication.\n\n\n- **[Updated clone menu navigation items](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/system-clone-landing.md)**\n\nAll clone-related functions are now available under the Clone Admin Console menu navigation item.\n\n- **[Submit a new clone even if another clone is scheduled](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_StartAClone.md)**\n\nCreate an additional clone request even if there’s already a future clone for that target. This feature removes the previous limitation where any new clone requests were not allowed until all existing requests were canceled. You can now submit new clone requests if more than five days apart from existing ones.\n\n- **[Clone summary](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_StartAClone.md)**\n\nHelp prevent clone conflicts with the **Clone summary**, which highlights clones that are scheduled in the next 30 days that involve the same target instance.\n\n- **[Configuration tab](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/system-clone-landing.md)**\n\nAll clone-related settings are now grouped under a single **Configuration** tab for improved organization and discoverability.\n\n- **[Clone Home Renamed to Clone Activity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/system-clone-landing.md)**\n\nThe **Clone Home** menu item has been renamed to **Clone Activity** to be more descriptive of the page's purpose and improve navigation clarity.\n\n- **Clone profile script updates**\n\nFixed an issue where setting a script in the clone\\_cleanup\\_script table to active=false or active=true did not apply consistently across all clone profiles the script was listed on. Changes now propagate correctly.\n\nBoth the source and target instances must be on Australia Patch 5 or a subsequent release to use cleanup script status.\n\n\n
\n\nCloud Cost Management\n\n\n\n- **[Optimization view on the Cloud Cost Management Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/optimization-view-ccm-ws.md)**\n\nThe Recommendations have been moved from the Operations view to the newly added Optimization view in the Cloud Cost Management Workspace. The Optimization view shows savings opportunities and recommendations for you across Unused resources, Rightsizing, Business hours, and Commitments.\n\n\n- **[Multi-currency setup on the Operations view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/operation-view-ccm-ws.md)**\n\nThe **Multi-currency setup** operation is available on the Cloud Cost Management Workspace Operations view to enable setting up display currency options for cloud cost and usage data.\n\n- **[Currency preference option on the Operations view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/operation-view-ccm-ws.md)**\n\nThe **Currency preference** operation is available on the Cloud Cost Management Workspace Operations view to enable selecting preferred currency options for cloud cost and usage data.\n\n\n- **[Granular instance operator role](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/cloud-insights-roles.md)**\n\nUse the instance operator role to perform routine operational tasks without requiring the full admin role for basic operations. By using limited privileges in the instance operator role, you can help reduce security risks across your organization.\n\n\n
\n\nCode Signing\n\n\n\n- **[Guardrail process optimization and scope increase](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/signature-verification-status.md)**\n\nAllows you to run the guardrail scan and identify records that have missing signatures, enabling you to proactively address records that are eligible for code signing but remain unsigned. Previously, the system only checked records with existing signatures and marked them as valid or invalid, which meant records without signatures were overlooked. Now, the process starts from the signature configuration itself, every eligible record is checked to see if it has a signature. If a record is missing a signature, it's clearly identified.\n\n\n
\n\nCollaborative Work Management\n\n\n\n- **[AI skills for Collaborative Work Management \\(CWM\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/now-assist-for-cwm-explore.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n- **[Task dependencies and relationships in CWM](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/managing-task-dependencies-relationships-cwm.md)**\n\nYou can now search by task number, in addition to name, when adding a relationship to a work item.\n\n\n- **[Inline comments changes in Docs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/cwm-docs.md)**\n - The Add comments icon appears in the inline toolbar.\n - Commented text displays a yellow highlight and underline. Selecting commented text darkens the highlight and opens a comment popover showing the full thread, including reply count, user avatars, names, and relative timestamps.\n - The comment popover provides options to edit or delete comments. Edited comments display an **Edited** indicator.\n - Users can turn highlights on or off using the **Show comment highlights** or **Hide comment highlights** options in the More actions menu of the document.\n\n- **[Formatting toolbar changes in Docs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/cwm-docs.md)**\n\nQuickly confirm which text formatting is active for your text selection. A green checkmark now appears next to the currently applied format in the formatting toolbar, giving you a clear visual indicator of the active formatting.\n\n- **[Sprint section footer changes in Sprint planning view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/agile-sprint-planning-in-cwm.md)**\n\nIn the sprint section footer of the Sprint planning view, unstarted sprints now display only the % of capacity utilized and remaining story points.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n
\n\nCommon Governance, Risk, and Compliance feature\n\n\n\n- **[ServiceNow Otto® name announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.The Now Assist for IRM \\(sn\\_irm\\_gen\\_ai\\) plugin, which provides generative AI capabilities for RCM, has been renamed to ServiceNow Otto for IRM.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[GRC notification redirection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/email-notification-redirection.md)**\n\nAfter upgrading GRC to version 22.3.6, notification links use dynamic routing rules to redirect you to the correct page, for workspaces where dynamic routing is configured.\n\n\n- **[Monitor my tasks in the Tasks page in the workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/configure-my-tasks-in-ws.md)**\n\nThe Task page now includes a timestamp showing when the task data was last refreshed. Additionally, a notification now displays when the page is refreshing data in the background.\n\n\n
\n\nCompliance Case Management\n\n\n\n- **[ServiceNow Otto® name announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.The Now Assist for IRM \\(sn\\_irm\\_gen\\_ai\\) plugin, which provides generative AI capabilities for Compliance Case Management, has been renamed to ServiceNow Otto for IRM.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n
\n\nConfigurable Workspace\n\n\n\n- **[Track record list changes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/use-ai-list-tracker.md)**\n\nGet an AI-generated summary of recent changes made to a list without manually reviewing each record.\n\n\n- **[AI filter assist](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/use-ai-filter-assist.md)**\n\nConvert everyday language into an encoded query with AI filter assist.\n\n\n- **Session tabs**\n\nThe following UI changes have been made to session tabs:\n\n - The icon to close a tab displays on hover only.\n - Overflow text on a tab is blurred instead of displaying an ellipsis.\n - Overflow tabs are displayed as a **More** tab with a split button.\n- **Lists for mobile devices**\n\nList design and behavior adapt to mobile devices to help improve usability.\n\n- **Forms**\n\nThe following UI changes have been made to forms:\n\n - Annotation fields provide rich text markup to enhance contextual form information.\n - The HTML editor toolbar displays a modern design.\n- **Form templates**\n\nThe following UI changes have been made to form templates:\n\n - The button to add a form template field has been updated to be more discoverable.\n - View selected conditions as a card below a field.\n- **Activity stream**\n\nThe following UI changes have been made to the Activity stream:\n\n - Filter Activity stream posts by user.\n - The Activity stream features a responsive design for stacking content, typography styles, and spacing.\n - System tokens for Activity stream components provide a consistent look and feel without needing to manually update style properties for every component.\n- **Email composer**\n\nThe following UI changes have been made to the email composer:\n\n - All email layouts display a minimized recipient field and borderless rich text editor.\n - A message displays in the header when an email is saved as a draft.\n - Copy and apply text formatting for emails using the format painter.\n\n- **Record List component bundle enhancements in UI Builder**\n\nConfigure these enhancements to the Record List component bundle in UI Builder:\n\n - Pin columns to keep them visible while scrolling horizontally.\n - Change the medium default size for highlighted values.\n - View list data as a data visualization.\n - Show a filter overview in the list header for a summary of the filters currently applied to the list.\n - Catalog variables and questions are supported as list columns.\n - Open lists in multiple session tabs from the list menu.\n - Customize gallery list card layouts including images, icons, text placement, and sizing.\n- **[Grouping for related lists](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure-related-list-grouping.md)**\n\nConfigure related lists to persist selections for the Group by filter.\n\n- **[Predicate Builder component enhancements in UI Builder](https://developer.servicenow.com/dev.do#!/reference/next-experience/australia/now-components/now-predicate-builder/uib-setup):**\n\nConfigure these enhancements to the Predicate Builder component in UI Builder:\n\n - Customize condition rows.\n - Configure a simple filtering mechanism.\n - Use a search term for filtering panel definitions.\n - Configure fixed queries.\n- **[Hierarchical queries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/data-hierarchies.md)**\n\nConfigure a record hierarchy to create filter queries that traverse levels of hierarchy.\n\n- **[Dynamic queries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/working-with-dynamic-schema.md)**\n\nConfigure dynamic attributes and dynamic categories to create filter queries that use the dynamic schema field type.\n\n- **[Form component enhancements in UI Builder](https://developer.servicenow.com/dev.do#!/reference/next-experience/australia/now-components/form%20record%20page/uib-setup):**\n\nConfigure these enhancements to the Form component in UI Builder:\n\n - Wrap field labels on mobile devices.\n - Display an indicator dot on unsaved fields.\n - Add a background color to unsaved fields to make them more noticeable.\n - Add an address field to forms that searches, validates, and automatically fills an address.\n- **[AI indicator](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_FormFields.md)**\n\nThe AI indicator is a visual cue that identifies form fields in configurable workspace and Core UI that have been updated with AI-generated content, providing a consistent and clear indication of AI involvement across the platform.\n\n- **[Unsaved field indicator](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure-unsaved-field-indicator.md)**\n\nConfigure the unsaved field indicator for your entire workspace experience instead of individual pages.\n\n- **[Background color for unsaved fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure-background-color-unsaved-indicator.md)**\n\nConfigure a background color to display on unsaved fields for your entire workspace experience instead of individual pages.\n\n- **[Background color for highlighted values](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure-background-color-highlighted-values.md)**\n\nConfigure a background color for fields with highlighted values.\n\n- **[Text commands for journal fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure-journal-fields-keyboard-shortcuts.md)**\n\nConfigure text commands that can be applied by keyboard shortcuts within journal fields.\n\n- **[HTML editor toolbar](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure.md-editor-toolbar.md)**\n\nConfigure toolbar options for the HTML editor within journal input fields.\n\n- **[Inline validation for string fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/format-regex-pattern-string-fields.md)**\n\nConfigure inline validation for string fields that formats inputs automatically, persists guidance text as a placeholder, and restricts unsupported characters.\n\n- **[Watch lists](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure-watch-list.md)**\n\nAdd and remove yourself and multiple records from a watch list.\n\n- **[Form Templates component enhancements in UI Builder](https://developer.servicenow.com/dev.do#!/reference/next-experience/australia/now-components/now-record-common-templates-connected/uib-setup)**\n\nConfigure these enhancements to the Form Templates component in UI Builder:\n\n - Preview form templates before applying them to the record page.\n - Display an alert message and confirm reuse when a selected form template is already applied to that record.\n- **[Activity Stream component enhancements in UI Builder](https://developer.servicenow.com/dev.do#!/reference/next-experience/australia/now-components/now-activity-stream-connected/uib-setup)**\n\nConfigure these enhancements to the Activity Stream component in UI Builder:\n\n - Edit and delete Activity stream posts after submitting.\n - Add knowledge base links from recommended actions to Activity stream posts.\n- **[Keyboard shortcuts for emails](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/add-response-templates-shortcut.md)**\n\nUse keyboard shortcuts to open drafts, email templates, and response templates.\n\n- **[Attachments component enhancements in UI Builder](https://developer.servicenow.com/dev.do#!/reference/next-experience/australia/now-components/now-record-common-attachments-connected/uib-setup)**\n\nConfigure these enhancements to the Attachments component in UI Builder:\n\n - Open the file viewer as a modeless dialog.\n - Customize the attachment header, upload instructions, and menu actions in both the full and compact modes.\n - Display the loading skeleton as a spinner or as three cards.\n - Enable a visible drop zone for file uploads in the compact mode.\n- **[Form action layout groups for declarative actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/configure-da-layout-group.md)**\n\nUpgrade form action layout groups to customize the order, label, and icons for declarative actions without altering the base action.\n\n- **[Declarative actions and UI actions on public pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/using-web-embeddables.md)**\n\nNon-logged in users may access specified declarative actions and UI actions on embedded web pages while maintaining integrity with security guidance and access control list permissions.\n\n\n
\n\nConfiguration Management Database \\(CMDB\\)\n\n\n\n- **Cleaner category grouping for Data Foundations advisor**\n\nThe CI class categories filter and the Set principal classes dialog box hide Data Model Navigator child categories that are already nested under a parent category, so the top-level list doesn't repeat categories.\n\n\n- **[Elevated user roles are no longer required for CMDB tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/manage-cmdb.md)**\n\nAccess to CMDB tables is no longer restricted to users with elevated privileges. Instead, for improved security, users with access privileges that are trimmed to CMDB features can complete any administrative or end-user CMDB task:\n\n - CMDB tables that required the admin or itil\\_admin roles are now also accessible to the sn\\_cmdb\\_admin user role.\n - CMDB tables that required the itil role are now also accessible to the sn\\_cmdb\\_editor user role.\n- **[Automatically generate de-duplication tasks for lookup and related tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/id-detect-dup-ci.md)**\n\nConfigure IRE to automatically generate de-duplication tasks for specific lookup or related tables during the identification process. You can then process those de-duplication tasks to remediate any duplications.\n\n- **[Remediate duplicate related items in lookup tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/id-detect-dup-ci.md)**\n\nConfigure IRE to create de-duplication tasks for duplicate related items in a lookup table, detected during a lookup-based identification. Sort which duplicates do or don't require remediation by configuring the system property **glide.identification\\_engine.lookup\\_match.create\\_duplicate\\_task\\_ci.enabled**. For more information, see [Detecting duplicate CIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/id-detect-dup-ci.md#section_unn_yjr_xgc).\n\n- **[Domain separation for key CMDB tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/c_DomainSeparationSetup.md)**\n\nThe following tables now support domain separation on instances which are configured with domain separation:\n\n - Key Value \\[cmdb\\_key\\_value\\]\n - Printer Instance \\[cmdb\\_print\\_queue\\_instance\\]\n - Software Instance \\[cmdb\\_software\\_instance\\]\n - Client Access \\[samp\\_client\\_access\\]\n - Oracle Options \\[samp\\_oracle\\_options\\]\nDomain separation can help protect sensitive information by supporting domain-specific data segregation.\n\nFor more information about domain separation and how to activate it, see [Domain separation setup and administration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/c_DomainSeparationSetup.md).\n\n- **[CMDB Query Builder engine execution modes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/query-builder-engine-execution-mode.md)**\n\nThe CMDB Query Builder expanded its support for various types of query structures that can run in V2 engine mode. Also, the performance of running queries in V2 mode is improved. Query structures that aren't supported include related list conditions, NOT operators combined with filters, certain Service Mapping relationships, and OR operators unless explicitly enabled by the **glide.cmdb.query.or\\_execution\\_mode** system property.\n\n\n
\n\nContinuous Authorization and Monitoring\n\n\n\n- **[Properties page enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/cam-components-installed.md)**\n\nThe Properties page includes new configuration options:\n\n - Use **Homepage Title** to customize the workspace homepage name.\n - The **Days Before Next Authorization** property is now available on the UI page.\n\n
\n\nContract Management Pro\n\n\n\n- **[Create a contract configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cncore-contract-config.md)**\n\nConfigurator-managed setups support the Renewal request type through a multi-select Request Type field, without requiring duplicate configuration entries. Both admin configuration and AI feature configuration extend to cover renewals.\n\n- **[Initiate an amendment from a contract record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cncore-amend-from-cntr.md)**\n\nInitiate an amendment from the contract workspace or from within a contract repository record.\n\n\n- **[Assign a signing order while adding a signatory](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cncore-update-sign-ss-cmr.md)**\n\nThe **Signatory order** field on the Add signatory form is editable. Assign a unique signing order to each signatory for sequential signing, or assign the same signing order to multiple signatories for parallel signing.\n\n- **[Modify the signing order on the Signatories related list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cncore-set-signing-order.md)**\n\nSet the signing order for a signatory by entering a number directly in the **Signatory order** column on the Signatories related list in Contract Workspace. The **Reorder** option is not available to modify the signing orders.\n\n- **[Signing order gaps and parallel grouping corrected automatically](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cncore-signature-workflow.md)**\n\nWhen you change a contract signing method from electronic signature to wet signature, signatories with the same signing order are assigned unique sequential signing order, and any gaps in the signing order are removed.\n\nWhen you select **Send for signature** or **Prepare for signature**, any gaps in the signing order are automatically removed.\n\n\n
\n\nCore Business Suite\n\n\n\n- **[Exploring employee support](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/core-business-suite/exploring-emp-home.md) [Exploring supplier support](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/core-business-suite/exploring-supplr-home.md)**\n\nProvide CBS admins with ia\\_admin and ia\\_user roles to give them broader permissions and control. The roles aren't available for the CBS admin by default.\n\n\n
\n\nCreator Studio\n\n\n\n- **[ServiceNow Otto rebrand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/creator-studio-text-to-form.md)**\n\nServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including Creator Studio. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n\n- **[Updated identifiers for AI-generated components](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/creator-studio-text-to-form.md)**\n\nAI gradient tokens are applied to specific components on the forms page to indicate when content has been generated or influenced by Now Assist. More easily identify AI-generated content consistently through the consistent and recognizable AI identity within Creator Studio.\n\n\n
\n\nCustomer Service Problem Management\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Diagnose and resolve a service problem case](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/telecom-media-technology/work-on-service-problem-case.md)**\n\nA refresh button is added to the Repair stage in the Service Problem Case.\n\n\n- **[Service Problem case record page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/telecom-media-technology/service-problem-case-record-page.md)**\n\nNew icons on the Service Problem case record for toggling between the playbook and record page views. Customer 360 tab is added to the Service Problem Case record page.\n\n\n
\n\nCustomer Success Management\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Touchpoint home page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/acct-lifecycle-events/account-lifecycle-touchpoint-home.md)**\n\nInternal touchpoints ensure that the internal teams are aligned on the objectives and outcomes of the engagement.\n\n\n
\n\nCustomer self-service for Sales Customer Relationship Management\n\n\n\n- **[Order exception support for quantity and shipping location requests](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/request-order-changes-now-assist.md)**\n\nEnable customers to request quantity changes and shipping location updates for existing orders, in addition to expedited delivery, through the chat assistant on the Business Portal.\n\n- **[Voice assistant intake for order exception requests](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/now-assist-order-mgmt-voice-aiagent.md)**\n\nEnable customers to submit expedite, quantity, and shipping location requests through the voice assistant. The voice assistant captures the request and creates an order case for the order case agent to resolve it in the CRM Workspace.\n\n- **[Scripted extension points for order exception checks and quote thresholds](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/create-atp-api-call.md)**\n\nProvide administrators pluggable scripted extension points so they can integrate the chat assistant with their inventory, ERP, and quote systems for delivery availability, quantity validation, shipping location validation, and quote threshold evaluation.\n\n- **[Consolidated extension point for order exception feasibility checks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/create-atp-api-call.md)**\n\nProvide a single scripted extension point \\(sn\\_ord\\_ops\\_aias.orderExceptionCheckEP\\) for the manage order operations chat assistant to validate delivery availability, quantity, and shipping location feasibility for order exception requests. This extension point replaces sn\\_ord\\_ops\\_aias.orderExpeditionCheckEP, which previously handled only available-to-promise \\(ATP\\) checks for expedited delivery.\n\n- **[Account and contact populated on interaction records for order exception chats](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/view-interactions-on-order-case.md)**\n\nProvide live agents with the customer's account and contact details on the interaction record when an order exception chat is handed off from the Business Portal. The Account and Contact fields are auto-populated on the interaction record during the virtual assistant conversation, so the live agent immediately sees the customer context, and the chat summarization feature can summarize the conversation by using those details.\n\n- **[AI-generated chat summary for live agent handoff](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/resolve-invoice-case-now-assist-agent.md)**\n\nProvide human agents with an AI-generated summary of the customer's prior virtual assistant conversation at the point of live agent handoff, replacing the full conversation history to accelerate context understanding and improve agent productivity.\n\n- **[Order line quantity validation for invoice disputes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/configure-invoice-quantity-check-ep.md)**\n\nProvide the invoice dispute support assistant AI with an additional validation source for quantity disputes by checking order line quantities when sold product records are unavailable, supporting scenarios such as new orders, non-serialized products, and consumable services. The assistant auto-approves eligible disputes and escalates to a human agent only when order data is ambiguous or missing.\n\n\n- **[Chat recommendations and quick actions in Active Chat](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/resolve-invoice-case-now-assist-agent.md)**\n\nEnable live agents to generate AI-recommended responses in Active Chat within the CSM/FSM Configurable Workspace, then review, optionally edit, and insert the response into the conversation. Agents can also use quick actions to perform common tasks such as creating cases, searching knowledge articles, summarizing chat conversations, and transferring chats directly from the Active Chat interface.\n\n\n
\n\nData Catalog\n\n\n\n- **Graph Explorer performance improvements**\n\nLineage views open faster by showing the nearest upstream and downstream connections first instead of waiting for the full diagram to load.\n\n- **ServiceNow collector lineage from Import Set Transform Map**\n\nThe ServiceNow collector harvests lineage edges based on the platform's native Import Set Transform Map framework.\n\n\n- **Data assets lineage improvements**\n\nTransform nodes now display transformations and processing steps in your lineage diagram with enhanced visualizations. Interact with transform nodes to view additional details about what data transformations occur at each step, helping you understand your data flow more clearly.Lineage graphs now load progressively by level, reducing the risk of timeouts when viewing large graphs. The system displays lineage in stages, allowing you to explore relationships without waiting for the entire graph to load, which improves overall responsiveness and performance.\n\n\n- **[ServiceNow metadata collector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/servicenow-metadata-collector.md)**\n\nControl how the collector harvests metadata. Enable an API size limit to cap the volume of data retrieved per request, exclude Glide artifacts from harvesting, and harvest Platform Analytics artifacts.\n\n\n
\n\nData Management for CSM\n\n\n\n- **Modify action limited to parent sold products**\n\nPerform the **Modify** action for only root sold products.The **Modify** action is inactive for child sold products across the list view, detail view, and hierarchical list.\n\n\n- **[Service Model Foundation renamed Entities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/renamed-entities.md)**\n\nRenamed Service Model Foundation entities to improve clarity and maintain consistency across the platform. Review your existing configurations, scripts, or integrations that reference these entities and update them accordingly.\n\n**Note:** The entity name changes are available in the Business Location 5.2.0 store app.\n\n\n- **[Household plugin migration to ServiceNow Store](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/activate-customer-service-household.md)**\n\nStarting with the Australia release, the Household family plugin \\(com.snc.household\\) has been migrated to the ServiceNow Store as a standalone application. Any new enhancements to this application are delivered through the Household store app. This change provides improved packaging, versioning, and deployment flexibility for B2C implementations that require household relationship management.\n\n\n- **[Enhanced Customer Data Viewer role](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/business-stakeholder-for-csm.md)**\n\nThe Customer Data Viewer \\(sn\\_customerservice.customer\\_data\\_viewer\\) role includes expanded access to additional data tables and menu items. These enhancements enable users to view a broader range of customer data while maintaining read-only access restrictions. With this enhancement, you can:\n\n - Extend access to additional tables for the customer data viewer role\n - Inherit household role in customer data viewer role\n - Explore additional menu items now accessible to the customer data viewer role.\n\n
\n\nData Privacy\n\n\n\n- **New experience**\n - [Optional condition filter](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/dps-create-anonymization-job.md) when running anonymization jobs to fine tune the scope of data to be anonymized.\n - [Specific anonymization policy](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/dps-create-anonymization-policies.md) for catalog variables to anonymize sensitive data in catalog requests.\n\n
\n\nData products\n\n\n\n- **[Edit a published data interface](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/edit-data-interface-wdf.md)**\n\nModify a published data interface to add columns, swap source tables, change the combination method, update column mappings, or adjust join conditions. Existing consumers continue to use the interface and must reconnect to pick up structural changes.\n\n\n
\n\nDevOps Change Velocity\n\n\n\n- **[Jira authentication with 3LO](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/connect-a-jira-tool-using-oauth-2-0-with-3lo.md)**\n\nAuthenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth \\(3LO\\) to enable secure, delegated access to your Jira account.\n\n- **[Bitbucket Cloud basic authentication using API token with scopes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/bitbucket-integration-dev-ops.md)**\n\nConnect to Bitbucket Cloud using Basic Auth by providing the email address and API token with the required scopes for your Bitbucket Cloud account as app password has been deprecated by Bitbucket.\n\n\n- **[Enhanced JFrog integration with DevOps Change Velocity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/devops-jfrog-connect-workspace.md)**\n\nGather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.\n\n- **[Bearer authentication in JFrog](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/devops-jfrog-connect-workspace.md)**\n\nConnect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.\n\n- **[HTTP proxy for Docker](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/servicenow-custom-actions-for-gitlab.md)**\n\nConnect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.\n\n- **[Health scan enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/run-health-scan-check.md)**\n - Identify any callback processing issues in your instance.\n - Identify any access control rule \\(ACL\\) that is incorrectly associated with a role in your instance.\n - Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys\\_\\* tables is present.\n - Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.\n- **[Auto close without Change Management - State Model \\[Legacy\\] plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dev-ops-change-acceleration.md)**\n\nChange requests can now be auto-closed without requiring you to install the Change Management - State Model \\[Legacy\\] plugin.\n\n\n
\n\nDeveloper Sandboxes\n\n\n\n- **[Upgrade enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/dev-sbx-clone-upgrade-info.md)**\n\nAutomatic backups for upgrades are now working correctly. This issue is related to PRB2017438.\n\n\n- **[Schema change for shared tables isolates the table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/dsb-installed-with.md)**\n\nTo ensure configuration consistency, if you make a schema change, such as adding a column, to a shared table, the table now becomes an isolated table on the sandbox that initiated the schema change.\n\n\n- **[Upgrade enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/dev-sbx-clone-upgrade-info.md)**\n\nAfter an upgrade, Developer Sandboxes now recreates the sandboxes on an instance and automatically backs up update sets to the base instance.\n\n- **[Queuing for successive sandbox creation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/allocating-sandboxes.md)**\n\nTo improve performance, Developer Sandboxes has implemented queuing when multiple sandboxes are created in succession.\n\n- **[SSO support for vanity URLs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/dev-sbx-general-guidelines.md)**\n\nInstances with vanity URLs can now support Single Sign-On \\(SSO\\).\n\n- **[New vibe coding documentation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/vibe-coding-landing.md)**\n\nDocumentation is now available that introduces vibe coding, which is a natural language approach to application development in ServiceNow, including how to get started, when to use it, and how it fits within the broader suite of AI-powered development tools.\n\n\n- **[Clarified sandbox initialization status](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/allocating-sandboxes.md)**\n\nAn error status message now appears on the instance home page when there’s an initialization error when allocating a sandbox.\n\n- **[Developer Sandboxes home page hidden when product is inactive](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/dev-sbx-entitlements.md)**\n\nThe Developer Sandboxes home page is unavailable when Developer Sandboxes is inactive on an instance.\n\n\n
\n\nDigital Product Release\n\n\n\n- **[Charts exclude cancelled phases from the release dashboards](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dpr-dashboard-release.md)**\n\nPolicies, phase tasks, and task approvals attached to a cancelled or restarted release phase are excluded from chart aggregates. They are also filtered out from the lists that opens on selecting a chart segment. This applies to the Digital Product Release landing page, Release Overview, Release Bundle Details, and the multi-product release dashboard.\n\n- **[Digital Product Release home page widgets scoped to your releases](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dpr-workspace.md)**\n\nThe **My releases** chart on the Digital Product Release Workspace home page shows only releases where you're the release owner or a release team member.\n\n- **[Release actions on all release pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dpr-manage-releases.md)**\n\nFrom any release page, perform actions such as **Start release**, **Re-target release**, **Close release**, **Complete current phase**, and **Run policies**.\n\n- **[Release template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dpr-create-release-template.md)**\n\nThe **Manage release template** button on the Release template form is renamed **Edit release template**.\n\n- **[Release creation wizard](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dpr-create-release-guided.md)**\n\nAdditional Products fields are no longer required in the Create release flow.\n\n- **[Policy status aggregation in a multi-product release](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dpr-policy-status-aggregation.md)**\n\nIn a multi-product release, the policy status of a product added after the release starts rolls up to the main release.\n\n- **[Product enhancement creation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/dpr-add-product-enhancement-from-epic.md)**\n\nThe **sn\\_dpr\\_workspace.enhancement\\_work\\_item\\_types** system property controls which work item types auto-create product enhancements. Leave it empty to stop enhancement creation.\n\n\n
\n\nDispute Content Pack for US Regulations\n\n\n\n- **[Enhanced SLA Definitions for Reg E and Reg Z](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/using-the-dispute-content-pack-for-us-regulation.md)**\n\nImprove regulatory adherence in your dispute workflow with the following enhancements to Reg E and Reg Z SLA definitions, ensuring timely dispute resolution and reducing regulatory risk exposure:\n\n - SLA tracking now anchors to the dispute report date instead of the case creation date.\n - SLA timelines for Reg Z are updated to require the financial institution to resolve the dispute within two complete billing cycles or 90 calendar days from the dispute report date.\n\n
\n\nDispute Rules Content Pack for Mastercard\n\n\n\n- **Updated Mastercard chargeback ineligibility rule for fraud**\n\nThe ineligibility condition for RC 4871 \\(Chip Liability Shift, Lost, Stolen, or Never Received Issue \\(NRI\\) Fraud\\) correctly evaluates the fraud-report timing window. A dispute is ineligible only when it is not raised within three days of the transaction being reported lost, stolen, or never received in the fraud and loss database. The condition also requires a fraud report ID to be present. The associated chargeback ineligibility reason text is updated to match the current wording in the Mastercard Chargeback Guide.\n\n\n- **[July Store Release: Build and update Mastercard chargeback ineligibility rules — Processing Errors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-mastercard-landing-page.md)**\n\nIneligibility rule conditions have been updated across the RC 4834 Processing Errors sub-categories to align with the latest Mastercard Chargeback Guide. Updated sub-categories include Transaction Amount Differs, Currency Errors, Cardholder Debited More than Once for the Same Goods or Services, ATM Funds Not Dispensed, Charges for Loss, Theft, or Damages, Merchant Refund Correcting Error Resulted in Cardholder Currency Exchange Loss, Improper Merchant Surcharge, Unreasonable Amount, and Cash was not properly provided from a Purchase with Cash Back transaction.\n\nFor Currency Errors: A new ineligibility condition has been added. CE is not applicable for ATM transactions \\(MCC 6011\\) where either the card was issued outside Europe or the terminal is located outside Europe.\n\nFor Transaction Amount Differs: The documentation requirements for this sub-category have been updated. For Maestro cards issued in Europe used at terminals outside Europe, no documentation is required. Brazil domestic disputes involving gratuity amounts now have explicit documentation requirements.\n\n- **[July Store Release: Build and update Mastercard chargeback ineligibility rules — Cardholder Disputes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-mastercard-landing-page.md)**\n\nIneligibility rule conditions have been added or updated across the following RC 4853 Cardholder Disputes sub-categories to align with the latest Mastercard Chargeback Guide:\n\n - Addendum Dispute\n - Cardholder Dispute of a Recurring Transaction\n - Counterfeit Goods\n - Digital Goods Purchase of USD/EUR 25 or Less\n - Goods or Services Not Provided\n - Goods or Services Were Either Not as Described or Defective\n - No-Show Hotel Charge\n - Refund Not Processed\n - Refund Posted as a Purchase\n - Timeshares\n - Transaction Did Not Complete\n - Travel/Entertainment Services Not Provided/Not as Described and Merchant Voucher Issued\nNew ineligibility rule conditions have also been added for the Cardholder Dispute-Not Elsewhere Classified-United States Domestic \\(RC 4854\\) sub-category.\n\n\n- **[Dispute Rules Content Pack for Mastercard chargeback eligibility rules updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-mastercard-landing-page.md)**\n\nDetermine the eligibility of a selected transaction for chargeback through chargeback eligibility rules transformed into technical formulas.\n\nFor May Store release, new ineligibility conditions have been added across all five existing RC 4808 Authorization sub-categories:\n\n - Required Authorization Not Obtained \\(RANO\\)\n - Expired Chargeback Protection Period \\(ECPP\\)\n - Stand-in or X-Code Approval after Issuer Decline \\(SIXCAID\\)\n - CAT 3 Devices \\(CAT3D\\)\n - Transit First Ride Risk Framework Claims \\(TFRR\\)\nFor May Store release, expanded eligibility rules for the following fraud dispute reason codes:\n\n - RC 4837 \\(No Cardholder Authorization\\)\n - RC 4849 \\(Questionable Merchant Activity\\)\n - RC 4870 \\(Chip Liability Shift\\)\n - RC 4871 \\(Chip Liability Shift – Lost/Stolen/Never Received Issue \\(NRI\\) Fraud\\)\n- **[Dispute Rules Content Pack for Mastercard intake questionnaire updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-mastercard-landing-page.md)**\n\nBenefit from the dispute questionnaire provided through Dispute Rules Content Pack for Mastercard with some modified questions and added hard stop alerts.\n\n\n
\n\nDispute Rules Content Pack for Visa\n\n\n\n- **Updated reason code 10.4 fraud and address verification eligibility conditions**\n\nRefined the invalid-dispute conditions for reason code 10.4 \\(Other Fraud – Card-Absent Environment\\), including new region-specific Address Verification Service \\(AVS\\) conditions phased in for Canada, US, and UK domestic transactions through October 23, 2026, then extended to Europe and select Latin America and Caribbean countries, and to Australia, New Zealand, and Singapore starting April 24, 2027. Added a Kazakhstan-specific condition for transactions initiated by reading a QR code, and a new condition \\(effective October 24, 2026\\) that evaluates device fingerprint, login ID, and delivery address matches across prior undisputed transactions.\n\n- **Updated reason code 11.3 authorization and clearing timeframe rules**\n\nRevised the No Authorization/Late Presentment conditions for ATM deposit and cash disbursement adjustments, removing outdated timeframe conditions and adding country-specific processing windows for India, Nepal, Japan, and Malaysia domestic transactions. Added new permitted-variance rules between authorization and clearing amounts for specific merchant category codes, including restaurants, cruise lines, lodging, and vehicle rental merchants, and for card-absent cardholder-initiated transactions. Added deferred-authorization timeframe conditions, including a Denmark-specific rule.\n\n- **Added reason code 13.3 price-discrepancy ineligibility condition**\n\nAdded a new condition marking reason code 13.3 \\(Not as Described or Defective Merchandise/Services\\) disputes ineligible when the dispute is based on a price discrepancy rather than a description or defect issue.\n\n- **Refined chargeback documentation messages**\n\nUpdated the required-documentation messages shown to dispute agents for reason codes 12.6 \\(Duplicate Processing/Paid by Other Means\\), 13.1 \\(Merchandise/Services Not Received\\), 13.2 \\(Cancelled Recurring Transaction\\), 13.5 \\(Misrepresentation\\), and 13.6 \\(Credit Not Processed\\) to align with the April 2026 Visa Chargeback Guide wording.\n\n\n- **[Updated chargeback eligibility rules for Visa reason codes 10.1, 10.2, 10.3, 10.4, 13.1, 13.2, 13.3, and 13.4](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-visa-landing-page-1.md)**\n\nThe chargeback eligibility rules for eight Visa reason codes have been updated to reflect Visa Chargeback Guide v1.1. The rules engine evaluates disputes automatically against the updated criteria; no manual configuration is required. Disputes that do not meet the updated eligibility criteria are flagged as ineligible before submission.\n\n- **[Updated dispute intake questionnaire for fraud disputes involving non-fiat currency and NFTs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-visa-landing-page-1.md)**\n\nThe fraud dispute intake questionnaire now includes a conditional question for disputes involving non-fiat currency or NFT transactions, such as cryptocurrency and digital token purchases. When the transaction is identified as a digital asset purchase, dispute agents and cardholders are asked to confirm whether the cardholder claims they were deceived into sending the asset to a fraudulent recipient. If confirmed, this claim supports accurate eligibility evaluation. The question is shown only when relevant and is cleared automatically when it does not apply. This supports accurate eligibility evaluation without requiring agents to manually identify digital asset transaction types.\n\n- **[Updated dispute intake questionnaire for RC 13.3 \\(Not as Described\\) disputes involving non-fiat currency and NFTs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-visa-landing-page-1.md)**\n\nThe consumer dispute intake questionnaire for RC 13.3 now includes an additional question for disputes involving non-fiat currency or NFT purchases. After confirming whether the asset received matched the description at the time of purchase, dispute agents and cardholders are asked whether there is evidence that the merchant guaranteed or promised the asset would increase in value. This question determines whether a specific dispute right applies, and appears only after the preceding NFT description question is answered.\n\n\n- **[Updated questions for the dispute questionnaire](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/exploring-the-dispute-rules-content-pack-for-visa.md)**\n\nAdded four new agent-facing questions to the dispute questionnaire under the authorization \\(11\\) and consumer disputes \\(13\\) categories. These questions map to the following reason codes:\n\n - 11.1 - Card recovery bulletin or exception file\n - 11.2 - Declined authorization\n - 11.3 - No authorization or late presentment\n - 13.6 - Credit not processed\n - 13.7 - Cancelled merchandise or services\n- **[Visa Resolve Online \\(VROL\\) version 26.1 updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-rules-content-pack-for-visa-landing-page-1.md)**\n\nUpdated the dispute questionnaire provided through the Dispute Rules Content Pack for Visa to align with Visa Resolve Online \\(VROL\\) release 26.1 revision changes.\n\n\n
\n\nDocument Services\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n- **[Document Viewer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/Documentviewer.md)**\n\nThe Next Experience Document Viewer is now available in the Classic UI \\(UI16\\) and Service Portals in addition to Workspace. ServiceNow Otto features including document summary, voice Q&A, smart redaction, and manual redaction are available.\n\n\n- **[Smart documents](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/configure-skill-smart-documents.md)**\n\nUse Smart Document skill across all tables.Existing configurations remain unchanged during upgrade, including those on specific tables or when the feature is disabled.\n\n\n
\n\nDomain Separation\n\n\n\n- **Dot-Walk Scoping Bypass Compliance \\(DIRS0000335\\)**\n\nDomain Separation has been updated to comply with the platform-wide dot-walk scoping bypass directive \\(DIRS0000335\\). Customers who have customizations involving dot-walk queries on domain-separated tables should review their configurations after upgrading.\n\n- **Java 21 Runtime Support**\n\nDomain Separation has been validated and updated to run on the Java 21 runtime introduced in the Australia release. Deprecated Java APIs have been removed from the Domain Separation codebase. No action is required for customers — this update is included automatically with the Australia upgrade.\n\n\n
\n\nEmployee Slate\n\n\n\n- **[Edit widgets inline](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/eslate-configure-browse-pages-inline-config.md)**\n\nInstance options to customize widgets on the home page and topic pages are no longer available. Customize your portal pages with the Admin editor.\n\n\n
\n\nEncryption\n\n\n\n- **[Field Encryption user interface changes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/now-platform-encryption.md)**\n\nThe new Field Encryption and Field Encryption Enterprise UI includes updates to key rotation and policies, access to encryption status and audit details, and changes to layouts.\n\n\n
\n\nEnterprise Architecture\n\n\n\n- **[Renamed Technology Portfolio Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-portfolio-management/eaw-tpm.md)**\n\nTechnology Portfolio Management \\(TPM\\) is renamed Technology Lifecycle Management \\(TLM\\) in the Enterprise Architecture Workspace.\n\n- **[Renamed Now Assist](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-portfolio-management/exploring-now-assist-for-ea.md)**\n\nServiceNow Otto for Enterprise Architecture \\(EA\\) is rebranded to ServiceNow Otto. User-facing text and icons across the Enterprise Modeling and Visualization tool are updated to reflect the new branding.\n\n\n- **[ServiceNow Otto for Enterprise Architecture \\(EA\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-portfolio-management/now-assist-ea.md)**\n - 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.\n - Changed the default LLM model for all ServiceNow Otto for Enterprise Architecture \\(EA\\) is to Azure OpenAI.\n\n- **[Enhancements to the My certifications section](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-portfolio-management/manage-requests-certs-assessments.md)**\n\nView only the certifications that are relevant to you in the **My certifications** tab on the Enterprise Architecture Workspace home page.\n\n\n- **[Granular admin role changes in Enterprise Architecture](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-portfolio-management/eaw-gran-admin-role-changes.md)**\n\nAdded the granular level admin role \\(sn\\_apm.apm\\_admin\\) to the following system properties in the Enterprise Architecture:\n\n - **sn\\_apm\\_trm.is\\_product\\_life\\_cycle\\_tech\\_debt\\_enabled**: Make this property false to disable calculating level 2 technical debt.\n - **glide.ui.sn\\_apm\\_trm\\_product\\_request\\_activity.fields**: TRM Product Request activity formatter fields.\n - **sn\\_apm\\_trm.noOfPublishersPerTRMPage**: The number of publishers to show per page.\n - **glide.ui.sn\\_apm\\_trm\\_product\\_lifecycle\\_request\\_activity.fields**: TRM Product Lifecycle Request activity formatter fields.\n - **sn\\_apm.noOfSoftwareModelsPerTPMPage**: The number of software models to show per page. This property is used for client-side pagination.\n - **sn\\_apm.discoveryModelProductTypesForTPMSuggestions**: Product types of discovery models to consider for TPM software suggestions.\n - **sn\\_apm.noOfSDLCComponentPerTPMPage**: The number of Agile Development components to show per page.\n - **glide.ui.cmdb\\_ci\\_business\\_app\\_activity.fields**: Business application activity formatter fields.\n - **sn\\_apm.startRangeOfTPMLifecycle**: The number of years before the current date is included when displaying software model lifecycle phases in the TLM timeline.\n - **sn\\_apm.endRangeOfTPMLifecycle**: The number of years beyond the current date is included when displaying software model lifecycle phases in the TLM timeline.\n - **noOfBusinessAppsPerTPMPage**: The number of business applications to show per page.\n\n
\n\nEnterprise Asset Management\n\n\n\n- **Product catalogs menu item**\n\nIn the navigation panel of the Admin center view, the **Product catalogs** menu item has been renamed to **Product catalog items**.\n\n\n- **[Now Assist to ServiceNow Otto® name change](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-products.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Work order plan reports in the Work management view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/work-management-overview-eam.md)**\n\nThe Work management view of the Enterprise Asset Workspace includes work order plan status and task reports.\n\n- **[Work order plan tabs in the Work management view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/work-management-overview-eam.md)**\n\nThe Work management view of the Enterprise Asset Workspace includes two new tabs:\n\n - Work order plans- View existing work order plans and create plans\n - Work order plan templates- Access available templates and create reusable templates\n- **[Affected assets tab in work orders and work order tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/work-management-overview-eam.md)**\n\nThe **Affected assets** tab provides a comprehensive view of all assets associated with a work order. When a work order includes an asset group, the tab lists every asset belonging to that group.\n\n\n- **[Multiple assets and asset groups in a work order](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/create-eam-work-order-task.md)**\n\nA work order and work order task can now be created for asset groups in addition to individual assets. Additionally, the sn\\_eam.enterprise\\_asset\\_manager role can add more assets to tasks while they're in the draft stage. When technicians start the task, they can take action on all included assets. The Deploy Asset, Swap Asset, and Remove Asset actions within work order tasks support multiple assets and asset groups.\n\n- **[Shutdown and Startup work types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/create-eam-work-order-task.md)**\n\nThe **Shutdown** and **Startup** work types available in the work order tasks enable you to manage asset shutdown and restart tasks.\n\n- **[Multiple calibration playbooks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/complete-eam-work-order.md)**\n\nWhen a calibration work order is created for multiple assets or an asset group, the system generates a separate calibration playbook for each asset in the Affected assets list.\n\n- **[Multiple condition lines](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/perform-condition-assessment-webui.md)**\n\nWhen an asset condition work order is created for multiple assets or an asset group, the system generates a separate condition line for each asset in the Affected assets list. All condition lines must be evaluated before the work order can be completed.\n\n\n
\n\nEvent Management\n\n\n\n- **Coral theme**\n\nThe Coral theme has been improved to enhance usability across web, mobile, and portal experiences that use Next Experience and Core UI:\n\n - A fully overhauled color system for smoother gradients and better contrast.\n - Softer outlines and more rounded components for a modern, accessible look.\n - A significantly improved dark mode with deeper blue tones for reduced eye strain.\n - New AI gradient styles and subtle animations to highlight intelligent features.\n - Smarter focus behavior that reduces visual clutter for mouse users.\n\n
\n\nExternal Content Connectors\n\n\n\n- **[Crawl schedules tab renamed](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/create-content-crawl-external-content-connector.md)**\n\nIn the external content connector editor, the **Crawl schedules** tab has been renamed to **Manage crawls**.\n\n\n- **[ServiceNow® instance external content connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/servicenow-instance-external-content-connector.md)**\n\nYou can now create and run multiple ServiceNow instance connectors on a single ServiceNow AI Platform instance.\n\n- **[Webcrawler external content connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/webcrawler-external-content-connector.md)**\n\nConnector admins can now schedule crawls on a daily, weekly, or monthly basis for all Webcrawler external content connectors.\n\n\n- **[Sitemap support in the Webcrawler external content connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/webcrawler-external-content-connector.md)**\n\nRetrieve content and links from URLs found in sitemaps defined for your web source system when running content crawls for the Webcrawler external content connector. A content crawl only retrieves sitemap URLs that include the crawl's starting point URL.\n\n- **[Start point links for scheduled partial content crawls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/create-content-crawl-external-content-connector.md)**\n\nView the start point for a scheduled partial content crawl via a link in its entry in the the external content connector's list of crawls.\n\n- **[Start point links in partial content crawl history entries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/review-crawl-ext-cont-connector.md)**\n\nView the start point for a scheduled partial content crawl via a link in its crawl history entries.\n\n- **[Limited Role-Based Access Control \\(RBAC\\) support in the Atlassian](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/atlassian-confluence-cloud-external-content-connector.md) Confluence Cloud external content connector**\n\nMap source system user and group permissions assigned via RBAC roles to users in your ServiceNow AI Platform instance.\n\n\n
\n\nFinancial Services Card Operations\n\n\n\n- **Price-discrepancy question for Visa consumer disputes**\n\nAn existing question, originally used under the Processing Errors dispute category, has been repurposed for consumer disputes filed under reason code 13.3 \\(Not as Described or Defective Merchandise/Services\\). Dispute agents are asked \"Is the dispute due to the difference between the quoted price and the actual charges made by the merchant?\" and cardholders are asked \"Is the dispute related to a discrepancy between the quoted price and the actual charges made by the merchant?\" A Yes answer marks the dispute ineligible for reason code 13.3, since a price discrepancy is not a valid basis for that reason code under the Visa Chargeback Guide.\n\n\n- **[Visa dispute management on the one-pager workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/work-on-a-dispute-case-integrated-with-visa.md)**\n\nAll Visa dispute tasks across the investigation, collaboration, and allocation stages are available in a single-page workspace, replacing the previous playbook-based experience. Dispute agents can view associated transactions from the Visa network directly on the task form and access the pre-arbitration questionnaire inline, with status tracking.\n\n- **[Updated dispute intake questionnaire for July Store release](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/installed-with-card-operations.md)**\n\nNew questions have been added to the dispute intake questionnaire to support updated Mastercard chargeback ineligibility rule assessment.\n\n - For Goods or Services Not Provided disputes \\(RC 4853\\): Dispute agents must select the applicable waiver and insurance status for merchandise delivery. Options are: a liability waiver was signed by the buyer; shipment insurance was declined by the buyer; both a liability waiver was signed and shipment insurance was declined; or neither applied. This question is mandatory for dispute agents and is also displayed to cardholders.\n - For Authorization disputes \\(RC 4808\\): Dispute agents must identify the current account status. Options include: account closed; suspended or restricted; fraud or compromise; credit-related issue; or account active and in good standing. This question is specific to Mastercard and is not displayed to cardholders.\nThe following additional changes have been made to existing questionnaire questions in this release:\n\n - The **What is the dispute about?** question choice list has been updated: the Multiple Authorization Requests option has been removed from the RC 4808 Authorization list, and Late Presentment has been removed from the RC 4834 Processing Errors list. The following labels have been updated: CAT 3 Devices \\(formerly Cardholder-Activated Terminal\\); Transit First Ride Risk \\(FRR\\) and Transit First Ride Issuer Liability \\(FRIL\\) claims; Installment Billing Dispute-Participating Countries; Cardholder Dispute-Not Elsewhere Classified-United States Domestic \\(new\\).\n - Display conditions have been updated for several existing RC 4853 Cardholder Disputes questions — including merchandise return date, date the cardholder first notified the issuer, and whether previous negotiation with the merchant occurred — to reflect the addition of the Cardholder Dispute-Not Elsewhere Classified- United States Domestic sub-category.\n - For Refund Not Processed disputes \\(RC 4853\\): The question asking for the date the cardholder first notified the issuer of the dispute is displayed when the credit voucher or transaction receipt is not dated. This question applies to dispute agents only.\n\n- **[Internal policy rule evaluation using dispute amount](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/dispute-decision-tables.md)**\n\nInternal policy rules in the **Card dispute rules for internal policy** decision table now evaluate using the dispute amount instead of the original transaction amount. Previously, if a cardholder or agent modified the disputed amount while answering additional transactional questions during intake, policy rules still evaluated against the original transaction value. Rules now use the dispute amount field \\(**sn\\_bom\\_credit\\_card\\_disputes\\_transaction.dispute\\_amount**\\), so any amount adjustments made during intake are correctly reflected in rule outcomes.\n\n\n- **[Updated chargeback eligibility questionnaire for May Store release](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/installed-with-card-operations.md)**\n\nNew Mastercard-specific questions have been added to the chargeback eligibility questionnaire.\n\nFor Authorization disputes \\(all RC 4808 sub-categories\\): A new mandatory certification statement appears in the dispute information section. It displays after the dispute amount modification reason field. Dispute agents must confirm that authorization was required for the transaction but was not properly obtained before an Authorization chargeback can proceed.\n\nFor Consumer Dispute RC 4853 Failed Travel Merchant: Two new questions support the bond or insurance scheme reimbursement requirement:\n\n - When a bond or insurance scheme exists, agents are asked what response was received from the bonding authority or insurance scheme when reimbursement was requested.\n - When no response has been received, agents are asked to provide the date on which the reimbursement request was submitted.\nQuestionnaire questions were updated including RC 4853 Failed Travel Merchant – Intra-EEA and Domestic European Transactions Only as an additional display condition.\n\n\n- **[Automated document submission in Mastercard transaction dispute process](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/chargeback-stage-mastercard.md)**\n\nStreamline the submission of supporting documents to Mastercard in the Mastercard Dispute Management workflow through document attachment and validation. Attached files are automatically checked against Mastercard requirements for file type and size. This update reduces the need for manual intervention, minimizes rework, and helps avoid rejection risk.\n\n- **[New subflow and action to support Card data security](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/card-data-security.md)**\n\nSupport attaching documents to a specified table record using the following subflow and action in Card data security:\n\n - Attach Document to Table Record\n - Attach Tokenized Document to Table Record\n\n
\n\nFinancial Services Operations Core\n\n\n\n- **[Case type selector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-case-type-select-modals.md)**\n\nFilter 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.\n\nTo configure agent criteria or customer conditions for the case type selector, use the following CSM tables:\n\n - `sn_csm_case_types_service_user_criteria`: for agent criteria\n - `sn_csm_case_types_service_customer_criteria`: for customer conditions\n\n
\n\nFinancial Services Operations Integration with Mastercard\n\n\n\n- **[Updated subflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/financial-services-operations-integration-with-mastercard-subflows.md)**\n\nThe following subflows were updated to support integration with the Card data security application:\n\n - Mastercom - Look up Case Documents\n - Mastercom - Look up Chargeback Documents\n\n
\n\nFinancial Services Operations Integration with Visa\n\n\n\n- **Updated questionnaire field labels and validation**\n\nRenamed the question \"Explain why credit presented does not apply\" to \"Provide the Transaction Identifier\\(s\\) or Acquirer Reference Number\\(s\\) and the Transaction Date that the credit\\(s\\) was applied to and why the credit\\(s\\) does not resolve the Dispute,\" and renamed \"Certification that the merchant facilities were withdrawn\" to \"Certification that the facilities were withdrawn.\" The **Name** field is no longer required, and **Key Factors** now accepts up to 200 characters.\n\n- **Updated Spoke action wiring for new questionnaire fields**\n\nAdded the **Date facilities were withdrawn** and **Date cardholder checked out from hotel** fields to the **Submit Dispute Questionnaire** and **Look up Dispute Details Response Parser** spoke actions, and added **CE Transaction Details** as a read-back field on **Look up Dispute Details Response Parser**. See [Financial Services Card Operations 2026 September Monthly release notes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/financial-services-card-operations-rn.md) for the corresponding questionnaire questions.\n\n- **Processing code field values updated for Visa compliance**\n\nThe `processing_code` field choice values in the Financial transaction table have been updated to align with current Visa data field specifications. Existing choice values have been updated with refined labels and descriptions; new choice values have been added to support additional transaction types.\n\nThe updated choice values include:\n\n - `00` — Goods/Service Purchase - Debit\n - `01` — Cash Disbursement \\(for example, withdrawal or cash advance\\) - Debit\n - `02` — Adjustment - Debit\n - `10` — Account Funding or Card Absent Account Funding\n - `11` — Quasi-Cash Transaction - Debit or Internet Gambling Transaction\n - `19` — Fee Collection - Debit\n - `20` — Return of Goods - Credit, Credit Transaction, Credit Voucher\n - `22` — Adjustment - Credit\n - `26` — Original Credit\n - `28` — Activation and Load / Load\n - `29` — Funds Disbursement - Credit\n - `30` — Available Funds Inquiry\n - `39` — Eligibility Inquiry\n - `50` — Bill Payment \\(U.S. only\\)\n - `53` — Payment \\(U.S. only\\)\n - `72` — Activation \\(POS\\)\nDispute agents and administrators see these updated labels and descriptions in transaction UI drop-down lists and data entry forms. Existing transactions require no action. Existing choice values not listed here remain unchanged.\n\n\n- **[Updated subflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/components-installed-with-the-financial-services-operations-integration-with-visa.md)**\n\nThe following subflows have been updated to support integration with the Card data security application:\n\n - Look up Associated Transactions\n - Look up Dispute Pre Arbitration Details\n - Look up Dispute Filing Details\n - Look up Dispute Response Details\n - Look up Dispute Pre Arbitration Response Details\n\n
\n\nGoal Framework\n\n\n\n- **[Changes to Goal and Target forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/goal-form.md)**\n\nThe **Cancelled** option has been added to the **State** field in both the [Goal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/goal-form.md) and [Target](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/target-form.md) forms, enabling you to set their status to **Cancelled** when needed.\n\n- **[Changes to Strategic Priority form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/strategic-priority-form.md)**\n\nThe **Status** field has been added to the Strategic Priority form, enabling you to set the status of a strategic priority as **None**, **Green**, **Yellow**, or **Red**.\n\n\n
\n\nGoal Framework for SPM\n\n\n\n- **[Changes to Target form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/target-form.md)**\n\nThe **Assigned entity type** and **Assigned entity** fields have been added to the Target form to support defining targets at multiple organizational levels.\n\n\n
\n\nHardware Asset Management\n\n\n\n- **[Now Assist > ServiceNow Otto announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/platform-now-assist-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Now LLM Service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Unified audit record storage](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/ham-inventory-audit.md)**\n\nStarting with Hardware Asset Management version 15.0.0, the audit inventory has been enhanced to store audit records in the common Asset Audits \\[sn\\_itam\\_common\\_asset\\_audit\\] table. If you have enabled the audit enhancements and switched to the common Asset Audits \\[sn\\_itam\\_common\\_asset\\_audit\\] table, the following user interface changes have been made:\n\n - The asset audit records are stored in the Asset Audits \\[sn\\_itam\\_common\\_asset\\_audit\\] table. After switching to the common audit table, deprecated audit records \\(created before the switch\\) are no longer visible in the **Asset audits** tab from the Inventory view. These records can be accessed from the Asset Operations view, when the **migrate\\_hamaudit**system property is set to **true**.\n - The Asset Audits \\[sn\\_itam\\_common\\_asset\\_audit\\] table can’t be accessed by navigating to **All** > **Asset Audits** > **Asset Audits**. You can access the legacy Asset Audits \\[sn\\_hamp\\_asset\\_audit\\] table instead.\n - If your ServiceNow® instance is licensed for both Hardware Asset Management and Enterprise Asset Management, the **Stockroom Details** tab displays a single Asset Audits tile. This unified Asset Audits tile shows the open audit records for both hardware and enterprise inventory, instead of displaying separate tiles for Hardware Asset Audits and Enterprise Asset Audits.\n\n**Note:** Note: If your ServiceNow instance isn't licensed for Enterprise Asset Management, the Hardware Asset Audits tile shows the number of open asset audit records for the hardware inventory audit.\n\n\n
\n\nITSM MCP Server\n\n\n\n- **[Changes to the ITSM MCP Server tools](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/itsm-mcp-server-tools-reference.md)**\n - You need the sn\\_mcp\\_server.viewer role as the base role to access ITSM MCP server.\n - The **sn\\_itsm\\_mcp\\_server.incident.get\\_details** and **sn\\_itsm\\_mcp\\_server.incident.modify** incident tools are available to both fulfillers and requesters.\n - As a fulfiller, you can use the **sn\\_itsm\\_mcp\\_server.incident.modify** tool to also escalate incidents.\n - As a requester, you can use the **sn\\_itsm\\_mcp\\_server.incident.get\\_details** to check the status of a specific incident.\n - The **sn\\_itsm\\_mcp\\_server.requester.add\\_comment** tool has been renamed to **sn\\_itsm\\_mcp\\_server.request.modify**.\n - As a requester, you can use the **sn\\_itsm\\_mcp\\_server.request.modify** tool to add customer-visible comments to the requested items.\n - As a fulfiller, you can use the **sn\\_itsm\\_mcp\\_server.incident.modify** to add customer-visible comments to incidents.\n\n
\n\nIdentity\n\n\n\n- **Role masking in Now Assist AI agents**\n\nUse role masking for AI agents and agentic workflows to limit the inherited roles during tool execution, verifying that AI agents run with restricted privileges, minimizing potential security risks and helping prevent unintended actions.\n\n- **[User management enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_CreateAUser.md)**\n\nUser management enhancements:\n\n - Configure AI agents or AI users by selecting the `AI` option from the Identity type drop-down menu.\n - Use the ai\\_user\\_admin role for creating, editing, and role management of AI users. Use this role to view, create, edit, assign roles to, and delete users with the identity type as `AI`.\n - Use the Identity sub-type field to categorize the identity type while creating a user.\n - Use the new date and time formats based on the user's preference while creating users.\n- **[Federated ID](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/federated-id.md)**\n\nUse Federated ID to uniquely identify roles across multiple instances. Federated ID provides a unique identifier for roles, making it easier to manage and track them across instances.\n\n- **[Machine Identity Console](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/machine-identity-console.md)**\n\nView the Inbound API Integration Usage dashboard under the Machine Identity Console's Unique API calls page to access statistics for requesters and their API calls.\n\n\n
\n\nImpact\n\n\n\n- **[Now Assist>ServiceNow Otto](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/impact/prevent-resolve-technical-debt-ai.md)**\n\nServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including Impact. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n\n- **[Optimization Accelerators](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/impact/optimization-accelerators.md)**\n\nOptimization accelerators catalog displays across dashboards, catalog filter and navigation, accelerator creation flows, and accelerator detail views inline with the other accelerator catalogs Flash cards now reflect the Optimization accelerator catalog category, and dashboards include platform optimization usage and consumption metrics.\n\n- ****\n\nOpen the Real-time Messaging panel directly alongside the development workspace; a slide-in side panel that stays visible until dismissed. Findings are organized into tabs by severity level, each showing a total count, and ordered by impact to the instance.Hover over the Level of Finding field in the findings table and definition records now displays a tooltip explaining Act, Recommend, Suggest, and Review.Select and open a filtered back-end list view for donut chart segments.\n\n- ****\n\nDashboard data refresh timing and status jobs trigger at the enhanced time frame and frequency for near real-time data. The dashboard also displays status messaging about job progress and any delays.\n\n\n- **[Run Impact Guided Setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/impact/guided-setup-impact-in-app.md)**\n\nThe Impact Guided Setup provides a more efficient, streamlined way for you to configure the Impact Store Application. For information about how to upgrade, see [Configuring Impact](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/impact/configuring-impact-platform.md).\n\n- **[Prevent and resolve technical debt with AI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/impact/prevent-resolve-technical-debt-ai.md)**\n\nReview enforcement messages for Update Set completion: Enforcement messages clarify which suite or scan type is required to meet completion criteria.Fix violations from JPMC issue analysis: Use new Scan Engine definitions that address real-world JPMC-identified violations.Deactivate base system Scan Engine definitions: Remove OOTB definitions from your instance without requiring an override.Sync exception reasons across instances: Synchronize exception reasons across multi-instance environments.Register your instance with streamlined guidance: Follow improved setup instructions for initial Scan Engine configuration.\n\n\n- **[Entitlements and usage](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/impact/capabilities-map.md)**\n\nRecommended capabilities has been renamed Squad-prioritized capabilities.\n\n\n
\n\nImport and Export\n\n\n\n- **The mssql-jdbc.7.4.1.jre8 jar file is no longer part of the MID Server distribution**\n\nIf you have a JDBC data source integration that uses this jar file \\(that is, any MSSQL connections\\) install this jar file or the vendor recommended jar file according to KB0862383.\n\n\n
\n\nIndustrial Process Manager\n\n\n\n- **[Additional fields in the OT Subnet Mapping table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/create-a-new-ot-subnet-mapping-record.md)**\n\nThe following fields were added for equipment model entity mapping:\n\n - Subnet\n - Managed Network\n - VLAN ID\n- **[OT Discovered Subnets table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/automate-mappings-between-ot-assets-and-equipment-model-entity.md)**\n\nThe OT Discovered Subnets table was added to the ServiceNow AI Platform and contains the discovered subnets in your OT network.\n\nTo access the table, navigate to **All** > **Industrial Workspace Admin** > **Industrial Process Manager** and select **OT Discovered Subnets**.\n\n- **[Discovered Subnet value added to the OT Subnet Mapping table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/create-a-new-ot-subnet-mapping-record.md)**\n\nA Discovered Subnet value was added to the **Type** field in the OT Subnet Mapping table on the ServiceNow AI Platform to identify which mappings were done with discovered subnets.\n\n- **[Updated OT device mapping to equipment model entities in the Industrial Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/map-ot-devices-in-iw.md)**\n\nYou can now map OT devices to multiple equipment model entities. When you navigate to the Equipment Model Manager and select the **Mapped OT Devices** tab in an equipment model record, you can select the **Map OT Device** button. In the Add OT Devices page, you can select the devices you want to map in both the **Unmapped OT Devices** tab and the **All Devices** tab. Then you can select the equipment model entities to map your devices to.\n\n- **[Location Validation Map tab](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/create-location-hierarchy-isa.md)**\n\nThe **Location Validation Map** tab was added to the Equipment Model Manager of the Industrial Workspace so you can view a node map that displays the location hierarchy and validation status of an equipment model entity.\n\n\n- **[Admin role dependency](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/granular-admin-roles.md)**\n\nSeveral new granular admin roles were added to enable developers to complete administrative configuration tasks without requiring the full admin role.\n\n\n
\n\nInstance Scan\n\n\n\n- **[Scan execution of inactive and base system checks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/hs-sys-properties.md)**\n\nYou can now execute scans on inactive checks by setting the glide.scan.inactive\\_records property to true. Add and enable glide.scan.base\\_system\\_records property to execute scans on base system checks.\n\n\n
\n\nInterview management\n\n\n\n- **[Schedule an interview](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/schedule-interview.md)**\n\nSchedule interviews more efficiently with auto-populated template variables that reduce manual email editing.\n\n- **[Manage interviews](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/manage-interviews-recruiter.md)**\n\nTrack applicants' responses to interview invites on interviews records directly.\n\n\n
\n\nKey Management\n\n\n\n- **[Updated workflow for creating cryptographic modules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/create-cryptographic-module.md)**\n\nUse the streamlined workflow designed for faster, easier creation of cryptographic modules.\n\n- **[SecurityUtils Enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/server-api-reference/GlideSecurityUtilsScopedAPI.md)**\n\nThe SecurityUtils API has been enhanced to help prevent cross-site scripting attacks, including methods to sanitize and escape input.\n\n\n
\n\nKnowledge Center\n\n\n\n- **[Auto-fix article optimization findings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/auto-update-articles.md)**\n\nAuto-fix applies to an AI-based **Image Alt Tag** scan based on the confidence score. Also, the AO auto publish enabled flag is renamed to Enable automatic updating and publishing of articles from AO findings.\n\n- **[Merge and publish potential duplicate articles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/automerge-duplicate-articles.md)**\n\nA new system property **Define the eligibility of time to revert the automatically merged or automatically updated articles** is available to configure the period within which you can revert a run. Also, the Enable auto merge publish flag is renamed to Enable automatic merging and publishing of duplicate articles.\n\n- **[Article health score](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/healthscore-metrics.md)**\n\nDuplicate score is added as a part of the Article health score and contributes to the overall health score of the article along with the Article optimization score. The article editor features a side panel with an Overview of: the Article health score, Article Optimization issues, Usage insights and Duplicate content alert.\n\n- **[Configure skills for potential gaps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/configure-na-km.md)**\n\nHR case data is included in knowledge gap analysis so that gaps related to HR cases appear in the Gaps area of Knowledge Center, alongside the existing IT incident and CSM case gaps. To use this feature, an admin must turn on the **Knowledge gaps identification \\(HR\\)** AI skill in AI Admin Hub.\n\n\n- **[Auto-fix article optimization findings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/auto-update-articles.md)**\n\nThe overview page shows automatic updates and manual review results for an automatically updated run, with progress indicators for bulk updates and reverts.\n\n- **[Merge and publish potential duplicate articles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/automerge-duplicate-articles.md)**\n\nMerge potential duplicate articles in a Knowledge Base where, the duplicate article drill-down widget groups them by topic and Knowledge Base.\n\n\n- **[Knowledge Center article editor](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/kc-article-editor.md)**\n\nThe article editor displays a word count indicator next to the editor size controls. Authors can see the total number of words in an article as they write, helping them stay within recommended limits.\n\n\n
\n\nKnowledge Graph\n\n\n\n- ****\n\nNew Query Builder section on Knowledge Graph Designer landing page. You can also directly access it from the main menu.\n\n\n- **[Create Knowledge Graph tag](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-knowledge-graph-tags.md)**\n\nThe new option to add AI instructions at node, property, and edge level when creating a tag, gives more business context to natural language queries.\n\n\n
\n\nLive Connect\n\n\n\nThe following UI changes are in this release.\n\n
\n\nLocalization Workspace\n\n\n\n- **[Cancel translation requests, delete draft requests, and review archived requests from the landing page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/lw-status-synchronization.md)**\n\nMonitor and control your requests on the landing page with functions to cancel translation requests, delete draft requests, and review archived requests.\n\n- **[View the translation method from the translation request summary](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/lw-status-synchronization.md)**\n\nView the translation method, such as TMS or machine translation, from the translation request summary. The summary is available from the My Requests list on the landing page.\n\n- **[Use intelligent due date suggestions based on the size and scope of your requests](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/lw-estimate.md)**\n\nUse intelligent due date suggestions, which provide an estimated completion date for your translations, based on the size and scope of your translation request. You can accept the suggested due date when submitting your request.\n\n\n
\n\nMID Server\n\n\n\n- **[MID Server security logs require 100MB of storage](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerSystemRequirements.md)**\n\nTo store the security logs, MID Servers must be installed on a host with at least 100MB of storage capacity.\n\n\n- **[MID Server supports PowerShell 7 for Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/powershell-remoting.md)**\n\nMID Server now supports PowerShell 7, while maintaining backward compatibility with PowerShell 5.1. This update enhances security, accelerates onboarding, and reduces deployment blockers through improved runtime detection and comprehensive test coverage.\n\n- **[Configure the MID Server for CyberArk CCP](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/t_ConfigureTheMIDServerForCyberArkCCP.md)**\n\nMID Server's CyberArk integration adds a REST-based CCP option alongside the existing AIM SDK method, providing flexible, interchangeable integration choices. This additional option can reduce dependency overhead and enables you to choose between the AIM SDK and REST-based approaches according to your requirements.\n\n- **[Smart Workload Manager in clusters](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_ConfigureAMIDServerCluster.md)**\n\nMID Servers in a cluster now assign jobs based on the true load, using a variety of criteria. The smart workload manager continuously evaluates the queue size, execution time, CPU usage, and buffer size. The manager then assigns tasks to ensure that no server is overloaded.\n\n- **[MID Server is bundled with Java Runtime Environment 21](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerSystemRequirements.md)**\n\nMID Server comes bundled with Java Runtime Environment version 21.0.7 and requires a minimum JRE version 17.0.10. The installer automatically configures Java 21.0.7 to run in your environment. If you have installed your own JRE, see the **Important information for upgrading MID Server to Australia** section to ensure your JRE is compatible.\n\n\n
\n\nManufacturing Commercial Operations\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n
\n\nMobile Platform\n\n\n\n- **[Mobile App Builder live component previews](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/mab-record-example-panel.md)**\n\nSupport was added for live component previews to the following:\n\n - Input form screens\n - Navigation tabs\n - Mobile app configurations\n - UI rules\n- **[Mobile App Builder auto-loading](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/mab-workspace.md)**\n\nAuto-load records and its downstream components when opening a record for the first time.\n\n- **[Product branding in Virtual Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/mobile-publishing.md)**\n\nAdd custom in-product branding to Virtual Agent.\n\n- **[Chat button in standard search results](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/now-assist-mobile-search.md)**\n\nLaunch Virtual Agent directly from your standard search results to chat with the Virtual Agent about the selected search result.\n\n- **Mobile Voice Agent background calling**\n\nContinue a Voice Agent call after backgrounding the mobile app on iOS and Android. Mute, unmute, or end the call from the home screen or lock screen without returning to the app.\n\n\n- **[Enhanced prelogin page customization](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/branded-landing-page.md)**\n\nConfigure the placement of the branded landing page login button to be either in the top menu header or as a part of the web page. Integrating the button into a web page helps you to implement a secure flow that addresses issues like short authentication session lifetimes.\n\n- **[Tone in Virtual Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/now-assist-mobile-va.md)**\n\nAdjust the Virtual Agent tone and response lengths in Assistant Designer.\n\n- **[Suggested actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/using-enhanced-chat-mobile.md)**\n\nConfigure suggested actions across all agentic workflows.\n\n- **[Input form screen buttons](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/servicenow-lens-mobile.md)**\n\nEnable up to two top action buttons on mobile device input forms that have the **Screen presentation** attribute.\n\n- **[Markdown support for tables in Virtual Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/now-assist-mobile-va.md)**\n\nRender tables in Virtual Agent with markdown support to keep table sizing consistent.\n\n- **[Turn off mobile impersonation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/mobile-impersonate-2.md)**\n\nConfigure the **impersonationEnabled** property to turn off mobile impersonation functionality. With this property, administrators can hide the impersonation option from the mobile app, regardless of assigned user roles.\n\n- ****\n\nThe following changes have been made:\n\n - Expanded the supported file types to include all of the following: PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, JPG, JPEG, PNG\n - Field service agents can now upload attachments in the background after submitting a work order task form, eliminating wait time caused by slow or unreliable network connections. Failed uploads retry automatically, so agents can move to their next task without interruption.\n- **[Redesigned Settings screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/manager-user-settings.md)**\n\nNavigate the redesigned Settings screen in the Now Mobile and Mobile Agent apps to manage entries like preferences, profile, and account switching in one place. Tap the arrow next to a heading to expand or collapse its related options.\n\nAdded to the Settings screen is the Experience area, where users can select between different mobile app experiences.\n\n- **[System default added to theme option](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/enable-dark-theme.md)**\n\nUse the new Theme option from the Settings menu called System default to automatically match the device's current theme setting. The other options in the theme menu are Light and Dark.\n\n\n
\n\nNext Experience\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Updated Coral theme](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/next-experience-theming.md)**\n\nThe Coral theme has been improved to enhance usability across web, mobile, and portal experiences that use Next Experience and Core UI:\n\n - A fully overhauled color system for smoother gradients and better contrast.\n - Softer outlines and more rounded components for a modern, accessible look.\n - A significantly improved dark mode with deeper blue tones for reduced eye strain.\n - New AI gradient styles and subtle animations to highlight intelligent features.\n - Smarter focus behavior that reduces visual clutter for mouse users.\n- **New Works with ServiceNow badge added to user menu**\n\nThe Works with ServiceNow badge now appears in the user menu for custom-branded accounts. This applies to web and mobile experiences with Next Experience or Core UI enabled. All other branding and theme settings remain unchanged. This update applies automatically.\n\n\n
\n\nNext Experience Components\n\n\n\n\n
\n\nComponent\n\n\n\nEnhancement\n\n
\n\nActivity Stream\n\n\n\n- Enable users to edit or delete journal posts.\n- Add a dropdown with check boxes for author names using the Posted by filter that enables users to filter posts by author, select all, or clear all. Users can also filter for any AI-generated posts.\n\n
\n\nAlert\n\n\n\n- Enable keyboard focus to move to the alert when it appears.\n- Add AI variants with updated color palettes for generative AI workflows.\n\n
\n\nAlert list\n\n\n\nEnable keyboard focus to move to the **Show alerts** button when the alert list appears.\n\n
\n\nButton\n\n\n\nAdd AI variants with updated color palettes for generative AI workflows.\n\n
\n\nButton iconic\n\n\n\nAdd AI variants with updated color palettes for generative AI workflows.\n\n
\n\nButton circular\n\n\n\nAdd AI variants with updated color palettes for generative AI workflows.\n\n
\n\nCalendar\n\n\n\n- Hide time zone dropdown in the calendar header.\n- Hide time lapsed indicator or time zone indicators.\n- Add section-based time zones.\n\n
\n\nCard base container\n\n\n\nAdd AI variants with updated color palettes for generative AI workflows.\n\n
\n\nChecklist\n\n\n\n- Edit or delete items on hover.\n- Edit checklist items inline.\n- Edit, delete, and reorder checklist items.\n- Configure empty state checklists to add new items.\n\n
\n\nDropdown\n\n\n\nAdd AI variants with updated color palettes for generative AI workflows.\n\n
\n\nDropdown list\n\n\n\nThe mobile version uses the sheet component instead of a popover.\n\n
\n\nForm\n\n\n\n- Place each form field label in line with the input field and adjacent to other field labels using the “Tabbed” \\(horizontal\\) layout.\n- Highlight form fields with unsaved changes using a background color, in addition to the existing field indicator, which is now selected by default.\n\n
\n\nForm Templates\n\n\n\n- Show that the preview option displays modal preview to help agents understand all the fields affected when they apply a particular template.\n- Alert to inform users if a template has already been applied to a record.\n\n
\n\nHighlighted value\n\n\n\n- Enter additional text to display in a popover when the highlighted value is selected.\n- Add AI variants with updated color palettes for generative AI workflows.\n\n
\n\nIcon\n\n\n\nSupport for theme-specific custom icon uploads.\n\n
\n\nInput\n\n\n\nDisplay persistent placeholder text to guide users in entering data in the correct format.\n\n
\n\nKanban\n\n\n\nUse keyboard shortcuts to drag and drop cards between columns and rows.\n\n
\n\nList selector\n\n\n\nDisable the selection feature for a chosen array of list selector items.\n\n
\n\nNode map\n\n\n\n- Use radial layout to arrange nodes in a ring-like pattern.\n- Use content slots to add components.\n- Disable node dragging.\n\n
\n\nSchedule recurrence\n\n\n\n- Automatically update all recurring events in a series.\n- Fill in event details using AI.\n\n
\n\nSplit button\n\n\n\nAdd AI variants with updated color palettes for generative AI workflows.\n\n
\n\nTabs\n\n\n\nHide padding on the sides of each tab for horizontal \\(Top\\) tab position, to provide more room for additional tabs.\n\n
\n
\n\nChart\n\n\n\nEnhancement\n\n
\n\nBar \\(including Pareto\\)\n\n\n\n- Show or hide a tooltip that displays on hover showing the percentage of total for a data point.\n- Removed the display setting for Height, which can be configured in the **UI Builder Styles** tab.\n- Align title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
\n\nBox plot\n\n\n\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n\n
\n\nBubble\n\n\n\n- Show or hide a tooltip that displays on hover showing the percentage of total for a data point.\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n\n
\n\nDial\n\n\n\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
\n\nGauge\n\n\n\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
\n\nGeomap\n\n\n\n- Show or hide a tooltip that displays on hover showing the percentage of total for a data point.\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n\n
\n\nHeatmap\n\n\n\n- Show or hide a tooltip that displays on hover showing the percentage of total for a data point.\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
\n\nIndicator Scorecard\n\n\n\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n\n
\n\nPie/Donut\n\n\n\n- Show or hide a tooltip that displays on hover showing the percentage of total for a data point.\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
\n\nPivot table\n\n\n\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
\n\nSingle score\n\n\n\n- Align the title horizontally to the Start, Center, or End. The default is Start.\n- Wrap chart elements instead of truncating.\n- Align the title horizontally to the **Start**, **Center**, or **End**. Default is **Start**.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
\n\nTime series\n\n\n\n- Removed the display setting for Height, which can be configured in the **UI Builder Styles** tab.\n- Show or hide a tooltip that displays on hover showing the percentage of total for a data point.\n- Align the title horizontally to the **Start**, **Center**, or **End**. The default is **Start**.\n- Align all chart content to the starting edge, center, or ending edge of the visualization.\n- Set the line of truncation to 2 or 3 lines instead of truncating long titles after 1 line.\n- Wrap long titles to a second line, instead of truncating.\n- Hide the refresh action that is available to users in the More options menu.\n- Show incomplete periods for a data snapshot indicator when selecting Metric.\n- Enable Auto aggregation to have the most appropriate aggregation level determined based on the selected date range, applied date filters, or data availability.\n\n
|App shell|Enhancement|\n|---------|-----------|\n|Agent Workspace app shell|Configure alt text for a ServiceNow or customer logo button.|\n\n
\n\nNext Experience Developer \\(NED\\) Tools\n\n\n\n- **Service Workers tab in the Next Experience Inspector**\n\nThe Service Workers tab displays an updated homepage.\n\n\n- **Events tab in the Next Experience Inspector**\n\nExclude filters in the Events tab to filter out specific events.\n\n- **Components tab in the Next Experience Inspector**\n\nUse the journal section in the Components tab to get a log of state updates, property updates, actions dispatched, and actions handled.\n\n\n
\n\nNotifications\n\n\n\n- **[Create and associate actions for intent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/create-actions-for-intent.md)**\n\nAdded the Email Template field to the Reply Email Notification Intent Action type.\n\n\n- **[Now LLM support and email template configuration in Notification Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/notification-creation-agent.md)**\n\nNow LLM and third-party LLM models are now supported, and email templates can be configured for notifications created using the Notification Agent.\n\n- **[Email templates for the Email Generator Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/create-actions-for-intent.md)**\n\nUse branded email templates in the Email Generator Agent, allowing AI-generated responses with customer-specific layouts, logos, and styling.\n\n- **[Multiple intent identification in inbound emails](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/email-agentic-workflow.md)**\n\nMultiple intents can now be identified in inbound emails, allowing multiple reply email actions for a single email.\n\n- **[Handle missing inputs for inbound email actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/email-agentic-workflow.md)**\n\nMissing inputs for inbound email actions are now handled through configurable execution modes, allowing missing inputs to be requested, intents to be skipped, or processing to continue.\n\n\n- **[Create an email client template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_CreateAnEmailClientTemplate.md)**\n\nAdded a check box for the email client template.\n\n- **[Configure templates for personal corporate mailboxes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/configure-personal-corporate-mailbox.md)**\n\nAdded a new **From Generation Type** for the User Email Addresses for email client templates.\n\n- **[Integrate personal corporate mailbox for receiving emails](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/integrate-corporate-email-receiving.md)**\n\nAdded the Forwarding Address option for the email account type.\n\n\n- **[Sending email using Microsoft Graph](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/send-email-using-ms-graph.md)**\n\nConnect Microsoft email accounts using Microsoft Graph within the ServiceNow instance for sending outbound emails.\n\n- **[Email threading for inbound reply email](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_InboundEmailActions.md)**\n\nEnable classification of inbound emails by using the thread-index header for emails originating from Microsoft or Microsoft Outlook ecosystem.\n\n- **[Column Level Encryption for email attachments](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/cle-for-email-attachments.md)**\n\nAttachments from inbound emails are now encrypted when stored in CLE-enabled tables and decrypted when sent in outbound emails, ensuring secure access without requiring scripting.\n\n- **[Enable push notifications for logged-out users](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/enable-notifications-logged-out-users.md)**\n\nPush notifications can now be configured to be sent to users even when they are logged out, ensuring critical updates are not missed.\n\n\n
\n\nNow Assist in Document Intelligence\n\n\n\n- **[Updated banner in the extraction review panel](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/document-intelligence-workspace-with-now-assist.md)**\n\nChanged the label in the extraction review panel banner from Document Q&A to Extracted data.\n\n\n- **[Now Assist in Document Intelligence skills are now turned on by default](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-assist-skills-on-by-default.md)**\n\nThe new default behavior works as follows:\n\n - New customers: When you install a Now Assist product, designated skills are turned on automatically.\n - Existing customers who are upgrading: Any previously unconfigured skill is turned on automatically \\(the skill was never configured and turned on, then turned off again\\). Previously configured skills that were turned on, then off, remain inactive.\n\n- **[Document and visual insights AI agent enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/document-and-visual-insights-ai-agent.md)**\n\nTools used by the document and visual insights AI agent are consolidated to improve performance.\n\n- **[Changes to limitations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-assist-document-intelligence-limitations.md)**\n\nThe file size limit for uploading a file using the attachment summarization feature is changed from 10MB to 20MB.\n\n- **[Add a tool](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/add-a-tool.md)**\n\nDocument and visual intelligence capabilities used to leverage extraction, question answering, and summarization for skills created with AI Skill Kit is available to users with the appropriate role\\(s\\).\n\n\n
\n\nOperational Resilience\n\n\n\n- **[Create reporting configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/create-reporting-configurations.md)**\n\nThe Reporting Configurations module is provided in the Digital resilience incident reporting application to drive incident report generation.\n\n- **[Advanced scenario analysis](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/scenario-analysis-playbook-experience.md)**\n\nThe **Playbook** tab is provided in the Scenario analysis records.The **Statistical Modelling** and **Manual** options are available in the **Method** field on the **Details** tab.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n- **[Export action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/work-on-action-tasks.md)**\n\nThe **Export** UI action on the action task form displays the following options: **Generate MS Word**, **Export Excel**, and **Export JSON**.\n\n- **[Excel download/upload request form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/create-excel-report-aggregate-expenses.md)**\n\nAfter upgrading the Digital Resilience Third-party Information Register application to version 22.0.x, the Excel download/upload request form includes the following fields for converting and aggregating contractual expenses to currencies required by regulators:\n\n - **Report type**\n - **Enable currency conversion**\n - **Base currency**\n - **Enable third-party total expense aggregation**\n - **Reference date**\n - **Date of the reporting**\nThe **Type** field includes the **Plain-csv reporting package** option for generating reports in Comma-Separated Values \\(CSV\\) format.A business rule checks eight composite key fields when saving a contractual arrangement and displays a warning if a duplicate is found. B.05\\_02 includes a link to open the duplicate record directly for comparison. B.05\\_01 correctly includes ICT Intra-Group Service Provider \\(Legal Entity providers\\) in the ICT Third-Party Service Provider report.A warning is displayed when a Legal Entity Identifier \\(LEI\\) fails validation or a mismatch is detected against the GLEIF API across all four record form types.\n\n- **[Template versions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/set-up-sae-templates.md)**\n\nNew assessments display the latest published Smart Assessment template version.\n\n\n
\n\nOperational Sustainability Management \\(formerly Environmental, Social, and Governance\\)\n\n\n\n- **[ServiceNow Otto® name announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.The Now Assist for IRM \\(sn\\_irm\\_gen\\_ai\\) plugin, which provides generative AI capabilities for RCM, has been renamed to ServiceNow Otto for IRM.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n- **[Campaigns](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/environmental-social-governance/campaigns.md)**\n\nThe Campaigns list and record views were added to the Operational Sustainability Workspace. Related lists for entities, metrics, campaign tasks, owners, and approvers are included, along with declarative Add/Remove actions for managing campaign entities and metrics.\n\n\n- **[Metric definition setting record fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/environmental-social-governance/metric-definition-setting-record-fields.md)**\n\nAfter upgrading GRC: Metrics to version 22.5.2, Metric definitions now support a configurable variance base value, resolved from the individual metric, its metric definition, or a global default. Variance percentages remain meaningful when a previous-period value is missing or zero.\n\n\n
\n\nOperational Technology Discovery\n\n\n\n- **[Edit an Appliance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/edit-an-appliance.md)**\n\nNavigate to the Appliances page where the individual Sensors and Collectors with their status and location are displayed. The page displays the component type, its endpoint, and CPU usage. Select the appliance name to see its details and additional settings.\n\n- **[Filter results for Host Status](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/results-filter-host-status.md)**\n\nIn the Scan Results filtering types, the **Host Status** helps you view query results based on whether the queried host was **Up** or **Down**. This filter is derived from the Nmap XML status field inside the Raw scan output.\n\n\n- **[Requirements for Discovery Console for OT installation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/reqs-ot-console-installation.md)**\n\nThe required dependency version changed from .NET 8 to .NET 10.\n\n\n
\n\nOperational Technology Incident Management\n\n\n\n- **[Now Assist for OTSM to ServiceNow Otto for OT Service Management name change](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/now-assist-for-operational-technology-service-management.md)**\n\nServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including Now Assist for OTSM. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n\n- **[Summarize UI action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/summarize-ot-incident-now-assist.md)**\n\nThe **Summarize** UI action was added to OT incident records in the Industrial Workspace so you can automatically summarize the incident details.\n\n- **[Generate resolution notes UI action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/generate-resolution-notes-ot-incident.md)**\n\nThe **Generate resolution notes** UI action was added to OT incident records in the Industrial Workspace so you can generate resolution notes after the incident state is set to **Resolved**.\n\n**Note:** This UI action appears after the OT incident state is set to **Resolved**.\n\n- **[Catalog item for reporting an OT incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/report-ot-incident-in-ot-employee-portal.md)**\n\nThe Report OT incident item has been added to the OT Service Catalog for use in the Employee Center for OT.\n\n\n- **[Admin role dependency](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/granular-admin-roles.md)**\n\nSeveral new granular admin roles have been added, which enable developers to complete administrative configuration tasks without requiring the full admin role.\n\n\n
\n\nOperational Technology Manager\n\n\n\n- **[Now Assist for OTM was renamed to OT Manager Foundation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/now-assist-for-otm-landing.md)**\n\nNow Assist for Operational Technology Manager \\(OTM\\) was renamed to Operational Technology \\(OT\\) Manager Foundation.\n\n\n- **[Now Assist for OTM was renamed to OT Manager Foundation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/now-assist-for-otm-landing.md)**\n\nNow Assist for Operational Technology Manager \\(OTM\\) was renamed to Operational Technology \\(OT\\) Manager Foundation.\n\n\n- **[Automated IT OT Bulk Conversion name change](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/automatically-convert-it-records-to-ot-devices.md)**\n\nThe Automated IT OT Bulk Conversion menu item was replaced with Automated IT OT Bulk Contextualization on the ServiceNow AI Platform.\n\n- **[Banner messages for the Bulk Update Ruleset for Reassigning IT to OT feature](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/automatically-convert-it-records-to-ot-devices.md)**\n\nA banner message was modified during the Bulk Update Ruleset for Reassigning IT to OT feature process to reflect the correct information when you use this feature.\n\n- **[IP Network Subnets related list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/ot-assets-related-links-and-lists.md)**\n\nThe IP Network Subnets list was added for OT devices so you can see all subnets the selected OT device is associated with.\n\n- **[VLAN related list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/ot-assets-related-links-and-lists.md)**\n\nThe VLAN related list was added to the OT device form view to show the VLANs associated with a device.\n\n\n- **[Use CMDB groups to add OT context to IT CIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/use-cmdb-groups-it-ot-conversion.md)**\n\nWhen you use CMDB groups to add OT context to IT CIs, you can no longer create an Automated IT OT Bulk Contextualization record with more than one CMDB group.\n\n- **[Automated IT OT Bulk Contextualization - Using CMDB groups scheduled job](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/use-cmdb-groups-it-ot-conversion.md)**\n\nThe **Automated IT OT Bulk Contextualization - Using CMDB groups** scheduled job can only process 10,000 CIs at one time. If you have more than 10,000 CIs, the remaining CIs will be processed in the next job run.\n\n- **[Admin role dependency](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/granular-admin-roles.md)**\n\nSeveral new granular admin roles were added to enable developers to complete administrative configuration tasks without requiring the full admin role.\n\n\n
\n\nOrder Management\n\n\n\n- **[Managing inflight order for site projects](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/inflight-offering-somt.md)**\n\nUse the OM integration with SPM for in-flight orders to support projects for site and maintain program project and sub-project hierarchy.\n\n\n
\n\nPerformance Analytics\n\n\n\n- **[Data snapshots automatically installed on eligible instances](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/limitations-mlb.md)**\n\nIf you have Australia Patch 3 or later, the Data snapshots plugin is installed automatically if you have RaptorDB Professional. If your instance is also domain separated, the Data snapshots feature is installed but disabled.\n\n\n- **[Explore native data snapshots indicators with KPI Details](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/kpi-details-targets.md)**\n\nKPI Details supports data snapshots indicators that you create, not only those that are enabled from classic indicators. The following features have been created for or extended to native data snapshots indicators:\n\n - Subscriptions for alerts on targets and thresholds, which can be set from the targets and thresholds panels\n - Adjustable filtering by breakdown, calendar, or time series aggregation\n - Hierarchical breakdowns, with scores rolled up to parent elements\n - Customizable score formatting options, such as precision and abbreviation\n- **[View data trends in data snapshots as data accumulates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-ds-automated-indicator.md)**\n\nWhen you select a field by which to trend a data snapshots automated indicator, you have the option to show the trend for incomplete collection periods. This feature shows the trend as it develops for live data without having to wait for the end of the collection period. You can set this behavior either on the automated data snapshot indicator record or in a time series data visualization for a data snapshot indicator.\n\n- **[Collect data snapshots scores with confidence](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/tables-unlimited-breakdowns.md)**\n\nData mining for data snapshots scores has the following improvements:\n\n - Collect scores for tables with any volume of records.\n - The system accurately and automatically handles data gaps when data mining is turned off.\n - You are warned of the implications before you manually disable data mining \\(score collection\\).\n- **[Activate data snapshots in more cases and with better information](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/activate-unlimited-breakdowns.md)**\n - Activate indicators without active data collector jobs.\n - Activate indicators regardless of underlying record volume. For example, the `INSERT_VOLUME_EXCEEDED` error no longer occurs.\n - If the activation fails because of scripted breakdowns, the scripted breakdowns are listed in the failure message.\n - Generic parsing errors have been rewritten into specific, categorized messages.\n\n
\n\nPerformance Analyzer\n\n\n\n- **Deep linking**\n\nSave and share links that replicate the same view for others.\n\n- **Group by variant**\n\nAggregate pages with data grouped by variant help you to identify performance issues.\n\n- **Filter client interaction lists**\n\nFilters for client interaction lists enable you to investigate user-specific performance issues.\n\n- **Waterfall view**\n\nThe waterfall view displays which macroponent is associated with server-side calls to help you trace API calls to specific UI components.\n\n\n
\n\nPlatform Analytics experience\n\n\n\n- **[Use simplified navigation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/using-the-next-experience-global-header.md)**\n\nWhen you are moved to Next Experience navigation:\n\n - The Analytics Overview page and all library pages now contain their own Platform Analytics navigation tree.\n - The navigation path **Self-Service** > **Dashboards** redirects to **Platform Analytics** > **Library** > **Dashboards**.\n - The navigation path **Reports** > **View / Run** redirects to **Platform Analytics** > **Library** > **Data Visualizations**.\n- **[Sort library records by column values](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/find-dashboard-library.md)**\n\nSelect the header of any column in a library page to sort the library by that column.\n\n- **[New settings in Single Score data visualizations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-dv-sing-sc-ac.md)**\n\nConfigure new color settings for Single Score data visualizations. You can also change the relative position of both the score and the title header.\n\n\n- **[Manage Platform Analytics in the improved Analytics Overview page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/analytics-center.md)**\n\nQuickly discover artifacts, access relevant information and key metrics, and take actions to manage the health of the library. The Analytics Overview page \\(formerly Analytics Center\\) acts as a one-stop shop and entry point for role-specific access to all important information related to Platform Analytics.\n\n- **[Platform Analytics experience is enabled by default for all users on upgrade to Australia](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/par-workspace.md)**\n\nCreate content entirely within Platform Analytics.\n\n- **[Take role-based tours](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/guided-tours.md)**\n\nRole-based guided tours are added to the Platform Analytics Migration Center and the Dashboards and Data Visualizations library pages.\n\n- **[Filter dashboards by string field values](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-select-filter-workspace.md)**\n\nFilter data by the contents of string-type fields with a single-select or multiple-select filter.\n\n- **[View the percentage each data segment contributes to the total](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-dv-donut-ac.md)**\n\nEnable the **Show % of total in tooltip** option to show the percentage each data point contributes to the total alongside absolute values in the tooltip. Applies to time series, bar, bubble, donut, geomap, and heatmap visualizations.\n\n- **Publish report functionality replaced with Read-only link option in Report Designer**\n\nIt is no longer possible to publish a report. The **Read-only** option provides a URL that authenticated users can follow to view a report.\n\n- **[Explore native data snapshots indicators in KPI Details](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/kpi-details.md)**\n - Employ intraday analysis with granularity based on work shifts.\n - Customize score formatting options.\n - Adjust breakdowns, calendar, and aggregation periods while exploring an indicator.\n - Set up subscriptions for alerts on targets and thresholds directly from the targets and thresholds panels.\n - Define hierarchical breakdowns with scores rolled up to parent elements.\n- **[Create hierarchical filters for Industrial Connected Workforce indicators](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-hierarchical-filter.md)**\n\nCreate multilevel filters with roll-up aggregation across nested organizational structures, which moves from site, to plan, to department, to functional location.\n\n- **[Download data visualizations as CSV or Excel files](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/export-data-vis-from-dboard.md)**\n\nAs a viewer, you now can download any data visualization, not only a List, as a CSV or XLS file.\n\n- **[Automatically set the aggregation period of data snapshots indicator trend lines](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/config-dv-time-series-ind-data.md)**\n\nSet the **Aggregation period** field in the **Trend by** settings to Auto so ****, the system automatically selects the aggregation period of data snapshot indicator trend lines based on the date range and business calendar.\n\n- **[Automatic aggregation of date-filtered data based on date range](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-date-filter-workspace.md)**\n\nFilter dashboards by business calendar and have the system infer the appropriate aggregation level at runtime. If you put a time series data visualization on a dashboard with a date filter, the aggregation of shown data adjusts automatically depending on the selected date range. This adjustment applies to both table and data snapshots indicator data.\n\n- **[Create custom data visualization filters with an improved condition builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/filter-dv-condition-builder.md)**\n\nWhen creating a data visualization for table data, you can create a custom filter when you specify the data source. The condition builder for the custom filter now has menus of fields, operators, values, and related tables.\n\n- **[Hide the Refresh action on data visualizations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-dv-sing-sc-ac.md)**\n\nIn the Headers and Borders section of data visualizations, use the **Show refresh option** check box to hide the **Refresh** icon \\[Omitted image \"refresh-icon.jpg\"\\] Alt text: in the Configuration settings of data visualizations. Data visualizations on cached dashboards never have the Refresh icon.\n\n- **[Migration Center enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/data-migration.md)**\n - As an analytics manager, migrate any Core UI dashboard to Platform Analytics in the Dashboard library.\n - Edit migrated content before activating it in the Platform Analytics experience.\n - Activate content selectively.\n - Total views of Core UI reports and other widgets are now migrated along with the Core UI content.\n- **[Dashboard element enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/edit-db-elements-in-ac.md)**\n\nMoving and resizing dashboard elements no longer opens the configuration panel.\n\n- **[Enhanced scheduled exports](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/schedule-export-dboards-data-viz.md)**\n\nWhen scheduling the email of dashboards or data visualizations, limit recipients based on reference qualifiers.\n\n- **[Public reports are unpublished](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/report-permission-issues.md)**\n\nOn upgrade, all public Core UI reports are unpublished to enhance security control. Report administrators can find the unpublished reports on the Reports Public \\[sys\\_report\\_public\\] table. They can then make the reports available through the Sharing UI in the Report Designer.\n\n\n
\n\nPlaybook\n\n\n\n- **[Required role update](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/user-access-playbooks.md)**\n\nAny tasks that previously required only the admin role now require the playbook.admin role instead.\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n
\n\nPolicy and Compliance Management\n\n\n\n- **[ServiceNow Otto® name announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.The Now Assist for IRM \\(sn\\_irm\\_gen\\_ai\\) plugin, which provides generative AI capabilities for RCM, has been renamed to ServiceNow Otto for IRM.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n- **[SAE columns in Control Attestations list view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/c_Attestations.md)**\n\nThe Control Attestations list view now displays the Control and Entity columns, showing the control name and associated entity for each assessment instance. These columns are visible on the Compliance Workspace, Tasks page, Employee Center, and Risk Portal.\n\n\n
\n\nPortfolio Planning\n\n\n\n- **[Summarize demands with the demand summarization skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/summarize-demands-in-ppw.md)**\n\nThe demand summary is generated in the **AI Overview** tab instead of the **Details** tab. The skill is set to trigger automatically, that is, the summary is generated on landing in this tab. Auto-generation is on by default and applies to demands in Submitted, Screening, Qualified, or Approved states. You can define the trigger to manually trigger as well, where users must select the **Summarize** button to generate the summary.\n\n- **[AI skills for Next Experience for Demand Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/ai-skills-in-demands-workspace-ppw.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n- **[Access execution records from Portfolio Plans](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/access-demands-from-portfolio-planning-views.md)**\n\nThe execution URL is updated on the planning item demand. New planning items demand will automatically use the new execution URL. The execution URLs on existing planning item demands continue to work but doesn't reflect the updated navigation. Run the **Update Demand Planning Item Execution URL** scheduled job to update the execution URL on the existing demands.\n\n\n- **[Next Experience for Demand Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/demand-workspace-ppw.md)**\n - The Demands icon has been added to the Portfolio Planning L1 menu to open the All Demands home page.\n - The **State** field on the All Demands home page has been color-coded for each state value.\n - The **Playbook**, **Details**, and **Docs** tabs have been added to the L2 menu of each demand to clearly and consistently group information.\n - The **Details** tab has been added to add and manage demand information such as financials and resource assignments.\n - The **Playbook** tab has been added to define clear stages and guided activities to read and follow. Selecting the name of a stage or activity navigates you to that stage or activity in the playbook. The **Skip**, **Update**, and **Mark Complete** options have been added to the activities of the playbook.\n - The **Docs** tab has been added to view and manage the documentation on the demand.\n - If you have the AI Control Tower plugin installed and the investment type of the demand is set to artificial intelligence:\n - The **AI Associations** section in the Demand details is displayed. The following fields are included:\n - **Product**: Enables you to select the product or system that the demand relates to.\n - **Impacted AI systems**: Links the impacted AI systems with the demand. You can select existing AI systems from the list or remove systems that are no longer relevant.\n - The **AI Checkpoint** stage is added to the demand default playbook. This stage includes the **Product** and **Impacted AI systems** fields.\n - The **Create AI System** option is added to the **Details** page of a demand for users with the sn\\_ai\\_steward role.\n - [Australia Patch 5](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-5.md)The **Financials** grid is added to the navigation menu of a demand. It has options to create cost plans, monetary benefits plans, expense lines, and create and compare baselines.\n - The **Dashboards** menu item is added for demands, providing **Overview**, **Financials**, and **Data Quality** tabs.\n - The following items have been added to the demand form and are available if you have the identify similar records AI skill activated:\n - The **Identify similar demands** button, which identifies and displays similar demands.\n - The **Similar Demands** tab in **Details**, which displays the list of similar demand records identified by AI.\n - The **AI Overview** tab is added to the navigation menu of a demand. It generates a demand summary on landing if the skill trigger is set to automatic. If the trigger is set to manual, a **Summarize** button is available to generate the summary.\n\n
\n\nPredictive AI for CSM\n\n\n\n- **[Now Assist > ServiceNow Otto announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto® introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n- **[Automated quality assurance dashboard](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/quality-assurance-management.md)**\n\nEnable admins to filter scoring parameters and sort agent and case lists. Admins can sort data, manage filters, and easily organize cases on the dashboard with the new sorting, visibility, and skill management capabilities.\n\n- **[Activate Now Assist skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/activate-now-assist-for-customer-service-management-csm-skills_0.md)**\n\nEnable admins to view detailed information about each Now Assist skill to make faster and more informed decisions about enabling skill capabilities.\n\n\n- **[Configure knowledge generation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/configure-knowledge-generation-in-now-assist_0.md)**\n\nEnable users with the **sn\\_skill\\_builder.admin** role to generate knowledge base articles in ServiceNow Otto for CSM by selecting the required input fields from a task record, reducing manual effort and streamlining the knowledge base generation process.\n\n- **[Configure Sidebar Summarization](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/configure-sidebar-summarization-in-now-assist.md)**\n\nEnable customer agents to generate summaries built from the required case and task tables in ServiceNow Otto for CSM as default tables can now be pre-selected and locked.\n\n- **[Provide Customer 360 insights agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/customer-service-management-ai-agent-collection-customer-360.md)**\n\nEnhanced Provide Customer 360 Insights with Enterprise Graph and AI agent deep research for richer, more contextual query results.\n\n- **[Triage cases agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/case-resolving-use-case.md)**\n\nMultilingual and localization flows in the Triage Cases workflow are now fully supported.\n\n\n
\n\nPrivacy Management\n\n\n\n- **[ServiceNow Otto® name announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.The Now Assist for Privacy Management \\(sn\\_prm\\_gen\\_ai\\) plugin has been renamed to ServiceNow Otto for Privacy Management.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n
\n\nProcess Mining\n\n\n\n- **[Automated finding names updated](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/automated-findings.md)**\n\nThe following automated finding names have been updated to include \"Transition\" in the name:\n\n - Slow duration \\(Transition\\)\n - Extreme duration \\(Transition\\)\n- **[Role names changed](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/components-installed.md)**\n\nRole names in Process Mining that previously included \"optimization\" have been updated to use the term \"mining\" instead. For example, the sn\\_process\\_optimization\\_admin role has been renamed sn\\_process\\_mining\\_admin.\n\n\n
\n\nProduct Catalog Management and Pricing Management\n\n\n\n- **Domain separation support**\n\nStarting with Product Catalog Management Core v19.1.0, all product catalog tables support the basic level of domain separation.\n\n\n- **[Custom context variable enhancement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/som-create-context-variable.md)**\n\nUse the **Applicable to** field in the Context Variable form to indicate that a custom context variable is to be used for pricing. The pricing engine uses this indicator to resolve pricing in the correct transaction scope, to help prevent mispricing of product bundles.\n\n\n\n- **[Product catalog interface enhancement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/using-product-catalog.md)**\n\nQuickly identify products with derived pricing through product tiles that display a message stating that the product price varies. Pricing is calculated and updated automatically based on selections made.\n\n\n
\n\nProduct Support for Technology\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Service delivery overview](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/proactive-service-exp-workflows/account-360-analytics-dashboard.md)**\n\nThe Service Delivery Overview L1 menu is added to the Service Operations Workspace and CSM/FSM Configurable Workspace.\n\n\n
\n\nProject Portfolio Management\n\n\n\n- **[AI skills for Demand Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/similar-demand-identification-using-now-assist.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Demand summarization skill enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/demand-summary-demand-classic.md)**\n\nThe demand summarization skill incorporates data from related entities when generating a summary. In addition to demand record fields, the summary includes insights from demand tasks, cost plans, monetary and non-monetary benefit plans, resource assignments, and work notes. The generated summary covers business requirements, timeline, risks, stakeholder comments, cost, effort, monetary and non-monetary benefits, and ROI.\n\n\n- **[Next Experience for Demand Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/demand-workspace.md)**\n\nThe new Next Experience for Demand Management provides a unified layout, guided stages, improved navigation, and enhanced capabilities such as Playbooks and Docs integration. As you move to Next Experience for Demand Management, you’ll find it easier to create, review, and manage demands with a cleaner layout and guided actions. The classic UI is still available, but new improvements will appear in the workspace.\n\nNext Experience for Demand Management is available with the Strategic Portfolio Management \\(SPM\\) Standard and Pro licenses.\n\n\n- **[Demand Management UI changes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/demand-form.md)**\n - The **Start date** and **Due date** column labels have been renamed **Planned start date** and **Planned end date**, respectively. This change is applicable only for new installations of the Australia version. To ensure continuity, if you’re upgrading to the Australia release from an earlier release, you’ll continue to see the prior labels.\n - If you have the AI Control Tower plugin installed and the investment type of the demand is set to artificial intelligence:\n - The **AI Associations** section in the Demand form is displayed. The following fields are included:\n - **Product**: Enables you to select the product or system that the demand relates to.\n - **Impacted AI systems**: Links the impacted AI systems with the demand. You can select existing AI systems from the list or remove systems that are no longer relevant.\n - An option to create an AI system under Related Links in the Demand form is available for users with the sn\\_ai\\_steward role.\n\n- **[Australia Patch 4](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-4.md)[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n
\n\nProject Workspace\n\n\n\n- **[RIDAC enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/manage-ridac-pw.md)**\n\nNew RIDAC menu is added on the L2 menu. These three pages are added under RIDAC menu:\n\n - AI-Identified Risks\n - RIDAC by Type\n - All RIDAC\n\n- **[Inline comments changes in Docs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/collaborative-project-planning-with-docs.md)**\n - The Add comments icon appears in the inline toolbar.\n - Commented text displays a yellow highlight and underline. Selecting commented text darkens the highlight and opens a comment popover showing the full thread, including reply count, user avatars, names, and relative timestamps.\n - The comment popover provides options to edit or delete comments. Edited comments display an **Edited** indicator.\n - Users can turn comment highlights on or off using the **Show comment highlights** or **Hide comment highlights** options in the More actions menu of the document.\n\n- **[AI-generated status reports](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/create-a-status-report-in-project-workspace.md)**\n\nThe **Generate status report** button has been added to generate status reports with AI assistance.\n\n- **[Configure project insights modal UI enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/email-project-summary-pw.md)**\n\nThe **Financials** and **RIDAC** check boxes have been added in the configure project insights modal.\n\n- **[Project insights generation skill enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/configure-project-insights-generation-skill.md)**\n\nNew admin configuration options are available for the project insights generation skill.\n\n- **[Project insights email template enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/email-project-summary-pw.md)**\n\nThe Financials and RIDAC sections have been added in the email template.\n\n- **[Project Workspace UI enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/use-projects-pw.md)**\n\nAn AI Insights page has been added to capture AI‑generated information for each project.\n\n- **[Skill name updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/ai-skills-project-workspace.md)**\n - Renamed the project doc summarization skill to the project doc generation and insights \\(Project Workspace\\) skill.\n - Renamed the planning item doc summarization skill to the planning item doc generation and insights \\(Strategic Planning\\) skill.\n - Renamed the EAP doc summarization skill to the EAP doc generation and insights \\(Enterprise Agile Planning\\) skill.\n - Added the project status generation in Project Workspace.\n- **[Project Workspace UI changes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/project-workspace-landing-page.md)**\n - Added a **Project reference** field to request and refresh forms that enables you to associate hardware requests with an SPM project.\n - Added an Asset Requests related list on the Project form that enables project managers to view, track, and monitor all associated hardware requests directly from a project.\n - The **Resources** tab in Project Workspace now opens the resource board within the same page instead of launching a new browser tab.\n\n- **[AI skills in Project Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/ai-skills-project-workspace.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n
\n\nPublic Sector Digital Services\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Enhancements to Grants Management: Program Setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/psds-using-grants-management-playbook.md)**\n - [Establish the Grant Program Budget in Grants Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/psds-config-gmp-pgr-budget.md)\n\nUse the restructured Program Budget step that is now organized into three sections: Program Budget, Budget Categories, and Award Allocation. Grant Program Managers can select from three award models—Single Award, Multiple Equal Awards, or Multiple Variable Awards—with budgets automatically derived from the Awards category. Real-time calculations update the Budget allocated and Balance left fields as you enter category percentages. This enhancement prevents completion until all of the program budget is allocated across the categories.\n\n - [Configure program lifecycle stepper](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/psds-config-gmp-pgr-lifecycle-stepper.md)\n\nDisable the six-step grant program lifecycle stepper at the instance level, reducing ambiguity about grant program state. By default, the stepper indicating the Preparing Program, Accepting Proposals, Evaluating, Awarding, Post-Award, and Closed states is hidden in the Grant Program record page and admins can enable it if required for deployments that follow a batch or competitive grant lifecycle. When turned off, program state is conveyed through existing status fields.\n\n- **[Enhancements to Grants Management: Proposal Playbook](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/psds-using-grants-management-playbook.md)**\n - [Screen a grant proposal in the Grants Proposal Playbook](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/psds-using-gmp-grant-proposal-screen.md)\n\nFlag and route a document back to the applicant while reviewing the proposal details in the screening step. The document persists in the Flagged section with all metadata intact. Grant program managers and Grant program directors can reverse the flag by selecting the reset status icon to move it back to Requires Verification with no data loss. Select Request Documents at the bottom of the Verify Documents screen to route flagged documents back to applicants automatically; this action creates a case task assigned to the applicant, sends a notification in the applicant portal prompting re-upload, and changes the document status to Pending Resubmission. Once the applicant uploads the corrected document, the Upload Additional Documents activity closes and you can continue verification, maintaining a complete audit trail throughout the process.\n\n\n\n- **[Updated Coral theme](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/next-experience-theming.md)**\n\nThe Coral theme has been improved to enhance usability across web, mobile, and portal experiences that use Next Experience and Core UI:\n\n - A fully overhauled color system for smoother gradients and better contrast.\n - Softer outlines and more rounded components for a new, accessible look.\n - A significantly improved dark mode with deeper blue tones for reduced eye strain.\n - New AI gradient styles and subtle animations to highlight intelligent features.\n - Smarter focus behavior that reduces visual clutter for mouse users.\n- **[Enhancements to Constituent Service Portals](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/portals-psds-exploring.md)**\n\nUI Enhancements have been made to all Public Sector Digital Services constituent portals by replacing legacy widgets \\(for example, portal banners, data lists\\) with standardized, CSM Configurable Widgets and components. The update verifies backward compatibility, migration guidance, usage analytics, and provide training for admins, and also enables dynamic data rendering, and better filtering across service flows.\n\n- **[Enhancements to Investigative Case Management Configurable Case role-based access](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/psds-config-icm-assign-user-roles-responsibilities.md)**\n\nExtend write access and restrict read access to cases based on Assigned Office, Assignment Group, or both to allow automatic case access alignment with organizational units without managing the Teams tab manually.\n\n- **[Enhancements to Document Screening](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/government-industry/psds-ai-skill-doc-screening.md)**\n\nApplicants can select a specific document type from a pre-configured, category-scoped list during upload, stored on the document record and displayed read-only to internal agents in both portal and Workspace views.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nStarting 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.\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n
\n\nPurchase Order Management\n\n\n\n- **[Changes in the purchase order exception page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/source-to-pay-operations/purch-order-exception-details.md)**\n\nThe New activity today section on the Purchase Order Management landing page has been expanded to list the most recent exceptions and tasks.\n\nThe **Exception intelligence** tab is enhanced to show the supplier spend patterns over time.\n\n\n
\n\nQuote Management\n\n\n\n- **[Enhancements to price ramps on quote lines](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/add-price-ramps-on-a-quote-line-item.md)**\n\nModify active ramp segments on amendment quotes to better manage pricing changes over time.\n\n - Split an active ramp segment into multiple shorter segments within the original term, with the system automatically assigning the correct line types and effective dates for each resulting segment.\n - Merge split segments back into the original ramp while the quote is in draft state.\n - Remove segments that are no longer needed.\n - Edit the quantity in the product configurator. The quantity field for the last ramp segment of configurable and bundled products is read-only.\n- **[Quote approvals](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/explore-advanced-approval-for-sales.md)**\n\nBuild on existing quote approval workflows with greater control and flexibility\n\n - Receive automated reminder notifications for pending approvals steps based on reminder schedules configured by your administrator.\n - View the escalated approver on the approval step card when an approval step is escalated, so you can clearly identify who is responsible for the next action.\n - Add ad-hoc approvers to an approval request outside the configured approval workflow when additional review is needed.\n - Override an approval to advance a quote when permitted by your organization's approval configuration.\n\n
\n\nRecommended Actions for Operational Technology Service Management \\(OTSM\\)\n\n\n\n- **[Contextualize UI action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/use-ai-enhanced-ra-otsm.md)**\n\nThe **Contextualize** UI action was added to the Recommendations panel in the Industrial Workspace for external documents related to the selected OT incident.\n\n\n
\n\nRecruitment workspace\n\n\n\n- **[Get overview of recruitment workload](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/recruitment-workspace-oveview.md)**\n\nView all the job requisitions where you're listed as an additional recruiter or recruitment coordinator, on the home page cards and list view in Recruitment workspace. Previously, only the primary recruiter saw these requisitions in Recruitment workspace.\n\n\n
\n\nRegulatory Change Management\n\n\n\n- **[ServiceNow Otto® name announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.The Now Assist for IRM \\(sn\\_irm\\_gen\\_ai\\) plugin, which provides generative AI capabilities for RCM, has been renamed to ServiceNow Otto for IRM.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n- **[Default AI model provider for regulatory alert recommendation skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/configure-recommendation-skill-for-a-regulatory-alert.md)**\n\nAfter upgrading to version 22.4.0, the regulatory alert recommendation skills in ServiceNow Otto for Integrated Risk Management \\(IRM\\) use AWS Claude as the default model provider.\n\n- **[Default AI model provider for agentic workflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/using-agentic-ai-workflows.md)**\n\nAfter upgrading to version 22.4.0, the Get regulatory analysis and Generate regulatory action plans agentic workflows use AWS Claude as the default model provider.\n\n\n- **Now Assist skills for Risk & Sustainability**\n\nThe skill family name Regulatory change management has been updated to Regulatory change to improve naming clarity and consistency within Now Assist skills for Risk & Sustainability under the Technology workflow module in the AI Admin Hub Center.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n
\n\nRetail Strategic Portfolio Management Suite\n\n\n\n- **[Retail Strategic Portfolio Management Suite playbooks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/use-playbooks-spm-retail.md)**\n\nThe **Playbooks** option is available in the L-2 navigation menu of the Project Workspace for retail projects created from a template.\n\n- **[Project type fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/spmr-project-type-fields.md)**\n\nNew Project Type form fields to mark important dates based on the created project type.\n\n\n
\n\nSales CRM for Telecommunications\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n
\n\nSecurity Center\n\n\n\n- **[Security Hardening tool Updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/security-hardening-settings.md)**\n\nThe security Hardening tool has been updated to the latest Instance Security Hardening Settings V7.\n\n\n
\n\nSecurity Incident Response\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Assign groups in PIR user assignment rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/create-pir-assignment-rules.md)**\n\nUser Assignment Rules for Post-Incident Review \\(PIR\\) assessments in the SIR module now support group-based assignment in addition to individual user selection. You can configure assignment rules using groups. The PIR automatically reflects group membership updates without requiring manual edits to the assignment rules configuration.\n\n\n
\n\nSelf-service and omnichannel engagement for CSM\n\n\n\n- **[Integrating WhatsApp with Customer Service Management using the WhatsApp Cloud API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/messg-integrating-whatsapp-with-csm-whatsapp-cloud.md)**\n\nThe conversation thread includes an inline audio player for received audio messages, with play, pause, and seek controls.\n\n\n- **[Integrating WhatsApp with Customer Service Management using the WhatsApp Cloud API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/messg-integrating-whatsapp-with-csm-whatsapp-cloud.md)**\n\nWhatsApp direct integration gives agents richer conversational tools and gives customers more ways to reach for support. The key updates include:\n\n - Access synthesized responses generated from Now Assist Virtual Agent \\(NAVA\\) in WhatsApp direct conversations.\n - Play audio messages directly in the agent chat interface.\n\n- **[Call Wrap-Up](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/initiate-agent-wrap-up-during-active-call.md)**\n\nManage wrap-up during active calls using new UI components in the Active Call window in the CRM Workspace:\n\n - An **Open Wrap-Up** button to initiate the wrap-up process during an active call.\n - **Minimize** and **Expand** controls on the wrap-up modal to manage screen space while remaining on the call.\n\n- **[Walk-up Check-in on Business Portal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/walkup-checkin-businessportal.md)**\n\nInitiate a walk-up check-in directly from the Business Portal home page without navigating away from the landing experience.\n\n- **[Portal Data List widget JSON parameters](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/portal-datalist-widget-data-json.md)**\n\nGenerate dynamic record view URLs with the Data List widget. Portal admins can configure the target record context, parent table, child table, or reference table. The portal builds the URL with the relevant parameters to render the correct record view at runtime.\n\n- **[Portal Object widget instance options form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/port-object-inst-options.md)**\n\nAdds a Dynamic portal object instance option to the Portal Object widget \\(turned off by default\\). When turned on, the widget reads the extended table, record ID, and view from URL parameters. The widget derives the card title, image field, summary view fields, and detail view from the view definition on the extended table. This eliminates the need for static configuration in the widget instance.\n\n\n- **[Interaction Controls Component \\(ICC\\) call features](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/interaction-controls-component-icc-call-interaction-features.md)**\n\nThe following UI components are available in the Active Call window, enabled via ICC in the CRM Workspace:\n\n - A **Help Request** button to seek supervisor assistance during an active call.\n - A **Cancel Help Request** or **End Help Request** button to cancel and end a submitted help request at any time during the active call.\n - An overflow menu icon \\(ellipsis\\) to access secondary call control buttons when the number of controls exceeds five or when the available display width is exceeded.\n- **[Using the interaction and case page for callback request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-config-ws-pages-templates.md)**\n\nThe following UI components have been added on the interaction and case pages:\n\n - A **Schedule callback** button on interaction and case pages to enable agents to schedule callbacks on behalf of customers.\n - A **Reschedule** button on the callback task record page to enable agents to modify scheduled callback date and time on behalf of customers.\n - A **Cancel** button on the callback record page to enable agents to cancel callbacks created on behalf of customers.\n - A **Scheduled callbacks** tile in the contextual side panel to enable agents to view and manage upcoming callbacks while working on interactions or cases.\nScheduled callbacks list view: A **Scheduled callbacks** list view has been added in Agent Workspace to enable agents to view all scheduled callbacks and open any callback to access its task record management.\n\n- **[Using the email interaction page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/using-email-interaction-page.md)**\n\nThe following UI components have been added on the Email Interaction page:\n\n - A **Compose Email** UI option to contact and consumer records for initiating outbound email interactions from these records.\n - Clickable email addresses to contact and consumer records to open the email composer with the recipient address automatically inserted.\n - A **Transfer Email** option with list of available agents and queues has been added for AWA or CCaaS‑routed email interactions. Agents can transfer the interaction to the selected queues or agents.\n - A unified wrap‑up dialog has been added to provide a single closure experience for email interactions routed through AWA or CCaaS.\n - A **Summarize** button on the email interaction page to trigger an AI summary of the full conversation.\n - A Refresh Summary icon on the summary card to manually re-trigger summarization at any point.\n - Feedback icons and copy icon on the summary card to indicate whether the summary is helpful and to copy the summary text.\n\n- **[Customer Service Portal Base](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/configure-csm-service-portals.md)**\n\nStarting with the Australia release, the Customer Service Portal Base plugin \\(com.snc.csm\\_portal\\_base\\) has been migrated to the App Store as a standalone application. Future enhancements are delivered through the Customer Service Portal Base store app. This change improves packaging, versioning, and deployment flexibility for implementations that require portal framework, responsive design, case management, knowledge integration, and community features. The store app also includes email integration, translation support, attachment handling, and mobile enhancements.\n\n- **[Subscriptions and Activity Feed Framework](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/actsub-api.md)**\n\nStarting with the Australia release, the Subscriptions and Activity Feed Framework plugin \\(com.snc.subscriptions\\_activity\\_feed\\) has been migrated to the App Store as a standalone application. Future enhancements are delivered through the Subscriptions and Activity Feed Framework store app. This change improves packaging, versioning, and deployment flexibility for implementations that require subscription framework, activity tracking, notification preferences, or context management.\n\n- **[Walk-Up for CSM](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-walkup-experience.md)**\n\nStarting with the Australia release, the Walk-up for CSM plugin \\(com.snc.walkup\\_for\\_csm\\) has been migrated to the App Store as a standalone application. Future enhancements are delivered through the Walk-up for CSM store app. This change improves packaging, versioning, and deployment flexibility for implementations that require subscription framework, activity tracking, notification preferences, or context management.\n\n\n
\n\nService Catalog\n\n\n\n- **[Use UI Policy tab to add and manage the UI policies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/create-ui-policies-in-catalog-builder.md)**\n\nPreviously, when creating or editing a question in Catalog Builder, users could define UI policies or dynamic behavior by selecting the UI policies icon \\(\\[Omitted image \"dyn-beh-quest.png\"\\] Alt text: UI policies icon\\). This option has been removed. Now, users must directly use the UI Policy tab to add and manage the UI policies \\(actions, conditions, scripts, and other required details\\) to the catalog item.\n\n\n
\n\nService Exchange \\(formerly Service Bridge\\)\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Health dashboard](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/service-exchange/se-se-center.md)**\n\nThe Health dashboard has been relocated to the Service Exchange Center. Access a more holistic view of system health that includes a resolution center, connection health, and built-in scan suites providing centralized visibility and faster troubleshooting of integration issues.\n\n\n
\n\nService Operations Workspace for ITSM\n\n\n\n- **[Generate, update and publish PIR](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/review-update-pir-mim-sow.md)**\n\nPerform the following actions on the PIR if you have the incident\\_write role and added as co-contributor to the PIR:\n\n - Update the state or publish the PIR.\n - Refresh the Incident Summary data on the PIR.\n - Create PIR custom event.\n - Search, add, edit and save co-contributors \\(Users\\) for PIR.\n\n- **[Configure reference field auto-load behavior from SOW Admin Center](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/admin-center-sow.md)**\n\nUse the Reference field auto-load behavior option from the SOW Properties section of the SOW Admin Center to configure the **Reference search on click** \\(**ref\\_search\\_on\\_click**\\) UX page property. The option enables you to configure the automatic searching of field value results displayed for reference fields such as Configuration item, Service offering, and Service.\n\n- **[Recent list links in SOW record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/view-inc-record-info-contextual-sidepanel.md)**\n\nSelect the Recent incidents, Recent interaction, or Recent tasks links from the Record information side panel of a SOW record displays the 10 most recent records irrespective of their timeline instead of showing the records from last seven days. You can select the **View All** option to view additional records as well.\n\n\n
\n\nService Portal\n\n\n\n- **[Create a portal theme](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_CustomCSS.md)**\n\nCreate theme variants for Service Portal themes to tailor the visual experience for your users, which can help you match your brand.\n\n\n
\n\nServiceNow AI Lens\n\n\n\n- **Default app on launch setting on the ServiceNow AI Lens downloads and preferences page**\n\nThe ServiceNow AI Lens Downloads page has been renamed to ServiceNow AI Lens downloads and preferences, and a Default app on launch setting has been added to the page. The setting includes the following options:\n\n - Browser \\(no installation required\\): Launches AI Lens from your browser when you start a session.\n - Desktop app: Launches AI Lens desktop application when you start a session.\n- **UI updated to reflect ServiceNow Otto branding**\n\nThe UI has been updated to reflect the ServiceNow Otto branding. Icons, and UI text have been updated throughout the interface to use Otto terminology and visual identity.\n\n- **New Upload button and Upload file dialog**\n\nThe AI Lens page, which opens in your browser when you select Create with Lens or Update with Lens button, now provides an Upload button. Selecting Upload opens the Upload file dialog, where you can add or drag to upload files. After attaching, you can optionally rename the files. To upload the files, select Next. After uploading, submit the files for ServiceNow AI Lens to analyze and auto-fill your form fields.\n\n\n- **[Quick visual distinction between AI-filled form fields and manually filled fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-record-sn-lens.md)**\n\nServiceNow® AI Lens now uses visual gradient indicators to distinguish AI-filled form fields from manually entered data.\n\n\n- **[New screen with browser and desktop app access options](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-record-sn-lens.md#use-your-browser)**\n\nA new ServiceNow AI Lens screen opens when you select the **Create with Lens** button on a list view or **Update with Lens** button on a form. The screen provides the following options:\n\n - **Capture screen**: Captures a screen from your browser and lets ServiceNow AI Lens analyze its contents to auto-fill form fields.\n - **Open AI Lens desktop**: Opens the ServiceNow AI Lens desktop application for the full range of capabilities, including capturing multiple screens and uploading files.\n- **[Preview screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-record-sn-lens.md#use-your-browser)**\n\nThe new preview screen displays the screen that ServiceNow AI Lens captured before submitting for analysis. The screen provides the following options:\n\n - **Crop**: Select to crop the captured screen to specify the area that you want ServiceNow AI Lens to analyze, before submitting it for analysis.\n - **Additional instructions \\(Optional\\)**: Enter instructions to guide ServiceNow AI Lens in analyzing specific information from the captured screen.\n - **Re-capture**: Select to discard the current capture and repeat the screen capture process.\n - **Analyze**: Select to submit the captured screen for analysis and then auto-fill the form fields.\n\nNo changes in this release.\n\n
\n\nServiceNow AI Platform core feature\n\n\n\n- **[Data Egress and Usage by Domain tabs added to the Inbound API Integration Usage dashboard](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/inbound-api-integration-usage-dashboard.md)**\n\nView data volumes returned in integration responses and monitor domain-level usage.\n\n\n- **[Country setting added to Language and Region preferences](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/next-experience-language-preferences.md)**\n\nUsers can select their country from the Next Experience language and region preferences.\n\n- **[New options for date and time format in the User record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/user.md)**\n\nUsers can select from new options for Date format and Time format in the User record.\n\n- **[Control whether date and time formats reflect the user locale by default](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/set-localization-props.md)**\n\nConfigure date and time formats to reflect the user locale when no date or time format has been selected in user preferences through the **glide\\_i18n.date.default\\_to\\_locale** system property.\n\n- **[Control how to set the language for guest users](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/set-localization-props.md)**\n\nUse a guest user's IP address to set their language through the **glide\\_i18n.ip\\_geolocation** system property.\n\n- **[Activate additional choices for countries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/activate-country-choices.md)**\n\nActivate additional choices for countries in the Next Experience language and region preferences or in a User record.\n\n- **[ECMAScript 2021 \\(ES12\\) JavaScript mode supports additional scripting features](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/javascript-engine-feature-support.md)**\n\nUse additional scripting features in applications or scripts that use the ECMAScript 2021 \\(ES12\\) JavaScript mode.\n\n- **[JavaScript engine updated with changes from the Rhino engine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/updates-javascript-engine.md)**\n\nThe JavaScript engine on the ServiceNow AI Platform was updated to incorporate changes from the open-source Rhino JavaScript engine.\n\n- **[New Normalization Data Services system property](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r_AvailableSystemProperties.md)**\n\nCreate duplicate records in core\\_company extension tables by setting the **com.glide.acl\\_check\\_all\\_filter\\_on\\_new** system property to true to reference account records.\n\n- **[System properties secured by default](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r_AvailableSystemProperties.md)**\n\nGlide properties that can impact instance security are set to secure values by default. For more information about which system properties are affected and why, see the [Glide Property Hardening \\[KB1982254\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1982254) article in the Now Support Knowledge Base.\n\n- **[Tracking records in unauthenticated users' sessions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/web-embeddables.md)**\n\nTrack records created, modified, or deleted by unauthenticated users to enable session-based ACL access on public forms, portals, or workflows.\n\n- **[Manage guest user access to records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/web-embeddables.md)**\n\nRestrict guest user access to records they created or updated during their current session using the 'is in session' condition builder on the ACL form for Sys ID fields.\n\n- **[Session-based guest access](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/web-embeddables.md)**\n\nManage REST GraphQL security with path-based ACLs that are enforced without needing to require authentication for access to an API.\n\n\n
\n\nServiceNow IDE\n\n\n\n- **[Updated Activity Bar](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/servicenow-ide-user-interface.md)**\n\nThe Activity Bar includes additional views for bookmarks and recent activity, and the Metadata Explorer view has been replaced with the File Categories and Apps views.\n\n\n
\n\nServiceNow Lux Lab for VS Code\n\n\n\n- **ServiceNow Lux Lab for VS Code**\n\nAs of the September 2026 release, the ServiceNow AI Experience Lab for VS Code extension is now named ServiceNow Lux Lab for VS Code. The extension's functionality is unchanged; only the product name has been updated.\n\n\n
\n\nServiceNow Otto for App Engine\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n
\n\nServiceNow Otto for Configuration Management Database \\(CMDB\\)\n\n\n\n- **Now Assist > ServiceNow Otto announcement**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.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.\n\n\n- **[New role required for the Create configuration item agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/na-cmdb-awf-ci-creator.md)**\n\nThe sn\\_cmdb\\_admin role is now required to use the 'Create configuration item' agentic workflow \\(was sn\\_cmdb\\_editor\\).\n\n- **Skills now also require the now\\_assist\\_panel\\_user role**\n\nAI skills that execute in the Now Assist panel now require both the cmdb\\_dedup\\_admin and now\\_assist\\_panel\\_user roles.\n\n\n
\n\nServiceNow Otto for Contract Management Pro\n\n\n\n- **[Search in contracts document](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cmpro-na-converse-ask-ques-new.md)**\n\nContract document-based conversational search queries now return all matching results instead of 10 results. Use show more option to load the remaining results.\n\n- **[Search in contract metadata](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cmpro-na-search-metadata.md)**\n\nIn conversational search, introduced an option to preform in-document search after the contract metadata search results are available.\n\n\n- **[ServiceNow® AI implementation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Default large language model provider](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\nThe default model provider for contract metadata extraction, contract analysis, and contract obligation extraction is Azure OpenAI.\n\n- **[Improved missing clause detection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cncore-NA-review-land.md)**\n\nMissing clause detection in contract revision using the contract analysis skill has been enhanced for accuracy. The setup, configuration, and review experience remains unchanged across all supported workspaces.\n\n\n- **[Configure use case mappings for metadata and obligation extraction](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cmpro-na-usecase-mappings-me.md)**\n\nClear the **Contracts created from contract request** check box on the use case mapping forms for the contract metadata extraction and contract obligation extraction skills to extract metadata and obligations from signed contracts that are uploaded directly on a contract record.\n\n- **[Conversational contract search and insights](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/cmpro-agentic-workflows.md)**\n\nThe conversational search feature's improved experience enables you to:\n\n - View results in a listing view, making it easier to scan, compare, and navigate contract information.\n - Open contract documents directly from the search results and perform an in‐document search.\nThe conversational search feature does not support searching within contract documents that are scanned PDFs.\n\n\n
\n\nServiceNow Otto for Creator\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Use the app generation skill to generate apps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/sns-app-gen-use-app-gen-skill.md)**\n\nBuild Agent is the default setting for app generation in ServiceNow Studio. To continue using the app generation skill, change the setting in ServiceNow Studio.\n\n\n
\n\nServiceNow Otto for FSM\n\n\n\n- **Primary action button for Now Assist Virtual Agent**\n\nAccess Now Assist Virtual Agent from a primary action button in the ServiceNow Agent mobile app navigation bar. Administrators can configure this button to launch Now Assist Virtual Agent or another global function. When configured for Virtual Agent, tapping the button opens Now Assist without additional navigation steps.\n\n- **AI visual indicators**\n\nConsistent gradient styles indicate when AI is assisting or augmenting an experience. Gradients appear across AI-powered features in Workspace, UI16, and mobile interfaces. Gradients subtly animate during AI processing and return to a static state when complete.\n\n- **Updated icons in Now Assist Virtual Agent**\n\nThe Now Assist Virtual Agent interface includes updated icons for web search, photo upload, and microphone functions.\n\n\n- **Create Work Order AI agent performance improvements**\n\nThe Create Work Order AI agent was optimized to reduce latency and improve response times. Inter-agent communication was streamlined to minimize redundant processing during work order creation.\n\n\n
\n\nServiceNow Otto for Financial Services Operations \\(FSO\\)\n\n\n\n- **[Now Assist > ServiceNow Otto announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Updated default model provider for ServiceNow Otto for FSO skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/financial-services-operations/configure-fso-now-assist-skills.md)**\n\nThe 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.\n\n\n
\n\nServiceNow Otto for HR Service Delivery \\(HRSD\\)\n\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n
\n\nServiceNow Otto for IT Service Management \\(ITSM\\)\n\n\n\n- **Now Assist > ServiceNow Otto announcement**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.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.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n- **[Customize the change risk assessment answer generator skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/cust-now-assist-itsm-change-risk-assessment-skill.md)**\n\nControl the data that the change risk assessment answer generator skill uses to suggest answers. Create, modify, or deactivate **AI Risk Data Sources** to change which related records and knowledge articles the skill receives. Six data sources are available out of the box, including related affected CIs, impacted services, impacted business applications, service offerings, active change tasks, and outages. To change which change request fields the skill reads, update the `sn_itsm_gen_ai.com.snc.asmt_answer_generator.change_request_fields` system property.\n\n- **[IT Service Management AI agent collection assess quality of a change request agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/now-assist-itsm-aiagents-assess-quality-change-request-workflow.md)**\n - Use the assess quality of a change request agentic workflow to rate a change request and get field improvement suggestions. The change quality assessor AI agent rates the request against an active change policy document, suggesting values only for fields the policy defines. If no policy applies, the agent rates the request against similar closed change requests.\n - The agent scores the short description, description, implementation plan, backout plan, test plan, risk and impact analysis, and justification. Results are recorded in the **AI Change Quality Scores** table.\n - Track change quality trends in Platform Analytics on the `ai_change_quality_score` table. A line chart shows the average score by month.\n - To change how the agent evaluates a field, or to assess a custom field, override the `POLICY_EXTRACTION_KEYS` entries in the `ChangeQualityUtil` script rather than the protected `ChangeQualityUtilSNC` script. This ensures your changes remain after you upgrade. Use the `u_custom_field` entry to assess a custom field, and use the `overall_chg_policy` entry to set policies for the whole change request.\n\n- **[Editing change request skills using Now Assist Skill Kit \\(NASK\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/cust-now-assist-itsm-change-risk-skill.md)**\n\nEasily edit the change request risk explanation and change request summarization skill prompts and inputs directly in the Now Assist Skill Kit \\(NASK\\).\n\n- **[Configuration item details for suggest configuration items for a change request workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/now-assist-itsm-aiagents-suggest-configuration-items-for-a-change-request.md)**\n\nProvide details such as class, location, and environment to find configuration items \\(CIs\\) relevant to a change request while using the suggest configuration items for a change request agentic workflow from the Now Assist panel.\n\n- **[Role masking for change risk explanation skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/supporting-information-now-assist-itsm.md)**\n\nEnhance security for the change request risk explanation skill by enabling admins to limit roles that are inherited by the user.\n\n\n- **[Some generative AI skills are turned on by default](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-assist-skills-on-by-default.md)**\n\nThe new default behavior works as follows:\n\n - New customers: When you install an AI product, designated skills are turned on automatically.\n - Existing customers who are upgrading \\(starting with Australia Early Access\\): Any previously unconfigured skill is turned on automatically \\(the skill was never configured and turned on, then turned off again\\). Previously configured skills that were turned on, then off, remain inactive.\n- **[Renaming the Incident assist skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/now-assist-itsm-incident-assist.md)**\n\nThe incident assist skill has been renamed to **\\[DEPRECATED\\] Incident assist**.\n\n- **[Renaming demo voice AI agents](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/now-assist-itsm-aiagents-voice.md)**\n\nThe voice AI demo agents have been renamed as primers.\n\n- **[Skills activated by default in Now Assist for ITSM](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/using-now-assist-for-itsm.md)**\n\nFor new ServiceNow Otto for IT Service Management \\(ITSM\\) users, the following skills are activated by default:\n\n - Resolution notes generation\n - Knowledge generation\n - Chat reply recommendation\n- **[Virtual agent topics available as demo data](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/itsm-va-prebuilt-topics.md)**\n\nThe Virtual Agent topics listed in this table have been renamed and are now available as demo data.\n\n |Existing name|Updated name|\n |-------------|------------|\n |Add Comment To incident|\\(DEMO\\) Add Comment To incident-LLM|\n |Approve Sysapproval Approver|\\(DEMO\\) Approve Sysapproval Approver-LLM|\n |Change Password|\\(DEMO\\) Change Password \\(Template\\) - LLM|\n |Check IT Ticket Status|\\(DEMO\\) Check IT Ticket Status \\(Template\\)|\n |Close incident|\\(DEMO\\) Close incident-LLM|\n |Explain change risk|\\(DEMO\\) Explain change risk|\n |Mark incident Unresolved|\\(DEMO\\) Mark incident Unresolved-LLM|\n |Open IT Ticket|\\(DEMO\\) Open IT Ticket \\(Template\\)-LLM|\n |Reject Sysapproval Approver|\\(DEMO\\) Reject Sysapproval Approver-LLM|\n |Reset Password|\\(DEMO\\) Reset Password \\(Template\\) - LLM|\n |Resolve incident|\\(DEMO\\) Resolve incident-LLM|\n |Unlock Account|\\(DEMO\\) Unlock Account \\(Template\\) - LLM|\n |View And Add Comments|\\(DEMO\\) View And Add Comments-LLM|\n\n\n
\n\nServiceNow Otto for Legal Service Delivery \\(LSD\\)\n\n\n\n- **[Summarize a legal request or matter by using ServiceNow Otto for Legal Service Delivery \\(LSD\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/now-assist-lsd-summarize-case.md)**\n\nSummarization now includes data from extended practice area tables, providing context‑rich summaries for your legal requests and matters.\n\n\n
\n\nServiceNow Otto for Operational Technology \\(OT\\) Service Management\n\n\n\n- **[Summarize UI action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/summarize-ot-incident-now-assist.md)**\n\nThe **Summarize** UI action was added to OT incident records in the Industrial Workspace so you can automatically summarize the incident details.\n\n- **[Generate resolution notes UI action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/generate-resolution-notes-ot-incident.md)**\n\nThe **Generate resolution notes** UI action was added to OT incident records in the Industrial Workspace so you can generate resolution notes after the incident state is set to **Resolved**.\n\n**Note:** This UI action appears after the OT incident state is set to **Resolved**.\n\n\n
\n\nServiceNow Otto for Software Asset Management \\(SAM\\)\n\n\n\n- **[Troubleshoot button alongside the error message on the Integration profile form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/troubleshooting-saas-now-assist-sam.md)**\n\nThe **Troubleshoot** button is available for all SaaS integrations on the error message that is displayed when connection validation fails due to an error. When selected, the button triggers the generation of error summary and resolution guidance.\n\n\n
\n\nServiceNow Otto for Workplace Service Delivery \\(WSD\\)\n\n\n\n- **[Now Assist > ServiceNow Otto announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n
\n\nServiceNow Otto in Platform Analytics\n\n\n\n- **[Improved overview pages for skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/activate-aide-explorer.md)**\n\nWhen you select **View details** on the tile of an AI skill in AI Admin Hub, you now get more information:\n\n - A more detailed description of the skill\n - Key benefits of the skill\n - Required and recommended skills to go with the skill\n\n- **[Promote selected indicators in AI Search results](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/indicator-scope-control.md)**\n\nAdd high-quality indicators that you identify to a list. The indicators on that list are given a boost in AI Search results for Query Generation.\n\n- **[View more indicator insights in Extended analysis](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/hidden-insights.md)**\n\nSee directional trends over time and indicator target information in Extended analysis summaries.\n\n- **[Improvements to data visualizations in Query Generation responses](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/ask-expl-questions.md)**\n - Single-score charts now render sparklines by default.\n - When a user query on indicator data does not specify a visualization type, the response returns the indicator's default chart type.\n- **[Now Assist renamed to ServiceNow Otto®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/now-assist-platform-analytics.md)**\n\nThe Now Assist Admin Console is now AI Admin Hub and many other changes have been made. This renaming is a work in progress.\n\n\n- **[Query indicator data](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/ai-data-explorer-implementation-checklist.md)**\n\nGet scores from automated indicators in your AI Data Explorer explorations. Only classic automated indicators, not Data snapshots, are supported.\n\n\n- **Explorations not available from visualization or list for unsupported scope**\n\nYou can't open AI Data Explorer from a data visualization or list that shows data from a protected scope that is not supported.\n\n- **[Improvements to generated segments](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/querygen-segments.md)**\n - The names of automatically generated segments now include both the module name and the name of the application it belongs to.\n - Improved logic to join conditions for segments generated from reports and report sources. More complex conditions such as global OR are now supported.\n\n- **[Explore data from protected scopes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/enable-aide-secure-scope-apps.md)**\n\nProvide access to protected application scopes to AI Data Explorer and Query Generation, and you can use data from those application tables in explorations. \\(Query Generation bundle 5.2\\)\n\n- **[Improvements to how segments are handled](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/querygen-segments.md)**\n\n - Manual segments are re-ranked to take priority over automatically generated segments.\n - Prompt changes made to better support manual segments.\n - More segments are passed to the LLM to increase the chance of the correct segment getting selected. Twelve segments are passed instead of three.\n - Segments longer than 2000 characters are dropped to prevent context window bloat.\n\\(Query Generation bundle 5.2\\)\n\n- **[Query Generation support for Glide Lists](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/querygen-unsupported-field-types.md)**\n\nQuery Generation now supports Glide List fields on tables.\n\n\n- **[Customize semantic metadata in configuration tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/customize-semantic-metadata.md)**\n\nCustomize semantic descriptions and usage instructions in the table and column configuration tables. Unlike the previous method of editing Entity and Dimension records, these changes can be transferred between instances through update sets.\n\n- **[View recommended actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/expl-view-recommended-actions.md)**\n\nAI Data Explorer can suggest actions based on the insights that it generates in an exploration.\n\n- **[Ask questions about FX currency data](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/qg-supported-query-operations.md)**\n\nQuery Generation now supports the FXCurrency \\(Currency 2\\) data type. This means that you can use AI Data Explorer to explore financial operations data, including those within Source-to-Pay Operations.\n\n- **[Benefit from improvements to segments](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/querygen-segments.md)**\n\nSegments are reusable definitions in Query Generation that provide non-obvious context to assist the semantic layer or LLM to select the correct dimension and values. Users can create manual segments via a new form. A scheduled job synchronizes manual and autogenerated segments. This job also cleans up segments to help surface the correct segments and reduce noise.\n\nManual segments are re-ranked to take priority over automatically generated segments.\n\nDomain separation is also now supported, with a Domain field on the Segments table. Segments based on reports and filters inherit the source domain. Manual segments have domains that are passed up to the Segments table on synchronization. Segments aren't supported for modules on domain-separated instances.\n\n\n- **[Query formula indicator scores](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/indicator-vs-table-data-source-selection.md)**\n\nIn AI Data Explorer, your queries can now reference information from indicator formulas, such as \"What percentage of open incidents are Priority 1?\"\n\n- **[Improved overview pages for skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/activate-aide-explorer.md)**\n\nWhen you view details from the tile of an AI skill in AI Admin Hub, you now get more information:\n\n - A more detailed description of the skill\n - Key benefits of the skill\n - Required and recommended skills to go with the skill\n\n
\n\nServiceNow SDK\n\n\n\n- **[Flow API supports Service Catalog triggers and actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/fluent-flow-api.md)**\n\nUse triggers and actions related to Service Catalog with the Flow API.\n\n- **[Access Control List API supports protection policies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/acl-api-now-ts.md)**\n\nControl whether someone can view or edit an access control list \\(ACL\\) with the protectionPolicy property in an ACL object.\n\n- **[Keys updated for static assets in full-stack applications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/building-applications-source-code.md)**\n\nStatic UX Assets \\[sys\\_ux\\_lib\\_asset\\] in full-stack applications have updated keys in the `keys.ts` file. UX Asset sys\\_ids aren’t changed.\n\n\n
\n\nServiceNow Studio\n\n\n\n- **[AI tools and files in ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/working-with-now-assist-tools-sn-studio.md)**\n\nServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including ServiceNow Studio. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n\n- **[Build Agent in ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/build-agent-in-servicenow-studio.md)**\n\nDevelopers who prompt Build Agent to create an app from the [ServiceNow Developer site](https://developer.servicenow.com/dev.do) are redirected to ServiceNow Studio instead of ServiceNow IDE to continue building their app.\n\n\n- **[Preview an app file in ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/preview-app-file.md)**\n\nFiles with preview capabilities open directly in preview mode in ServiceNow Studio, bypassing the record view. This change reduces the number of steps required to view file content and keeps developers focused on their work without manual mode switching.\n\n\n- **[Integrated tab groupings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/qs-open-apps-files-across-scopes.md)**\n\nIntegrated tabs are no longer color-coded or grouped by scope. You can see a list of the open files by selecting the more actions icon and selecting **Show Opened Editors**.\n\n- **[Build Agent in ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/build-agent-in-servicenow-studio.md)**\n\nBuild Agent is the default setting for AI-assisted app generation in ServiceNow Studio. You can change this setting in the ServiceNow Studio user preferences menu.\n\n\n- **[Create a collection of files in ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/qs-create-a-collection.md)**\n\nAs of the Australia Patch 3 \\(June\\), the Bookmark icon is now the Collections icon. Bookmarks are available as a category under collections.\n\n- **[ServiceNow Studio user interface](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/servicenow-studio-user-interface.md)**\n\nThe Navigator panel icons in ServiceNow Studio have changed slightly in size and appearance, but not in function.\n\n\n
\n\nServiceNow Vault\n\n\n\n- **[Removed `security_admin` role from Vault console admin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/vault-roles.md)**\n\nThe `security_admin` role has been removed from the roles required to elevate to and administer Vault Console. All administrative tasks including that of viewing tools metrics across the dashboard is now available to the `sn_vault_console.vault_console_admin`\n\n- **[ServiceNow Otto name change](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/now-assist-vault-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Default model provider for AI assets](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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. Azure OpenAI is the default model for all AI assets in ServiceNow Otto for Vault.\n\n\n
\n\nSmart Assessment Engine\n\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n- **[Create an assessment template category](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/sae-asmnt-template-category-create.md)**\n\nEnables one or more roles to access a template category with the multiselect **Category Roles** field.\n\n\n- **[Filtering questions in an assessment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/filtering-questions-in-an-assessment.md)**\n\nApply multiple assessment filters at once \\(for example, **Unanswered** + **AI-assisted**\\). The navigation pane dynamically grays out sections with no matching questions so responders see exactly where attention is needed.\n\n- **[Create an assessment template category](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/sae-asmnt-template-category-create.md)**\n\nStarting with version 22.3.X, the **Category Role** field in the assessment template category form is replaced with the **Category Roles** field.\n\n\n- **[ServiceNow Otto® name announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n- **[Hide conditional questions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/sae-q-text-create.md)**\n\nConditional questions that don't meet their visibility criteria are now fully hidden from the assessment and are no longer displayed as **Skipped**. Respondents see only the questions relevant to them, reducing assessment fatigue and eliminating \"Skipped\" clutter.\n\n\n
\n\nSoftware Asset Management\n\n\n\n- **[Removal candidates tab replaced with the Reclamation tab in the License usage view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/sam-workspace-workbench.md)**\n\nThe **Reclamation** tab in the License usage view on the Software Asset Workspace presents a consolidated view of reclamation candidates across all publishers, SaaS integrations, installed software, and reconciliation flows.\n\n\n- **[Manage software models with clearer licensing terminology](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/software-model-fields.md)**\n\nUnderstand licensing scope at a glance from the renamed column in the Software Model \\[cmdb\\_software\\_product\\_model\\] table. The **License all installs accessed by clients** column is renamed to **License all installs**. The new name reflects that all installs meeting the software model's conditions are licensed, not only those tied to client access records.\n\n- **[Software Spend Detection Core UI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/spend-detection-sam-workspace.md)**\n\nThe Software Spend Detection feature is no longer available in the Core UI. Software Spend Detection is now accessible from the Software Asset Workspace under License operations. Existing imports and spend transactions created in the Core UI are now accessible from the Software Asset Workspace.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Delete button on the Product Workload Mapping form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/integrate-with-crowdstrike.md)**\n\nA **Delete** button is available on the Product Workload Mapping form for CrowdStrike integration profiles to enable you to delete existing workload-to-software model mappings directly from the integration profile.\n\n- **[Product workload mappings and breakdown data lists on the License operations view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/operations-workspace.md)**\n\nView the product workload mappings, usage, and consumption lists on the License operations view without requiring additional configuration.\n\n- **[Engineering application licenses, usages, and denials lists on the License operations view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/operations-workspace.md)**\n\nView engineering application lists including licenses, usages, concurrent usage, denials, and unidentified publisher integration map on the License operations view for quick access.\n\n\n- **[Troubleshoot button alongside the error message on the Integration profile form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/troubleshooting-saas-now-assist-sam.md)**\n\nThe **Troubleshoot** button is available for all SaaS integrations on the error message that is displayed when connection validation fails due to an error. When selected, the button triggers the generation of error summary and resolution guidance.\n\n\n- **[Granular configuration admin roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/sam-installed-components.md)**\n\nUse granular admin roles, such as sam\\_admin and sam\\_integrator, to complete administrative configuration tasks without requiring the full admin role. By using limited admin privileges that provide access to only certain tasks, you can help reduce security risks across your organization.\n\n\n
\n\nSource-to-Pay Operations Integrations\n\n\n\n- **[Source-to-Pay integration with SAP](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/source-to-pay-operations/source-to-pay-sap-integration.md)**\n - Enhanced integration to support data retrieval from SAP ECC, SAP OData, and SAP HANA RFC using the updated Buyer Group staging process.\n - Enhanced integration to support Read-Only security directives to strengthen data protection, applying required field-level changes in alignment with the Read-only field remediation guidelines to ensure compliance and consistency across integrations.\n - Updated entity naming convention from Department to Buyer Groups for improved standardization.\n- **[Source-to-Pay integration with SAP Ariba](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/source-to-pay-operations/source-to-pay-integration-sap-ariba.md)**\n - Enhanced integration to support fetch shipment details from SAP Ariba.\n - Updated entity naming convention from Department to Buyer Groups for improved standardization.\n- **[Source-to-Pay integration framework](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/source-to-pay-operations/source-to-pay-integration-framework.md)**\n - Enhanced the Purchase Requisition Line \\(PRL\\) outbound staging table to improve data completeness and consistency for outbound Purchase Requisition integrations.\n - Performance optimizations have been applied to the Purchase Order \\(PO\\) transform map to improve efficiency and scalability when processing high‑volume PO data.\n\n
\n\nStrategic Planning\n\n\n\n- **[Australia Patch 5](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-5.md)[Summarize demands with the demand summarization skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/summarize-demand-in-demand-workspace.md)**\n\nThe demand summary is generated in the **AI Overview** tab instead of the **Details** tab. The skill is set to trigger automatically, that is, the summary is generated on landing in this tab. Auto-generation is on by default and applies to demands in Submitted, Screening, Qualified, or Approved states. You can define the trigger to manually trigger as well, where users must select the **Summarize** button to generate the summary.\n\n- **[AI skills for Demand Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/similar-demand-identification-using-now-assist.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n- **[Access execution records from Portfolio Plans](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/access-demands-from-portfolio-plan-spw.md)**\n\nThe execution URL is updated on the planning item demand. New planning items demand will automatically use the new execution URL. The execution URLs on existing planning item demands continue to work but doesn't reflect the updated navigation. Run the **Update Demand Planning Item Execution URL** scheduled job to update the execution URL on the existing demands.\n\n- **[Components installed with Enterprise Agile Planning](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/components-installed-with-enterprise-agile-planning.md)**\n\nThe EAP role hierarchy is updated. The `sn_apw_advanced.eap_admin` role now contains `sn_apw_advanced.eap_scrum_master`, which in turn contains `sn_apw_advanced.eap_user`. The `sn_apw_advanced.eap_admin` role no longer contains `sn_apw_advanced.eap_user` directly.\n\nAs a result, the following actions require the `sn_apw_advanced.eap_scrum_master` role:\n\n - Changing the start date or the end date of an iteration.\n - Creating, editing, and deleting planning calendars and calendar spans.\nBecause `sn_apw_advanced.eap_admin` contains `sn_apw_advanced.eap_scrum_master`, users with the admin role keep access to these actions.\n\n\n- **[Demand summarization skill enhancements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/demand-summary-demand-classic.md)**\n\nThe demand summarization skill incorporates data from related entities when generating a summary. In addition to demand record fields, the summary includes insights from demand tasks, cost plans, monetary and non-monetary benefit plans, resource assignments, and work notes. The generated summary covers business requirements, timeline, risks, stakeholder comments, cost, effort, monetary and non-monetary benefits, and ROI.\n\n\n- **[Next Experience for Demand Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/demand-workspace.md)**\n - The Demands icon has been added to the Strategic Planning L1 menu to open the All Demands home page.\n - The **State** field on the **All Demands** page has been color-coded for each state value.\n - The **Playbook**, **Details**, and **Docs** tabs have been added to the L2 menu of each demand to clearly and consistently group information.\n - The **Details** tab has been added to add and manage demand information such as financials and resource assignments.\n - The **Playbook** tab has been added to define clear stages and guided activities to read and follow. Selecting the name of a stage or activity navigates you to that stage or activity in the playbook. The **Skip**, **Update**, and **Mark Complete** options have been added to the activities of the playbook.\n - The **Docs** tab has been added to view and manage the documentation on the demand.\n - If you have the AI Control Tower plugin installed and the investment type of the demand is set to artificial intelligence:\n - The **AI Associations** section in the Demand details is displayed. The following fields are included:\n - **Product**: Enables you to select the product or system that the demand relates to.\n - **Impacted AI systems**: Links the impacted AI systems with the demand. You can select existing AI systems from the list or remove systems that are no longer relevant.\n - The **AI Checkpoint** stage is added to the demand default playbook. This stage includes the **Product** and **Impacted AI systems** fields.\n - The **Create AI System** option is added to the **Details** page of a demand for users with the sn\\_ai\\_steward role.\n - [Australia Patch 5](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-5.md)The **Financials** grid is added to the navigation menu of a demand. It has options to create cost plans, monetary benefits plans, expense lines, and create and compare baselines.\n - The **Dashboards** menu item is added for demands, providing **Overview**, **Financials**, and **Data Quality** tabs.\n - The following items have been added to the demand form and are available if you have the identify similar records AI skill activated:\n - The **Identify similar demands** button, which identifies and displays similar demands.\n - The **Similar Demands** tab in **Details**, which displays the list of similar demand records identified by AI.\n - The **AI Overview** tab is added to the navigation menu of a demand. It generates a demand summary on landing if the skill trigger is set to automatic. If the trigger is set to manual, a **Summarize** button is available to generate the summary.\n- **[Changes to Target form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/target-form-egm.md)**\n\nThe following fields have been added to the Target form to support defining targets at multiple organizational levels.\n\n - **Assigned entity**\n - **Company**\n - **Business Unit**\n - **Department**\n - **Portfolio**\n - **Product model**\n - **Value stream**\n - **Initiative**\n - **Strategic Program**\n- **[Changes to Strategic Priority form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/strategic-priority-form.md)**\n\nThe **Status** field has been added to the Strategic Priority form, enabling you to set the status of a strategic priority as **None**, **Green**, **Yellow**, or **Red**.\n\n- **[Hierarchy and List views in Prioritization](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/managing-backlog-alignment-planner-workspace.md)**\n\nThe **Kanban** and **Hierarchy** views have been removed from the Prioritization page and are now available as separate tabs in the Planning page. This change improves navigation by consolidating all planning-related views in one place.\n\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n
\n\nSubscription Management\n\n\n\n- **[Support for Moveworks consumption tracking](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/monitoring-now-assist-usage.md)**\n\nStarting in Australia patch 7, Moveworks consumption can now be measured as part of your Assist meter, following the same subscription rules as other assist-based products. For more information about the timeline and required steps for integration, see [Moveworks Assist in Subscription Management: Rollout Timeline, Customer Actions & FAQ \\[KB3147691\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3147691) on the Now Support Knowledge Base.\n\n\n- **[Now Assist usage excludes demo data](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/monitoring-now-assist-usage.md)**\n\nDemonstration instances are excluded from the total Now Assist usage count to improve tracking of Assist consumption. The accrual time field displays when Now Assist data was last accrued.\n\n- **[Changes to Now Assist usage measurement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/monitoring-now-assist-usage.md)**\n\nNow Assist usage measurement is evolving. Update Subscription Management to version 6.1 or later on all instances to avoid mixed measurement states. For more information, see [Now Assist Usage - Overview & New Measurement Logic: January 2026 \\[KB2704710\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710) on the Now Support Knowledge Base.\n\n- **[Streamlined user-based subscription allocation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/managing-user-subscriptions-v2.md)**\n\nTo simplify the Subscription Management experience, the manual allocation workflow for user-based subscriptions has been removed for administrators who have never used it. Administrators who have manually allocated user-based subscriptions before can still make manual allocations.\n\n- **[Hidden user-based subscription allocations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/subscriptions-overview-v2.md)**\n\nTo help prevent inaccuracy when allocations aren't complete, allocation details for user-based subscriptions are now hidden from the Subscription Management overview. Contact your account executive for user-based subscription allocation details.\n\n\n
\n\nSupplier Lifecycle Operations\n\n\n\n- **[Verify bank account ownership using Relish](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/source-to-pay-operations/verify-banking-information.md)**\n\nWhen a banking details change request is assigned to a supplier manager and they start working on it, they can verify the details using Relish.\n\nBy default, bank validation checks only the bank routing number and address details. Relish also verifies the bank account number and account ownership information when bank account ownership validation is enabled.\n\n- **[Conduct bulk sanction screening using Relish](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/source-to-pay-operations/perform-bulk-sanction-screening.md)**\n\nWhen a sanction screening request for compliance verification is assigned to a supplier manager and they start working on it, they can verify the details using Relish.\n\nSupplier managers can conduct sanction screening for multiple suppliers simultaneously using the bulk sanction screening feature.\n\n- **[AI driven supplier onboarding using ServiceNow Otto for SLO](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/source-to-pay-operations/supplier-onboarding-agentic-workflow.md)**\n - Leverages Web search results to generate a supplier scorecard highlighting key strengths, positive indicators, and potential risk signals.\n - If Craft is configured, the workflow leverages the Craft integration to generate a comprehensive, normalized supplier scorecard and risk assessment. It provides a structured evaluation of the supplier’s overall profile and associated risk factors.\n - If Relish is integrated, the supplier's banking information is further validated and synchronized with Relish.\n\n
\n\nTable Builder\n\n\n\n- **[Field configuration in Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/field-parameters.md)**\n\nA new **Read Only Option** has been added to the dictionary tables \\(`sys_dictionary` and `sys_dictionary_override`\\). The existing **read\\_only** field is now locked and cannot be edited in the UI. Field behavior depends on the selected option. With **Display Read Only**, the field appears read-only but can still be updated through APIs. With **Strict Read Only**, the field can't be changed in the UI or by client scripts such as \\[`g_form.setValue()`\\]. A new system property,`glide.read_only.legacy_read_only_behavior`, controls whether the old behavior, where client scripts could override read-only settings, is retained.\n\n\n
\n\nTelecommunications Customer 360\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Products](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/telecom-media-technology/c360-products-card.md)**\n - Filter the list of sold products displayed by product characteristic values.\n - Modify configurations, suspend, resume, or disconnect one or more sold products and their services.\n- **[Customer history](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/telecom-media-technology/c360-inter-history-card.md)**\n\nThe **Interaction history** card has been renamed to **Customer history**. Phone interactions, chat messages, cases, contracts, work orders, and other activity types that have been configured are displayed.\n\n\n
\n\nTelecommunications Network Inventory\n\n\n\n- **[Now LLM service deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Network topology](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/telecom-network-inventory/using-network-topology.md)**\n\nTopology map icons updated to support dark theme colour contrast.\n\n\n- **[IP address management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/telecom-network-inventory/ip-address-management.md)**\n\nThe IP Pool menu and records are now labeled as IP Address Block throughout the Network Inventory Workspace and Service Operations Workspace.\n\n\n
\n\nTelecommunications Service Operations Management \\(TSOM\\)\n\n\n\n- **[SD-WAN Discovery connectors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/telecom-service-ops/sd-wan-data-model.md)**\n\nEnable comprehensive SD-WAN visibility by using new Telecom Discovery connectors. Standardize data processing through the SD-WAN Data Model integrated into the Telecom Discovery Builder Framework ETL pipeline.\n\n\n
\n\nTheme Builder\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Updated Editor page Global styles preview options](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/working-with-global-styles.md)**\n\nThe Global styles panel has been updated in the following ways:\n\n - The UI styles preview tab has been renamed to Abstract UI.\n - The Experience preview tab has been renamed to Experiences.\n - A Categories tab is now available allowing you to view groups of components by font or font size. This tab appears only when the Typography panel is open.\n- **[Global styles panel updated](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/working-with-global-styles.md)**\n\nThe Global styles panel has been updated in the following ways:\n\n - Global styles panel was relocated to simplify theme editing and provide a more consistent interface.\n - The Typography panel now features two dedicated tabs, Fonts and Sizes allowing you to manage typefaces and font scales independently. In addition, the panel supports a new structure for editing typography at a category level, bridging the previous gap between global and individual component styling.\n- **[Create a theme wizard updated](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/tb-create-theme.md)**\n\nThe existing create a theme wizard has been updated and streamlined in the following ways:\n\n - Primary and secondary colors are now selected in a single step.\n - The neutral color step has been removed. You can now choose a neutral color from the Global styles overview panel when needed.\n - The additional colors step has been removed. Additional brand colors can also be selected from the Global styles overview panel.\n - Custom font upload is now available directly from the font selector.\n - The final step is still the theme summary, with all editing options accessible directly from this page.\n\n
\n\nThird-party Risk Management\n\n\n\n- **[Australia Patch 5](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-5.md)**\n\nStarting 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.\n\n\n- **[Default AI model for issue recommendation skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/supporting-information-now-assist-tprm.md)**\n\nAfter 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.\n\n- **[Large language models on the ServiceNow AI Platform®](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/exploring-large-language-models.md)**\n\nThe 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.\n\n\n- **[Improved handling of skipped conditional questions in SAE assessments](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-sae-using.md)**\n\nAfter 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.\n\n- **[Comments field in the third‑party portal saves when you leave the field](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/vendor-portal.md)**\n\nAfter 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.\n\n- **[Issue indicators in the third-party portal shown only after submission](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/vendor-portal.md)**\n\nAfter 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.\n\n\n- **[Consolidated assessment email notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/set_sys_props_for_email.md)**\n\nAfter 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.\n\n- **[Assessment count mechanism updated in the third-party portal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/vendor-portal.md)**\n\nAfter 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.\n\n- **[Inactive metrics excluded when copying assessment responses](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-assessing-tpr.md)**\n\nAfter 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.\n\n- **[Type of ICT services changes cascade to supply chain in DORA reporting](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-drtp-reg-contract.md)**\n\nAfter 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.\n\n- **[Duplicate contractual arrangements detected and warned in DORA Register of Information](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-drtp-reg-contract.md)**\n\nAfter 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.\n\n- **[Duplicate supply chain rows warned during DORA CSV package download](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-drtp-roi-packages.md)**\n\nAfter 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.\n\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n- **[Fields added to Create New Excel download/upload request form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-create-report-aggregate-expenses.md)**\n\nAfter 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.\n\n- **[TPRM Unified content management page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-ws-ucm-page.md)**\n\nAfter 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.\n\n\n- **[Simplified third-party element process](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/tprm-workflow-in-workspace.md)**\n\nAfter 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.\n\n\n
\n\nThreat Intelligence Security Center\n\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[TISC Library Repository](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/tisc-ioc.md)**\n\nEnhanced Threat Intelligence Library list views by grouping observables, indicators, threat entities, RSS feed, and vulnerability artifacts into appropriate categories for improved navigation.\n\n\n- **[Create Vulnerability Assessment from a Vulnerability](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/tisc-vul-assess.md)**\n\nIntroduced a new button **Create Vulnerability Assessment** to conduct a vulnerability assessment for a specific vulnerability.\n\n\n
\n\nUI Builder\n\n\n\n- **[Use pages across experiences](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/use-across-pages.md)**\n\nShare and reuse pages across workspaces without switching contexts or rebuilding content to help save time and simplify maintenance.\n\n\n
\n\nUnified Security Exposure Management \\(USEM\\)\n\n\n\n- **Risk rating options are no longer part of exception or deferral requests**\n\nChanging a risk rating is no longer available from the Request Exception dialog, or from the Bulk Edit dialog by selecting **Mitigating Control in Place** as a deferral reason. Risk rating and compensating control fields have been removed from both. Use **Modify risk** or **Request risk modification**, according to your role, to change a risk rating instead for individual records or in bulk.\n\n\n- **[ITSM Advanced plugin required for change request options in the Remediation view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/sem-ws-CRs.md)**\n\nUse the **Create Change** and **Add to existing change** options in the Remediation view of the Security Exposure Management Workspace to manage remediation tasks through Change Management. These options now require the ITSM Advanced plugin to be active on your instance. If you have migrated to an ITSM AI Native SKU without ITSM Advanced, upgrade to ITSM Advanced SKU to restore access to these options.\n\n- **[Create remediation tasks directly from the Security Exposure Management Workspace list view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/sem-workspace-list-page.md)**\n\nRemediation owners can now create remediation tasks directly from list views in the Security Exposure Management Workspace by selecting the Create Remediation Task action from the list toolbar in the Assigned to me and Assigned to my group views for host vulnerable items, application vulnerable items, container vulnerable items, and configuration test results. Previously, this action was available only for managers.\n\n\n- **[Improved vulnerability assessment workflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/vr-ws-vuln-assessment.md)**\n - CI filtering for vulnerability assessments: You can now filter which configuration items are included in a vulnerability assessment using a condition builder.\n - Business Application population on AVITs: AVITs created from SBOM assessment results now include Business Application information, helping you understand application impact and prioritize remediation.\n - Priority roll‑down from vulnerability assessments: Updates to the priority of a vulnerability assessment now automatically roll down to associated VITs and AVITs, ensuring consistent prioritization based on the highest severity.\n- **[Remediation task rule execution mode](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/sem-grouping-multiple-findings-remediation-tasks-processing.md)**\n\nYou can now choose how remediation task rules are evaluated during ingestion. The new Match First execution mode evaluates rules sequentially and applies only the first matching rule, assigning each finding to exactly one remediation task. The default Match All mode continues to evaluate all applicable rules.\n\n- **[Enhanced Compensatory controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/requesting-approving-risk-reduction.md)**\n\nWhen new vulnerable items are ingested and associated with a remediation task that already has an approved compensating control, the reduced risk rating is now automatically inherited by those new vulnerable items.\n\n\n
\n\nVirtual Agent\n\n\n\n- **[Enable additional chat features](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/additional-chat-features.md)**\n\nThe **Prioritize AI agents during skills discovery** option is available when configuring additional chat features. Because all assistants now use agentic orchestration by default, AI agent skills are available during skills discovery. Turning on this option gives AI agents priority over other assets \\(such as knowledge bases and Q&A modules\\) when the assistant discovers skills. If your assistant has overlapping skills, for example, a knowledge base article and an AI agent that both answer the same question, this setting lets you decide which one is prioritized, so you can steer users toward the AI agent experience instead of a static article.\n\n- **[ServiceNow® Otto for Virtual Agent system properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/nava-sys-props.md)**\n\nThe **sn\\_nowassist\\_va.assistant\\_personalization** system property is removed from the admin experience. This property previously let admins show or hide chat personalization options \\(agent persona, tone, and response length\\) when [branding an assistant](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/brand-assistant.md). By default, all settings are shown.\n\n\n- **[Updated Otto processing animation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/nava-integrated-chat.md)**\n\nView an updated Otto processing animation.\n\n- ****\n\nRole-based configuration is no longer stored or managed within Assistant Designer.\n\n\n- **[Upload files improvements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/upload-documents-na-va.md)**\n\nUpload up to 10 files or 50 MB for the following file types: PDF native, PDF OCR, Word, PPTX, Excel, CSV, TXT, JPEG, PNG for premium chat in ServiceNow Otto for Virtual Agent and Otto panel.\n\n\n- **[Refresh to the organization chart user interface](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/nava-integrated-chat.md)**\n\nThe org chart's user interface was updated for premium chat in ServiceNow Otto for Virtual Agent and ServiceNow Otto panel.\n\n- **[Brand and personalize an assistant](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/brand-assistant.md)**\n\nIn **Assistant Designer** > **Assistants** > **Branding**, the standard chat and enhanced chat sections are condensed into one section.\n\n\n- **[Now Assist > ServiceNow Otto® announcement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/sn-ai-implementation-landing.md)**\n\nServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n\n- **[Assistant Designer Asset library](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/conversational-interfaces/vad-topics-page.md): actions for this row icon**\n\nThe tooltip for the **Discoverable** and **Visible** options now explains that Setup topics can't be discoverable or visible, as they aren't editable by users. The Live Agent topic is excepted.\n\n\n
\n\nVisa Spoke\n\n\n\n- **Updated response field mapping for dispute response details**\n\nUpdated response field mapping for the following spoke actions so FSO can parse and surface the additional fields Visa introduced under the Reference Doc Summary tab's flexible schema for revision 26.2, including document-type, billing- and shipping-address, and travel-itinerary \\(outbound/inbound passenger name and departure/arrival date\\) fields for compelling-evidence documentation.\n\n - `Look up Dispute Response Details Response Parser`\n - `Look up Dispute Pre Arbitration Details Response Parser`\n - `Look up Dispute Pre Arbitration Response Details Response Parser`\n- **Updated case, collaboration, and related Spoke actions**\n\nUpdated the following spoke actions for IES corrections:\n\n - `Look up GMFP Details Response Parser` to correct the case stage/state description field length \\(widened to String \\(100\\)\\)\nAlso updated `Look up Dispute Financial Details Response Parser` to return the Virtual Account Number, Virtual Card Code, and Funding Account Number fields.\n\n\n- **[Card data security updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/visa-spoke.md)**\n\nThe following spoke actions have been updated to support integration with the Card data security application:\n\n - Look up Associated Transaction List\n - Look up Image\n - Look up Report Output\n - Download and Attach Image\n- **[VROL release 26.1 updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/visa-spoke.md)**\n\nUpdated the following Visa Spoke actions to align with VROL release 26.1 revision changes. These changes support dispute agents and admins in processing disputes accurately:\n\n - Submit Exception Request Builder\n - Submit Fraud Bundle Dispute Questionnaire\n - Look up Dispute Financial Details Request Builder\n - Look up Dispute Financial Details Response Parser\n - Submit Fraud Report Request Builder\n - Look up Fraud Report Details Response Parser\n - Look up Fraud Report Details Request Builder\n - Look up Transaction Details Request Builder\n - Look up Dispute Details Request Builder\n - Look up Dispute Details Response Parser\n - Look up Dispute Filing Details Response Parser\n - Look up Transaction Details Response Parser\n - Look up Transaction Details from Case Response Parser\n - Look up All Transaction Details Response Parser\n - Create Dispute Pre Arbitration Response\n - Look up Dispute Pre Arbitration Details Request Builder\n - Look up Dispute Pre Arbitration Response Details Request Builder\n - Look up Dispute Pre Arbitration Details Response Parser\n - Look up Dispute Response Details Request Builder\n - Submit Dispute Questionnaire\n - Look up Dispute Pre Arbitration Response Details Response Parser\n - Look up Dispute Response Details Response Parser\n - Initiate Dispute from Transaction or Case\n - Create Dispute Pre Arbitration\n\n
\n\nVulnerability Response\n\n\n\n- **Risk rating options are no longer part of exception or deferral requests**\n\nChanging a risk rating is no longer available from the Request Exception dialog, or from the Bulk Edit dialog by selecting **Mitigating Control in Place** as a deferral reason. Risk rating and compensating control fields have been removed from both. Use **Modify risk** or **Request risk modification**, according to your role, to change a risk rating instead for individual records or in bulk.\n\n\n- **Vulnerability Response assignment rules**\n\nThe sn\\_vul.rerun\\_task\\_rules system property for rerunning assignment rules was changed to sn\\_sec\\_rem.rerun\\_task\\_rules. Users must activate this property \\(set to 'true'\\) to rerun assignment rules.\n\n- **[Improved vulnerability assessment workflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/vr-ws-vuln-assessment.md)**\n - CI filtering for vulnerability assessments: You can now filter which configuration items are included in a vulnerability assessment using a condition builder.\n - Business Application population on AVITs: AVITs created from SBOM assessment results now include Business Application information, helping you understand application impact and prioritize remediation.\n - Priority roll‑down from vulnerability assessments: Updates to the priority of a vulnerability assessment now automatically roll down to associated VITs and AVITs, ensuring consistent prioritization based on the highest severity.\n- **[Remediation task rule execution mode](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/sem-grouping-multiple-findings-remediation-tasks-processing.md)**\n\nYou can now choose how remediation task rules are evaluated during ingestion. The new Match First execution mode evaluates rules sequentially and applies only the first matching rule, assigning each finding to exactly one remediation task. The default Match All mode continues to evaluate all applicable rules.\n\n- **[Enhanced Compensatory controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/requesting-approving-risk-reduction.md)**\n\nWhen new vulnerable items are ingested and associated with a remediation task that already has an approved compensating control, the reduced risk rating is now automatically inherited by those new vulnerable items.\n\n\n
\n\nWorkforce Optimization for CSM\n\n\n\n- **[Manager Workspace landing page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/customer-service-management/csm-configurable-manager-workspace-dashboards-new.md)**\n\nThe following UI components have been added on the Manger Dashboard:\n\n - The dashboard includes new AI‑powered widgets — Sentiment Analysis,Trending Topics, and Auto QA\n - **Help requested** can be viewed on the **Manager Workspace landing page** and in **Conversation Monitoring** list view.\n - The **Help requested** include different channels, such as **Chat**, **Email**, **Messaging**, **Phone** and **Video**.\n\n
\n\nZero Copy Connector for ERP\n\n\n\n- ****\n\n[Building flows to read or update the ERP system](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/erp-canvas-build-flow-operation.md)Required and optional fields now display correctly in the Use ERP Data action when nested structures share a name.\n\n\n- **[Simplified process for adding a REST entity to a model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/add-a-rest-entity-to-a-model-operation.md)**\n\nAfter you specify the REST service to use, the endpoint and return type are added automatically.\n\n\n- **[Improved ETL data extractions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/set-up-erp-integration-connection.md)**\n\nThe extract, transform, load \\(ETL\\) process uses script includes instead of Flow Designer.\n\n- **[Zero Copy Connector for ERP Data Products renamed to Content Packs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/erp-canvas-available-content-packs.md)**\n\nAll ERP Data Products, such as Enterprise Data Foundation, Quote to Cash, and Source to Settle, are renamed to Content Packs.\n\n- **[Zero Copy Connector for ERP Enterprise Data Foundation content pack](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/erp-canvas-enterprise-data-foundation-content-pack.md)**\n\nAdditional models, including Vendor Bank Details, Vendor Location Details, and Vendor Contact Details, are added to the content pack for use when interacting with an SAP system.\n\n\n
\n\nZero Copy Connectors\n\n\n\n- **[Australia Patch 6](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-6.md)**\n - [MySQL](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/mysql-zcc.md): The MySQL connector moved from the Community connector list to the Primary connector list. This connector is available with a Preview label, indicating that performance enhancements are ongoing.\n - [PostgreSQL](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/postgresql-zcc.md): The PostgreSQL connector moved from the Community connector list to the Primary connector list.\n - Authentication options for MySQL and PostgreSQL connections: The connection form for MySQL and PostgreSQL now includes additional authentication drop-down options, including AWS IAM and OAuth, alongside basic authentication.\n\n- **[Australia Patch 2](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-2.md)**\n - [Teradata](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/teradata-zcc.md): The Teradata connector now supports Bearer Token and OAuth authentication methods.\n - [Apache Iceberg](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/apache-iceberg-primary-zcc.md): The Apache Iceberg connector now supports S3-compatible object storage systems.\n\n- **[Australia Patch 1](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-1.md)**\n - [Amazon S3 Tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/amazon-s3-tables-zcc.md)\n - [Apache Iceberg](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/apache-iceberg-primary-zcc.md)\n\n- **[Apache Iceberg primary connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/apache-iceberg-primary-zcc.md)**\n\nThe Apache Iceberg connector is now certified as a primary connector.\n\n- **[Primary connectors in preview](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/primary-connectors-zcc.md)**\n\nPrimary connectors that are still being enhanced to include all planned functionality are now marked with a Preview label. These connectors are fully supported by ServiceNow®.\n\n\n- **[New application name](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/zero-copy-connectors.md)**\n\nWorkflow Data Fabric Hub is now Zero Copy Connector Hub.\n\n- **[Australia Patch 1](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-1.md)**\n\n[New connector package options](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/zero-copy-connectors.md)When installing Zero Copy Connectors, you can include primary connectors only by selecting Zero Copy Connectors Primary \\(sn\\_zcc\\_primary\\). Alternatively, select Zero Copy Connectors \\(sn\\_data\\_fabric\\_zcc\\) to include both primary and community connectors.\n\n- **[Australia Patch 6](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-6.md)**\n - Authenticate to [Databricks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/databricks-zcc.md) and [Snowflake](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/snowflake-zcc.md) using your own credentials with personal authentication support.\n - Retrieve real-time metadata and data from REST-enabled systems without copying or duplicating the data. This release adds [REST connectors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/rest-connectors.md) for [Oracle HCM \\(Discovery\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/oracle-hcm-discovery-zcc.md) and [Acumatica](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/acumatica-zcc.md).\n - [MySQL](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/mysql-zcc.md) and [PostgreSQL](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/postgresql-zcc.md) connectors moved from Community connectors to Primary connectors.\n\n
**Parent Topic:**[Release notes summaries for Australia features](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/release-notes-summaries.md)\n\n"}}