| AI Control Tower |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| AI Search |
- Yokohama Patch 11
- Now Assist Multi-Content Response Genius Results
- If 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.
- Search Suggestions
- Search 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.
- Gain insights into search behavior with a refreshed and updated Search Preview UI.
- Preview 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.
- Yokohama Patch 6
- Consumer-grade search experience for search portals
- The search results page for search portals has been revised to offer a more intuitive and consistent experience. Navigation tabs have been replaced with source facet buckets. All search results now open in a new browser tab,
preserving your search in the existing browser tab. Facet buckets now show minimum search result counts, reflecting results removed by late binding content security. Search terms are no longer highlighted in search
results.
- Consumer-grade search experience for global search and workspace search
- The search results page for global search and workspace search has been revised to offer a more intuitive and consistent experience. Navigation tabs have been replaced with source facet buckets. All search results now open
in a new browser tab, preserving your search in the existing browser tab. Facet buckets now show minimum search result counts, reflecting results removed by late binding content security. A new
glide.ui.ais.show_all_facets system property enables you to display facets from all sources when no source is selected. (The default behavior is to hide facets until a source is selected.) Search terms
are no longer highlighted in search results.
- Sort facet buckets alphabetically
- Override the default sorting of facet buckets by their search result counts and display them sorted alphabetically by their labels.
- Improved display for grouped attachment search results
- When grouped with their parent search results, attachment search results now appear in collapsed form to save space. If a parent search result includes more than three grouped attachments, you can use the new Show
more and Show less links to control how many attachments are visible.
|
| API |
Table 1. Changed scoped classes in Yokohama
| Class |
Methods |
|
- convertToPDF()
- convertToPDFWithHeaderFooter()
New properties, glide.pdf.url.whitelisting.enabled and com.snc.pdf.whitelisted_urls, have been added to ensure whether external URLs provided should be rendered in the PDF output.
A new property, accessibilityEnabled, has been added for PDF accessibility support.
|
Table 2. Changed global classes in Yokohama
| Class |
Methods |
|
- convertToPDF()
- convertToPDFWithHeaderFooter()
New properties, glide.pdf.url.whitelisting.enabled and com.snc.pdf.whitelisted_urls, have been added to ensure whether external URLs provided should be rendered in the PDF output.
A new property, accessibilityEnabled, has been added for PDF accessibility support.
|
Table 3. Changed REST APIs in Yokohama
| API |
Endpoints |
|
POST /now/attachment/file: A new parameter, creation_time, can be used to capture attachment creation times when the Now Mobile app is offline and the attachment is uploaded to a record at a later time. |
Table 4. Changed scoped classes in the ServiceNow Store
| Application |
App Version |
Class |
Methods |
| Lead to Cash Core |
V1.4 |
|
Enhanced the performance of the Commit Instance API to improve number generation for the number field:
- effect(): The _records_count return object is added to provide details about newly inserted records for a particular table, such as the table name and number of inserted records.
- commitInstance(): A new additional parameter, useNumberGenerator, is added to optionally generate and apply sys_ids to new table records in bulk.
|
| ATF Test Generator and Cloud Runner |
2.7.2 |
|
Added the testSuite parameter allowing you to set the name of the new test suite that is created during test generation. |
Table 5. Changed client classes in the ServiceNow Store
| Application |
App Version |
Class |
Methods |
| Customer Service Management |
v1.2 |
|
subscribe(): Added new events
- openframe_wrap_up_submitted
- openframe_heart_beat
|
| Mobile SDK |
v2.9.0 |
|
Updated available chat UI color defaults. |
| Mobile SDK |
v2.9.0 |
|
Updated available web view UI color defaults. |
| Mobile SDK |
v2.9.0 |
|
Updated available chat UI color defaults. |
| Mobile SDK |
v2.9.0 |
|
Updated available web view UI color defaults. |
Table 6. Changed global classes in the ServiceNow Store
| Application |
App Version |
Class |
Methods |
| ATF Test Generator and Cloud Runner |
2.7.2 |
|
Added the testSuite parameter allowing you to set the name of the new test suite that is created during test generation. |
Table 7. Changed REST APIs in the ServiceNow Store
| Application |
App Version |
API |
Endpoints |
| Accounts Payable Operations |
v2.0.0 |
|
Add properties supporting bill-to address information.
- POST /sn_spend_intg/ap_invoice/cxml
- POST /sn_spend_intg/ap_invoice/json
|
| ATF Test Generator and Cloud Runner |
2.7.2 |
|
Added the testSuite parameter allowing you to set the name of the new test suite that is created during test generation. |
| Order Management |
v11.3.0 |
|
The productSpecification request parameter has changed from required to optional.
- PATCH /sn_ind_tmt_orm/order/productOrder/{id}
- PATCH /sn_ind_tmt_orm/productorder/{id}
- POST /sn_ind_tmt_orm/order/productOrder
- POST /sn_ind_tmt_orm/productorder
|
| Order Management
|
v12.5.0 |
|
The productSpecification request parameter has changed from required to optional. These endpoints now retrieve all product inventory records. In prior releases, product inventory records without a
specified product specification weren't returned.
- POST /api/sn_prd_invt_/product
- GET /api/sn_prd_invt_/product
- GET /api/sn_prd_invt_/product/{id}
|
| Product Catalog |
v14.1.0 |
|
The ability to specify product bundles has been added to the following endpoints:
- GET /sn_tmf_api/ catalogmanagement/catalog
- GET /sn_tmf_api/ catalogmanagement/catalog/{id}
- GET /sn_tmf_api/ catalogmanagement/productOffering
- GET /sn_tmf_api/ catalogmanagement/productOffering/{id}
- PATCH /sn_tmf_api/ catalogmanagement/productOffering/{id}
- POST /sn_tmf_api/ catalogmanagement/productOffering
- GET /sn_tmf_api/ catalogmanagement/productSpecification
- GET/sn_tmf_api/ catalogmanagement/productSpecification/{id}
- PATCH /sn_tmf_api/ catalogmanagement/productSpecification/{id}
- POST /sn_tmf_api/ catalogmanagement/productSpecification
|
|
| Accounts Payable Operations |
- Work with invoices
-
- Invoice line statuses are updated as:
- PO matching error to Mapping error
- PO matching completed to Mapping complete
- Matching error to Mapping error
- Review mapping
- Invoice ingestion process when Document Intelligence is unavailable
- Accounts Payable Operations integration with Document Intelligence enables AP admin to create invoice manually when DocIntel is down. The capture invoice details activity card displays the Create invoice option.
|
| Adoption Services |
- Guided Setup
- Assign and transfer Guided Setup tasks to relevant users, for execution. This capability requires admin roles.
- Set Guided Setup steps as mandatory by disabling the skip action.
- You can now run the Guided Setup player or builder multiple times.
- Select the multi-run feature while you’re configuring and executing the tasks multiple times.
- Help Center
- Navigate to What's New within the Help Center panel across all experiences, including Core UI. Starting in the Yokohama release, configuration support for this new feature is available in classic and custom pages.
- This feature isn’t supported for non-Polaris users.
- Embedded Help
- Import non-English content without overriding the last uploaded language content.
- Guided Tours
- Create, edit, or delete Guided Tours from any scoped application including ServiceNow AI Platform.
|
| Advanced AI Search Management Tools | |
| Advanced Risk | |
| Agent Client Collector |
- Explore metrics with Metric Explorer independent of Agent Client Collector Monitoring
- Starting in version 4.1.0, view and monitor metric data with Metric Explorer, even if you have not installed Agent Client Collector Monitoring.
- Starting in version 1.1.0, ACC for Visibility has been renamed as Kubernetes Visibility Agent and consists only of what is currently CNO for Visibility. The term CNO for Visibility has been deprecated and replaced with Kubernetes Visibility Agent. All other ACC for Visibility functions are now part of Agent Client Collector for Visibility - Content.
|
| Agent experience for CSM |
- Form template enhancements
- Use the following form template enhancements to create or edit templates as needed:
- The Templates tab in the configurable side panel displays larger template cards with the template name and an expanded description. Users can view different lists of templates, mark their
favorites, and sort templates either alphabetically or by last used.
- The template form displays template fields in a clearly labeled form section and displays the line numbers and headings for each template line to improve readability
- The template tab header displays "Edit template" when a user opens a template in edit mode.
- Front-line case page integration with knowledge guidance
- Enable agents to attach and add links to knowledge articles in comments, work notes, or emails by using modeless dialogs.
- Resurface special handling notes
- Display the special handling notes for a case at any time by selecting Special handling notes from the More actions menu on the case record action bar.
- Customer Central application moved from family to store release
- Starting with the Yokohama release, the Customer Central application (com.sn_csm_customer_central) has moved to the ServiceNow Store. Any new enhancements to this application are delivered through the Customer Central store app.
- Customer Activity Guided Setup now accessible from a new location
- Use the following updates in Guided Setup to enhance navigation and access customer history configurations:
- Access the Customer Activity Guided Setup from .
- View Activity Contexts, Activity Types, Activity Groups, and Activity Type Templates within Guided Setup. You can also access them in the menu by navigating to .
- Customer Activity has been renamed to Customer History, maintaining the same functionality.
- Access the Business Rule in the Activity Feed where it is now listed independently alongside Activity Types, Activity Groups, and Activity Type Templates for improved accessibility. Previously, it was nested under
Activity Types.
- Front-line case page lookup component
- The Front-line case page includes the following enhancements:
- Includes the Consumer lookup component.
- Uses advanced search to look up contacts and consumers.
- Contact and consumer record cards can be collapsed to display more record space.
- Action bar layout
- The following interaction record pages include an action bar with a single action layout:
- CSM Interaction record page
- CSM voice interaction record page
- Comment and Work note modeless dialogs
- Create and use form templates that add content to the Additional comments and Work notes fields on a case record. Automatically display a modeless dialog that includes the
content from the form template and then post that content to the activity stream.
- Front-line case page contextual side panel
- The Record Information tab in the contextual side panel includes the Overview and Active SLA cards. The contact card and timeline card have been removed to improve the page load time.
- Recommended Actions AI search replaces Agent Assist
- Recommended Actions AI search replaces Agent Assist in the contextual side panel for the following record pages included with the CSM Configurable Workspace:
- CSM default record page
- Front-line case page
- CSM Interaction record page (for type = Chat, Video, Walkup, Email)
- Use the following features to provide agents real-time updates and customer history details:
- Automatically refresh the Customer History component when account, contact, or consumer details change.
- Prompt agents to add missing account or contact details instead of leaving fields empty.
- Display an empty component until an agent links a contact using the lookup component, then show the contact's details.
- Enables agent to view updated customer information directly in Customer History on the Front-line Case page.
|
| Application Manager |
- Unlicensed application information
- In 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.
|
| Audit Management |
- Reflow for Configurable Workspace
- The Audit Management
configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality.
|
| Authentication | |
| Business Continuity Management |
- You can use the latest assessment template to conduct the Business Impact Analysis (BIA).
|
| Case management for CSM |
- Process mining
- Use the process mining enhancements to improve processes as needed:
- Removed the viewer role from all records in the Process Mining Content Pack for Customer Service Management (CSM).
- Set process configurations as read-only templates, deletable only by a process mining administrator. You can enable customers to copy the template or import specific parts into their custom
configuration.
- Case lines and workflows
- The Case Line table (sn_case_line) includes the Install base and Asset reference fields. These fields display information based on the selected account and product.
|
| Code Signing |
- Enhancements to the guardrails check
- The Code Signing Guardrails check has been improved to enhance signature verification, resulting in more secure workflows. In addition, multiple optimizations have been implemented to improve the performance
benchmarks of the Guardrails scan, and log files now feature a more intuitive naming convention, which simplifies file identification within your system.
- Generate update sets with a maximum size of 10,000 records
- Code Signing now enforces limits on large update sets to improve the user experience. The maximum size for an update set is 10,000 records.
- Naming updates for trusted and production instances
- The trusted non-production instance has been renamed to trusted instance, and the protected production instance has been renamed to protected instance. These naming updates have been made to better align with
customer usage.
|
| Collaborative Work Management |
- Improved user experience for adding hyperlinks in Docs
- Insert hyperlinks in a Doc easily and quickly through the formatting toolbar, inline commands, or by pasting a copied link. The pasted URL can be converted into a hyperlink by pressing the Space or Enter key and edited using
the inline edit modal.
- Improved user experience for copying links of Boards
-
Ensure that your team sees the same data as you while sharing links of your Boards through the Copy link action, which now accesses the linked workspace showing the view in which the Board is
displayed to you regardless of the user's view settings.
- Redirection to the CWM task from notification emails
- Access task details when you open a task from an assignment email from CWM in a new browser tab in the context of its Board rather than being directed to the workspace home page.
- Redirection to the specific doc pages from notification emails
- Access the specific Doc page that you are @-mentioned in by selecting View Doc in the notification email, eliminating the need to look through multiple pages in the Doc.
- Reflow for Configurable Workspace
-
The CWM workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality.
|
| Common Core |
- Column Organization
- You can select and reorder columns when adding a table into your template by using the Document designer
Microsoft Word add-in. You can now organize your content better to meet your reporting needs.
- You can add up to 20 columns in a table and content block by using the Document designer application. You now have more flexibility with customizing your table and content block to meet your reporting needs.
- Yokohama Patch 11
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
|
| Compliance Case Management |
- Roles updated for smart assessment
- The following roles in Compliance Case Management have been updated with respect to smart assessments.
- sn_comp_case.compliance_case_admin
- sn_comp_case.compliance_case_analyst
- sn_comp_case.compliance_case_business_user
- sn_comp_case.compliance_case_manager
- Reflow for Configurable Workspace
- The Compliance Management configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality.
|
| Configuration Management Database (CMDB) |
- Access changes for the sn_cmdb_editor and sn_cmdb_admin user roles
-
- Starting with Yokohama Patch 4 (zbooted or upgraded), access has been reduced for the sn_cmdb_editor (CMDB Editor) and the sn_cmdb_admin (CMDB Admin) user roles which are used in CMDB Workspace. The sn_cmdb_editor and sn_cmdb_admin user roles no longer have create, update, or delete access to records in the Configuration Item [cmdb_ci] class.
- Starting with Yokohama Patch 6 (zbooted or upgraded), you must manually run the scheduled job 'Remove CMDB Roles from ITIL roles and Add CUD access to sn_cmdb_admin/sn_cmdb_editor roles to
configure the sn_cmdb_admin and the sn_cmdb_editor user roles with the permissions that are necessary for performing some CMDB Workspace tasks.
This scheduled job modifies user roles as follows:
- CMDB Workspace v6.3
-
- Apply the filters that were previously available only to the coverage charts to all charts in the Discovery sources tile in the CMDB 360 dashboard. For example, you can filter out non-CMDB tables or
include records only from principal classes. For more information, see CMDB 360 experience in CMDB Workspace.
- Use a condition builder or a custom script to narrow down the list of de-duplication tasks that are assigned to a template. For more information, see Create a de-duplication template.
- Use the new Allow empty field values option to allow or disallow certification of empty value fields when creating a certification policy type in CMDB Data Manager. For more
information, see Create a CMDB Data Manager policy in CMDB Workspace.
- CMDB Workspace v6.4
- You can now use dot-walking when setting assignments for the User Field or User Group Field options for CMDB Data Manager policies (such as Certification). Also, when converting legacy certification
schedules into Data Manager Certification policies, existing dot-walking settings are preserved. For more information, see Create a CMDB Data Manager policy in CMDB Workspace.
- CMDB Workspace v7.4
- In the CMDB Workspace version 7.4, you can now do the following tasks:
- Manually create a CI in CMDB Workspace that complies with its class identification rule and other class requirements, and is tested for uniqueness in CMDB, to help ensure that the CI is valid and maintains the integrity of CMDB. For more information, see Create a CI manually in CMDB Workspace.
-
Set the CMDB Health dashboard to use the legacy methods to calculate the completeness, correctness, and compliance KPIs. That legacy calculation method relies on settings of proportional
weights of metrics within the aggregated score of KPIs and was used up until the Washington DC release. By default, those weights aren’t used in the calculations of KPI scores.
Also, the CMDB Health dashboard now shows the overall score, which by default, is a simple average of the aggregated scores of the completeness, correctness, and compliance KPIs.
- CMDB Workspace v7.5
- In the CMDB Workspace version 7.5, you can now do the following tasks:
- Delete CMDB Data Manager retirement definitions in CMDB Workspace (other than the cmdb_ci retirement definition). For more information, see Delete a CMDB Data Manager retirement definition.
- Configure a CMDB Data Manager certification policy to disallow reviewers, to update fields' value while reviewing CIs in a certification task. Administrators can clear the Allow
updates to field values option to prevent reviewers from updating non-compliant field values into compliance, resulting in rejecting those CIs. For more information, see Create a CMDB Data Manager policy in CMDB Workspace.
- Schedule a de-duplication template for daily, weekly, monthly, or periodic runs for continuous remediation of duplicate CIs. For more information, see Schedule a de-duplication template.
- Receive notifications from CMDB Data Manager about certification and attestation tasks, that are incomplete or overdue. For more information, see Components related to CMDB Data Manager.
- Review and process tasks of your direct reports and of members of any user group that you manage. For more information about accessing these tasks in CMDB Data Manager, see My Work view in CMDB Workspace.
- Reject a CMDB Data Manager life-cycle task in CMDB Workspace. For more information, see Review CMDB Data Manager tasks in CMDB Workspace.
- Use the Create CI experience with a preset class when drilling down a class in the CI Summary chart on the Home view of CMDB Workspace. For more information about creating CIs manually while applying
IRE processes, see Create a CI manually in CMDB Workspace.
- Update to the Walk stage reports on the CSDM Data Foundations dashboard
- The Technical Service Offerings with Support Group or Change Group report now includes data that meets the sys_class _name = offering
parameter.
- Table label changes
- The following table labels have changed:
- The label for the cmdb_ci_service_auto table is now Service Instance instead of Application Service.
- The label for the cmdb_ci_service_technical table is now Technology management service instead of Technical service.
- Class descriptions showing in the user interface
- The descriptions for the base system classes are now integrated into CI Class Manager and appear in the Description field, on the Basic Info page for a class.
- Reflow for configurable workspace
- The CMDB
configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality.
|
| Continuous Authorization and Monitoring |
- Generate the OSCAL SSP model of an authorization package
- Export the SSP model of an authorization package in the OSCAL format. The exported report contains only the control objectives linked to the authorization package and their additional information, such as inherited controls
and the hierarchy of the control objectives.
- Generate ATO artifacts in Microsoft Word and HTML templates
- Use the Document designer plugin (com.sn_grc_doc_design) to create report templates in Microsoft Word. A new property module has been introduced to select the template type as a Microsoft Word template in addition to an HTML template.
|
| Contract Management Pro |
- Select contract type while initiating a third-party contract
- In the Initiate contract window, the Type field appears when you select the Third party paper option. You can specify whether the contract request is for a single contract or
multiple contracts.
If you select Single contract, a Contract type field appears where you can define the type of contract document. This field isn’t available when you select
Multiple contracts.
- Classify contract requests as a single or multiple contracts type based on selected documents
- When you're creating a third-party contract review request from Employee Portal, you can now select a single contract document to classify it as a single contract type. By selecting multiple contract documents, you can classify them as a multiple contracts type. The
Type field in the contract request reflects this selection by displaying either Single contract or Multiple contracts.
- Use scripts to define additional conditions for a clause variation
- You can now define the clause conditions on the fields and variables of a table that isn’t directly linked to the contract template table. The Advanced script check box in the Clause Variation form
enables you to add custom logic to determine when a clause variation is used in a contract.
- Configure tables in a contract template to append or add fields from related tables
- You can now use scripts to insert additional data from the related table fields into the dynamic tables of a contract. The Advanced script check box in the Column Mapping form enables you to configure
dynamic tables in a contract template to display additional data from related table fields by appending it to existing columns or adding it as new columns.
- Contract Management Pro configurations are available on the Contract Request table
-
You can now set up the following Contract Management Pro configurations directly on the Contract Request [sn_cm_core_contract_request] table to centralize the configuration on a single table and improve consistency and reusability
across business units:
- Contract templates
- Template rules
- Internal signatory rules
- Clause and clause variation setup
- Contract configuration
- External storage and e-signature integrations
- Mappings for Now Assist contract metadata extraction and Now Assist contract analysis
The Contract Request table is automatically selected for a new configuration. You can manually select a different table, if necessary. Note: To avoid configuration issues, ensure that you select the same table across all
related configurations.
- Configure dynamic tables for contract template
- You can now set up the contract template on the Contract Request [sn_cm_core_contract_request] table. When you select the Contract Request table, the Table tab in the Microsoft Word add-in displays an additional field, called the Parent request table field, that you can use to select the source parent request table.
Additionally, the
Table field has been renamed to Lookup table where you can select the table from the data that is populated into the contract document. If the template isn’t based on the
Contract Request table, only the Lookup table field is shown.
- Signature blocks enabled by default for new contract templates
- When you’re creating a contract template, the Signature blocks check box in the Word Template New Record form is selected by default. If you want to configure the participant-based signatories for the
contract template, you can clear the check box.
- Copy fields from parent request to contract request
- You can now configure the ContractManagementExt extension point to automatically copy the required fields from the originating business unit record to the contract request when it’s initiated.
- Modify signatories
- Enable contract fulfillers to pause an ongoing signature process, make necessary changes to the list or order of signatories, and then resume the process without restarting the entire workflow by using the Modify
Signatories and Resume signature options. This feature is supported only for the Docusign electronic signature provider.
- Signature workflow for a contract request
- The wet signature process has been enhanced for better control and clarity. Wet signature requests are sent one signatory at a time, starting with the first signatory in order. When the signatory signs and returns the
document, the fulfiller manages the remaining signatures.
- Resend signature request
- Enable contract fulfillers to manually trigger a signature request when needed, instead of relying on automated reminders by using the Resend signature request option.
- Configuring signatories in Contract template using Microsoft Word add-in
- Signature placeholders in contract templates are now mapped to the e-signature tool tags (such as Docusign), instead of signer fields to help accommodate changes in the signatories. The values in the signature blocks are filled in by the signatories during the signing process.
- Upload and parse a Microsoft Word
document that includes content controls
- Upload the contract document directly from the Microsoft Word Add-in instead of selecting it from your system.
|
| Creator Studio |
- Playbooks use only published forms
- As of Creator Studio version 27.2.2, forms must now be published (marked as ready) before you can use them to create an automated playbook.
- Hide the App Engine Studio template with a new system property
- As of Creator Studio version 27.2.2, Creator Studio users who have both App Engine Studio (AES) and Creator Studio installed will no longer see the AES template when they create an app. Admins can choose to show the AES template using the new com.glide.creator_studio.template_deny_list system property.
- Form location removed from form creation
- Defining the catalogs and topics for a form is now accomplished by modifying the form settings rather than being done during the form creation process. If you haven't defined a location for a form, you are prompted to do so
before you can mark it as ready.
|
| Data Loss Prevention Incident Response | |
| Data Management | |
| Data management for CSM |
- Product Inventories configurations for Customer Life Cycle Management workflows
- Perform the Modify, Suspend, Resume, and Disconnect operations on product inventory records directly from the Product Inventory related list on the Accounts page.
- Grant write access to account relationships
- Enable administrators and customer service managers to update account relationship records.
- Enable write access to contact relationships
- Enable administrators and customer service managers to update the contact relationship records.
- Migrate the account manager responsibilities from the account team member relationships to the new responsibility access configurations. The updated framework enables you to manage access settings more
efficiently.
- Update roles within relationship agent and relationship contributor
- Modify the roles of the relationship agent and relationship contributor to include the new granular roles that can grant access by responsibilities.
- Notification for case tasks at business locations
- View the notifications for the case tasks that are associated with the business locations on the Business Location Service Portal (BLSP). This way, your location members can stay informed about their pending
tasks.
- Case resolution by location staff at other business locations
- Enable your location staff, whether at company-owned or third-party-owned organizations (internal and external business locations), to handle and resolve issues from other eligible business locations.
-
The Inbound Queue [sn_tmt_core_inbound_queue] table is renamed to Inbound Request table.
Use the Request Configuration field on the Inbound Request [sn_tmt_core_inbound_queue] table to reference the Inbound Request Configuration [sn_tmt_core_inbound_queue_config] table while executing
synchronous or asynchronous flows.
|
| DevOps Change Velocity |
- Simplified onboarding of orchestration tools not supported in the base system
- Integrate orchestration tools that aren’t supported in the base system by leveraging a generic framework.
- Custom fields for planning tool integration
- Add custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making.
- Additional scans for DevOps Health Scan Content pack
- Additional set of proactive checks focused on problems that tend to occur before or after an upgrade along with identifying configuration issues like plugin and version incompatibilities, or pipelines that chronically fail,
have been added.
- Import pull-request records for Bitbucket Server or Bitbucket Data Center
- Import pull-request records for Bitbucket Server or Data Center for improved insights and efficiency.
- Change request creation with errors in DevOps data retrieval for Harness pipelines
- Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.
- Branch name filter
- Search for build numbers by the branch name while associating DevOps data to a change request in the Service Operations Workspace (SOW) or Classic UI.
- Test summary name in GitHub Actions
- The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.
- Token based authentication for Rally
- Configure webhooks for Rally using token based authentication instead of using the integration username and password.
- Renamed variables for Docker
- The environmental variables in the Generic Docker actions for DevOps Change Velocity have been renamed by removing the CI prefix for better clarity.
- Security scan results
- Security scan results on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab.
- Source of commits in SOW
- View the source of commits like pipeline execution, branch, repository, and so on for a change request in the DevOps data section of the Service Operations Workspace.
- Track file changes
- The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks.
- Close code value for a change request
- Two new properties have been added in DevOps Change Velocity, so that you can specify a close code value for a change request based on the change request completion state when the autoCloseChange parameter is enabled.
- Support for MID Server cluster
- Improve load balancing and failover protection by selecting a MID Server cluster when connecting to a tool instance associated with a MID Server cluster. This configuration enables multiple MID Servers with relevant capabilities to be grouped.
- Improved UX for DevOps Change health scans
- Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
- Pipeline association for GitHub Actions
- When onboarding GitHub Actions pipelines through the App onboarding catalog or the onboarding APIs, now only the selected pipelines are associated with the DevOps app. If no pipeline is selected, all pipelines within the specified repository are associated.
- Tool connection check status
- If a tool is marked as Disconnected because of a system-generated failure during an unsuccessful connection check, any subsequent successful check automatically updates the connection status to Connected. If you manually
disconnect the tool, the tool status remains Disconnected even if there’s a subsequent successful connection check.
- New roles for vulnerability integration
-
- The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.
- The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.
- Prod deploy commit logic for other step types
- Update the sn_devops.commit_rel_change_step_type property to have other step types, like Test or Deploy, use the same commit logic as Prod Deploy.
- Override start and end time of a change request
- Set the sn_devops.change_request.auto_close_allow_override_start_time and sn_devops.change_request.auto_close_allow_override_end_time properties as false to consider the
change request start and end time instead of the pipeline’s when the autoCloseChange parameter is enabled in a pipeline.
- Node version of DevOps extension
- The node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps.
- Enhanced pipeline governance in GitLab
- View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image.
- Health scan enhancements
-
- Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.
- Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in GitHub, GitLab, Azure DevOps, and Jenkins using the DevOps webhook configuration analysis health check.
- Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.
- Verify if any scheduled job has been configured to run as an invalid or non-admin user.
- Navigate to the Findings list from the DevOps Change Workspace home page by selecting View all findings in the Health scan findings widget.
- Enhanced JFrog integration with DevOps Change Velocity
- Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
- Bearer authentication in JFrog
- Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
- HTTP proxy for Docker
- Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
- Health scan enhancements
-
- Identify any callback processing issues in your instance.
- Identify any access control rule (ACL) that is incorrectly associated with a role in your instance.
- Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_* tables is present.
- Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.
- Auto close without Change Management - State Model [Legacy] plugin
- Change requests can now be auto-closed without requiring you to install the Change Management - State Model [Legacy] plugin.
|
| Dispute Rules Content Pack for Visa |
- Visa Resolve Online (VROL) version 25.2 updates
-
Updated the dispute questionnaire provided through Dispute Rules Content Pack for Visa to align with Visa Resolve Online (VROL) release 25.2 revision changes.
|
| Document Intelligence | |
| Document Services | |
| ERP Semantic Mining | Yokohama Patch 1
- Faster initialization
- In addition to daily total application statistics, the SQLM and APPSTATS initial scan now also retrieves all monthly total application statistics up to the current date.
|
| Enterprise Asset Management |
- Refresh flow in OT workspace
- For single and multi-model refresh orders, the OT manager can edit the replacement model even after the refresh order has been created in the OTAM workspace. Additionally, the sourcing location is also editable.
- Reflow for Configurable Workspace
- The configurable Enterprise Asset Workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality.
|
| Event Management |
- Property name changes
- Enable CMDB Correlation for Alert Aggregation ( CMDB groups) (sa_analytics.agg.query_cmdb_correlation_enabled) has been renamed Enable CMDB correlation.
- Enable alert aggregation for CI-based Automated groups (sa_analytics.specific_patterns_enabled) has been renamed Enable ML based Automation correlation.
- Enable alert aggregation for Text-based groups (sa_analytics.text_based_group_enabled) has been renamed Enable Text based correlation.
- Use all CMDB relations for CMDB group correlation. This property impacts both CMDB group correlation and Alert Similarity on the Alert form
(evt_mgmt.related_cis_get_all_relation_types) has been renamed Use all CMDB relations for CMDB group correlation.
- Pull connectors
- Simplifying the setup for Out-of-the-Box (OOTB) event rules that come with the pull connectors that have not yet been activated, deactivated, or modified, the Apply additional matching rules option is now enabled by default.
If a rule has been previously applied, you must set this option manually.
|
| External Content Connectors | |
| Field Service Management |
- SLAs in Dispatcher Workspace
- The SLAs breached query on the Dispatcher Dashboard in Dispatcher Workspace has been updated to look at the SLAs that are associated with the work order tasks only instead of the work orders and work order tasks. The SLA breached counter on the task cards is also
static, instead of real time. For more information on changing the SLA timer on task cards, see the Enable the SLA timer on work order task cards property on Configure settings for Dispatcher Workspace.
- Assignment groups and territories in Dispatcher Workspace
- You must save the default assignment groups or territories in Dispatcher Workspace to load when you open Dispatcher Workspace. If you don’t have the defaults saved, then you must select the assignment groups or territories to appear every time you open Dispatcher Workspace. This change is made to improve the performance of Dispatcher Workspace. For more information on saving the default assignment groups, see the Groups section on the General tab on Enable Dispatcher Workspace settings. For information on saving default territories, see Select Territories in Dispatcher Workspace. Administrators can disable this by setting the sn_fsm_disp_wrkspc.enableEmptyState system property to false.
- Work order questionnaire
- Availability of inline choices for a question and the ability to add additional information for a question when completing a work order questionnaire through the Now Mobile Agent application.
- Role to access opportunities
- The Opportunity Writer sn_opty_mgmt_core.opportunity_writer role has been replaced with the Opportunity Contributor sn_opty_mgmt_core.opportunity_contributor role. Field service technicians can use the new Opportunity
Contributor[sn_opty_mgmt_core.opportunity_contributor role to create and view opportunities.
- Google Maps APIs for Field Service Capabilities
- Upgrade to the new Places API (new) and Routes API for Field Service Capabilities.
Effective March 1, 2025, Google has designated the Places API, Directions API, and Distance Matrix API as Legacy services. The newer versions of these services are Places API (New) and Routes
API. You can’t enable or generate new API keys for these legacy services. However, you can continue using these services with the existing API keys. Enable the new APIs from Google Console to continue using
the API services without any issues. If you create a new Google API key after March 1, 2025, enable the new APIs from Google Console to use these services with the new API keys. For more information see, KB2111488, KB2112054, and Changes to Google Maps Platform automatic volume discounts, monthly credit, and services transitioning to Legacy status.
|
| Financial Services Card Operations |
- Visa Resolve Online (VROL) version 25.1 updates
-
Updated the following columns to align with release 25.1 revision changes:
- The is_parcelado column has been removed from the dispute intake table.
- The domain value description for the DisputeResponseReason column has been updated from Copy of ATM Cash Disbursement or Load Transaction to Copy of ATM Cash
Disbursement.
|
| Financial Services Operations Core |
- Added fields to Claim Base table
- Added the following fields to the Claim Base [sn_bom_claim_base] table:
- SIU review
- Claim validation decision
- Claim fraud decision
|
| Financial Services Operations Integration with Visa | |
| Generative AI Controller | |
| Hardware Asset Management |
- Reflow for Configurable Workspace
- The configurable Hardware Asset Workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality.
|
| Health Log Analytics |
- Component-based alert grouping is deprecated
- Starting in version 36.0.19, the adoption of a streamlined two-tier alert model, Log Analytics Group to Single Alert, has replaced component-based alert groups, which have been removed. This model aligns alert representation
with the service-level anomalies identified by Health Log Analytics, rather than individual host CIs. The update improves alert visibility, simplifies correlation, and enhances overall alert management efficiency.
|
| ITOM AIOps |
- Enrich automation
- Introduced a new section And finally that contains two radio buttons that replace the previous Continue running automations of this type toggle switch.
- Run other enrich alert automations continues running automations with the same filter conditions.
- Don't run other enrich alert automations halts additional automations after execution, except those owned by other assignment groups.
- Investigate alerts using Now Assist
-
Investigate alerts using Now Assist, which now uses the Retrieval-Augmented Generation (RAG) process to enhance alert investigation. This enhancement enables the retrieval of highly relevant past incidents, providing accurate
context and actionable insights. Now Assist also notifies users of those involved in past or present efforts to resolve similar issues, promoting collaboration and reducing duplicated efforts.
- Component-based alert grouping is deprecated
- Starting in version 36.0.19, component-based alert groups are removed as Health Log Analytics adopts a streamlined, two-tier alert model: Log Analytics Group to Single Alert. It aligns alert representation with the service-level anomalies identified by Health Log Analytics, rather than individual host CIs. The update improves alert visibility, simplifies correlation, and enhances overall alert management efficiency.
|
| ITOM Cloud Accelerate |
- Cloud Provisioning and Governance: Terraform Connector has been renamed Cloud Services Catalog Terraform Connector
|
| ITOM Optimization |
-
- Migration of legacy workflows to Workflow Studio flows or subflows.
- Policy Rule Actions now supports Workflow Studio subflows instead of legacy workflows.
|
| ITOM Visibility |
- Experience more accurate name suggestions for application service candidates based on Service Fingerprints in Service Mapping Plus store version 1.15.0.
- Limits in Service Mapping
- Limits in Service Mapping prevent the disabling or deletion of jobs scheduled for the Checkpoint Reaper or the Service Model's Blob Reaper.
- Limits in tag-based Service Mapping
- Starting with version 1.15.2, experience improved performance in Service Mapping. A new property limits the creation of tag-based service candidates to 200 per service family.
- Name update in Service Mapping
-
- Application Services in the navigation menu has been renamed Service Instances.
- The label for the [cmdb_ci_service_auto] table has been changed from Application Service to Service Instance.
- Discovery status monitoring
-
Discovery schedules that have no status updates for over a defined number of minutes are analyzed automatically by the Discovery Status Monitor job. By default, this job applies to Discovery schedules that discover configuration items.
|
| Identity | |
| Impact | |
| Incident Management |
- Email redirection behavior for major incident email notification links
- In major incident email notifications, you can now decide where the links to a major incident record are redirected. Instead of a major incident record automatically opening in the classic UI16 interface in Major Incident Management, the record can be opened in SOW. The major incident record link in an email notification opens in SOW only if the following conditions are met:
- The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true. Setting this property to true enables the email
redirection behavior for all tables including major incident.
- The Redirect SOW Email notification for Major Incident Management (sn_major_inc_mgmt.sow_email_notification_redirect.mim) property is set to true.
- You have the sn_sow_user role.
The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior.
- Email redirection behavior for incident email notification links
- In incident email notifications, you can now decide where the links to an incident record are redirected. Instead of an incident record automatically opening in the classic UI16 interface in Incident Management, the record can be opened in SOW. The incident record link in an email notification opens in SOW only if you have the sn_sow_user role and any of the following conditions are met:
- The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true. Setting this property to true enables the email
redirection behavior for all tables including incident.
- The Redirect SOW Email notification for Incident Management (sow_email_notification_redirect.incident) property is set to true. You can create this
property if you want to enable or restrict the email redirection behavior specifically for the incident table. This property, if created and set, overrides the Redirect SOW Email notification
(sow_email_notification_redirect) base system property.
The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior. To ensure consistency, the email notification templates for
incident tasks are also updated to send the notification from Service Operations Workspace (SOW) in the same format as sent from classic UI16 interface similar to incident. Also, the template theme is updated to match the Next Experience theme.
- Incident and problem workflow changes
- When a problem is fixed and the Share fix option is triggered, the event is added to the Work notes (Private) field instead of the Additional comments (Customer
visible) field for the incident associated with the problem record.
This feature is available in the base system for the new customers. For existing or upgrade customers, admin must set the
Communicate problem workaround to incident worknotes
(com.snc.incident.communicate_prb_workaround_to_inc_worknotes) system property to true to enable the feature.
- Changes in the reopening incident behavior
- Enable the agents with incident write access, callers, requesters, or Opened by end users to reopen a resolved incident. Both the caller and the requester can view and use the
Reopen option on the incident classic UI16 form and the Portal UIs, such as Service Portal and Employee Service Center (ESC) portal.
An agent can view and use the Reopen option on the incident classic UI16 form to reopen any incident that is assigned to them or to other
agents. However, on the Portal UI, an agent can only view and use the Reopen option to reopen an incident if it’s assigned to them.
- Sorting CIs in incident forms
- The search performance of the available CIs for the Configuration item field on an incident form is enhanced to promote a clean UI and quick loading and sorting of the CIs. The search results that list
the CIs are sorted alphabetically by CI name instead of by CI class and then CI name. The ref_ac_order_by=sys_class_name attribute is removed from the default attributes on the
cmdb_ci field of the Task [task] table, which increases the performance of the field.
This change is applicable to new and existing users using the default attributes. You can use the
Override attributes option to restrict this change for any required child tables that extend to the cmdb_ci field of the Task [task] table.
|
| Industrial Process Manager |
- Viewing multiple records at once in the Equipment Model Manager
- In the Equipment Model Manager of the Industrial Workspace, view multiple records and keep the record context available instead of only viewing one record at a time. When creating or opening multiple records, the records open in single row of tabs
at the same level so you can navigate back to other opened records.
|
| Instance Data Replication | |
| Insurance Claims Core | |
| Knowledge Graph |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| MID Server | |
| Mobile Platform |
- Input form screen enhancement and changes
- Use the following enhancements added to the input form screen:
- Selecting input values directly within the input form screen, either from a list or from a group of chips. Now users don’t need to navigate to a separate dedicated screen for value selection, when using the inline choice
chips layout. You can also define the number of input values to display on an input form screen section.
- Ability to add images, plain text, and rich text within specific inputs. These added descriptive elements provide more context to your users and give a clearer idea of what is required for certain inputs. For example, an
image can accompany a checklist to ensure that a piece of hardware is wired correctly.
- Provide users with the ability to perform actions in relation to the displayed input parameter, while working directly on an input form screen. The available actions are: navigate to another screen, add an attachment
from the gallery or camera, and add a comment to a field. Users submit these added actions either when saving their progress or completing the input form
screen.
- Save input form screen data before it's submitted. Users with access to the same record can see each other's changes either when saving their progress or completing the input form
screen.
- Interact and switch between other navigation tabs while also working on the input form screen.
- Sections are no longer displayed if they don’t contain any input fields.
- Additional number attributes for input form screens
- Use the following number attributes in your input form screens:
- Use the CustomErrorMessage attribute to specify an error message when a UI rule condition is met.
- Use the SkipValidationWhenHidden attribute to skip validation on hidden inputs.
- Enable barcode scanning with an external scanner
- Configure barcode scanning with an external scanner without denying access to the camera for the entire mobile app.
- Mobile Publishing enhancements and changes
-
- Enabled Android deep links for multiple instances.
- Enhanced validation for transparent images used in branded apps.
- Support for public-facing screens in branded mobile apps. Admins can configure URLs that link to public-facing web pages. These web pages are displayed to end users without needing to log in to the mobile
app.
- Turn off Zero Trust Access banners in mobile app screens
- In mobile client versions 19.4 and later, you can turn off Zero Trust Access banners on mobile screens. Turning off these banners can enhance usability of your mobile apps because the banner does not display each time the
connection state changes so end users are not interrupted by the banner display. You can configure this behavior by setting the disableZTABanner mobile property on your ServiceNow instance.
|
| Next Experience |
- Next Experience preferences
- The new user preference panel provides a more efficient, streamlined way for you to work. Use the new search bar to locate your preferences. A wider modal displays all preference groups and when you select a group,
all the individual preferences that are related to it appear in the same window.
|
| Next Experience Components |
Table 8. Components
| Component |
Enhancement |
| Appointment calendar |
- Select multiple slots
- Add customizable categories for appointment slots
- Hide past and unavailable slots
- Add contextual tags in appointment slots
- Configure number of rows displayed in each slot in the Day and DAYMOBILE views
- Configure container height adjustment
|
| Attachments |
- Option to download all attachments
- Revised delete attachment confirmation popup message
|
| Avatar |
Configure avatar to behave as a button or a link. |
| Calendar |
- DST support with multiple time zones in the Calendar and Timeline views
- Hide header
- Multiple time zones in the Timeline view
- Scroll control for the Calendar and Timeline views
|
| Email composer |
Now Assist generative AI suggestions for all email scenarios, email templates, response templates, and quick messages. |
| Email composer (mini) |
Now Assist generative AI suggestions for all email scenarios, email templates, response templates, and quick messages. |
| Form |
- Configuration panel updates
- Form controller configuration panel updates
|
| Form templates |
- Sort templates alphabetically and by last used.
- New tab for Favorites for you to add and remove templates.
- Larger cards that don't truncate template name and description, and show Last used timestamp.
|
| Highlighted value |
- Medium size variant.
- Custom tooltip property.
|
| iFrame |
Send messages to iframed document. |
| Kanban Board |
- Multi-select in cards
- Configure selecting dependency lines
- Add secondary header
|
| Modeless dialog |
Make the dialog dynamic and automatically resize to fit the content. |
| Node Map |
- Force layout for representing graphs without structure or hierarchy
- Custom popover configuration in Hierarchical, Layered, and Force layouts
- Customizable nodes in non-unified layouts
- Self-referencing nodes denoted with edges looping back to the node
- Export maps in JPG and PNG
- Aggregate or segregate multiple connections between the same nodes
|
| Pill |
Display the selected pill state which doesn't display by default. |
| Quick filter |
- Configure section headers in typeahead dropdown
- Configure footer action button
- Configure placeholder text value for input field
|
| Record lookup |
- Search for contacts by name, phone, or email
- Preview shortlisted results in a paginated form
- Quickly link or unlink a shortlisted contact to a case
- Edit details for a record without accessing the parent record
- Hide record header
- Configure search results
- Render highlighted values in the linked card
- Qualify search results using specific conditions (reference qualifiers)
- Hide fields with empty values
- Hide link button
- Expand or collapse card
|
| Stepper |
- Standardized font size (small or medium) for all steps
- By default, pagination adjusts to display the current selected step
|
Table 9. Data visualizations
| Chart |
Enhancement |
| Bar |
Percent (%) information added to chart tooltips and data table below chart. |
| Bubble |
Percent (%) information added to chart tooltips. |
| Geomap |
Percent (%) information added to chart tooltips and data table below chart. |
| Heatmap |
- Percent (%) information added to chart tooltips and data table below chart.
- When the metric value is set to "Count," show a zero (0) when no data is available.
|
| Pivot table |
- When there's no value in the selected dataset or for the configuration, choose the display format.
- Data sources limit increased from 10 to 15.
|
| Time series |
- Percent (%) information added to chart tooltips and data table below chart.
- Support for business calendars such as Gregorian, fiscal, and any manually added calendar.
- For all chart formats, except "column:"
- When there's no value in the selected dataset or for the configuration, choose the display format.
- For table data sources, when there's no data for a specific time on the chart, show a continuous line without gaps.
- Show a chart and graph data table for easier screen reader access.
- For line, spline, area, and step charts, have a marker show at each data point on the chart including where values are zero (0) or missing.
- For a chart with up to 3 metrics, you can add alternative Group by's for each metric for the user to select from.
- Sorting when data is grouped.
- New Date range option to set the period end date to update automatically to the current date.
|
Table 10. Templates
| Template |
Description |
| Dashboards |
- Pills at the top of the page display any categories assigned to the dashboard
- User avatars at the top of the page indicate real-time editing
|
Table 11. Bundles
| Bundle |
Enhancement |
| Record list |
- Condition builder available in the list header
- If live list is enabled, infinite scrolling is enabled by default
|
|
| Next Experience Developer (NED) Tools |
- Time filters for events
- Icons were added to each event to enable you to select a timeframe when filtering events.
- Subtree filters for events
- Scroll and search through a selected portion of the component tree.
- Filters for traces
- Filter traces with front-end filters to streamline span visualizations, specialty filters to view targeted waterfall analysis without losing overall context, and level filters to adjust the detail display in span
visualizations.
|
| Notifications | |
| Now Assist |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Previous Patch releases
- Configure multilingual service for Now Assist applications
- Enable translation settings is now Multilingual service in Now Assist admin console.
- Default email client for email recommendation skill
- The Seismic email client is enabled by default on Core UI with the activation of email recommendation. This client provides the Generative AI application features for creating email responses, draft management, and template management.
- Now Assist panel responseNow Assist panel response
- With the carousel experience removed, the Now Assist panel now generates a synthesized response for any user inquiry. This response includes content from Knowledge articles, flows & actions, skills, and links to those articles, instead of only the Now Assist panel skills.
|
| Now Assist AI agents |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Platform Request status AI agent
-
The request status AI agent provides an AI-generated summary of the most recent comments from the AI agent or other people working on a ticket. You can add attachments to an open ticket or incident to support a request
action. To find more information about an open ticket, you can ask the request status AI agent follow-up questions based on previous answers from the agent.
- Configuring Now Assist
AI agents
- Run AI agents and agentic workflows concurrently in AI Agent Background Channel and in Non-interactive mode.
- Add a Knowledge Graph to an AI agent
- The Global Graph resource for creating a Knowledge Graph tool has been renamed to Enterprise Graph.
Yokohama Patch 8
- Confirm your web search tool provider data policies
- If you select Google as your web search provider for web search AI agent tools, Google will use Grounding with Google Search, offered under a Global Standard deployment, and data may be routed to places outside of regions specified on your ServiceNow instance as a result. Consult your
organization's data policies before enabling AI agents with web search tools that use Google as the provider.
- Yokohama Patch 6
- Add version control to instructions sent to the LLM
- You can review multiple versions of instructions sent to the LLM when designing your AI agents or agentic workflows. You can choose which version is active to help with testing or evaluating the success of an AI agent or
agentic workflow to compare against other versions. Versions are named and ordered by time created for organizational purposes.
- Duplicate and edit existing tools when creating new AI agents
- When adding a tool to an AI agent, you can select an existing tool instead of creating a new tool from scratch. After an existing tool is added, you can make changes to suit the specific AI agent’s needs.
- Now Assist
AI agents reference
- The sn_aia.enable_agent_tool_input_value_overrides system property is migrated to the [sn_aia_property] agent system property.
- Yokohama Patch 3
- Monitor more AI agent analytics in the AI Agent Analytics dashboard
- Two new pages have been added to the AI Agent Analytics dashboard, giving administrators more indicators, visualizations, and breakdowns to track AI agent performance and usage.
- Exploring Now Assist
AI agents
- Impersonation in Now Assist records transactions done by an AI agent in the name of the AI agent who executes the agentic workflow.
|
| Now Assist Skill Kit |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for App Engine |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Collaborative Work Management |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Configuration Management Database (CMDB) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Creator |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills, agents, and agentic workflows are turned on by default
- The skills are automatically available to appropriate role users for the application, such as ITIL roles on incident forms or change forms. This change simply activates the skill and does not touch the roles that may be
needed to use the skill. The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills and agentic workflows are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill, agent, or agentic workflow is turned on automatically (the AI asset was never configured and turned on, then
turned off again). Previously configured skills and agentic workflows that were turned on, then off, remain inactive.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Previous Patch releases
- More easily identify changes when previewing and updating applications
- When previewing an application, any requested changes made by the Now Assist for app generation skill are listed when the preview pane loads.
- Edit applications without having to change the scope manually
- When editing applications, the Now Assist for app generation skill now changes the scope that you’re working in to the scope of the application automatically.
- More easily query Analytics Generation
- Analytics Generation now uses a semantic filter instead of Natural Language Query (NLQ), resulting in less rigid requirements for queries.
- Yokohama Patch 1
- Improved query engine for Analytics Generation
- Starting in Yokohama Patch 1, analytics generation supports GPT-4o for generating queries, to provide better accuracy in responses. These improvements include support for up to two levels of dot-walking based on user
utterances.
|
| Now Assist for Customer Service Management (CSM) | Yokohama Patch 3
- Triage cases agentic workflows enhancements
- Added new standalone AI agents to check duplicate cases and split some existing standalone AI agents to focus on more specific tasks. The AI agents available are the Triage cases planner AI agent, Context validator and
analyzer agent, Duplicate identifier AI agent, Informational queries AI agent, Transactional queries AI agent, Case creation AI agent, Entity extraction AI agent, Document verification AI agent, and Email response AI
agent.
- Now Assist in Portal case form enhancement
- Added the new Ask Now Assist button that opens a contextual chat window so that a requester can carry the conversation forward. If no results are found or if the requester isn’t satisfied with the result, they can
get further assistance by selecting the button to chat and get an answer, which helps to avoid case creation.
Yokohama Early Availability
-
Email reply recommendations enhancements
- Refined the AI-generated reply recommendation to create the best response for users by applying tone changes in the Now Assist context menu. Additional tone options, including casual, formal, and sympathetic, are available.
- Chat reply recommendation enhancements
- Added the chat reply recommendation enhancements to respond in a conversational tone and get feature parity in the Now Assist Admin console:
- Refined the AI-generated reply recommendation to create the best answer for your users by applying tone changes in the Now Assist context menu. Additional tone options, including casual, formal, and sympathetic, are available.
- Added parity with the chat summarization Now Assist Admin console capabilities. The Now Assist Admin console can specify the portal and channels for chat reply recommendations and assign additional support roles.
- Case summarization enhancement
- Detailed feedback option is now available for negative feedback
in the generated case summary.
- Xanadu Patch 7: Extended the capabilities of the case summarization feature so it can now be used on custom tables.
|
| Now Assist for Enterprise Architecture (EA) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Field Service Management (FSM) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Yokohama Patch 6
- Removed prompt headers
- The prompt headers have been removed from the work order summarization skill to support third-party Large Language Models (LLMs). You can now customize prompts via a hyperlink to the Now Assist skill.
|
| Now Assist for Financial Services Operations (FSO) |
- Yokohama Patch 11
- Role configuration required for agentic workflows and AI agents
- Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
|
| Now Assist for HR Service Delivery (HRSD) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Yokohama Patch 6
- Flow name
- The Resolve noncritical HR cases flow has been renamed to Resolve HR cases flow.
|
| Now Assist for Hardware Asset Management (HAM) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for IT Operations Management (ITOM) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- AIOps AI agents removed from the analyze alert impact agentic workflow
- Four AIOps AI agents have been removed from the analyze alert impact agentic workflow as they're now available in the manage alerts autonomously agentic workflow. AI agents for Dynatrace, Kentik, and New Relic remain in the analyze alert impact agentic workflow to help you learn about and respond to alerts.
|
| Now Assist for IT Service Management (ITSM) | Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Role configuration required for agentic workflows and AI agents
- Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Skills activated by default in Now Assist for ITSM
- For new Now Assist for IT Service Management (ITSM) users, the following skills are activated by default:
- Incident summarization
- Change request summarization
- Chat summarization
- Yokohama Patch 6
Removing the prompt headers from the Customize prompt screen
- The prompt headers have been removed from the Customize prompt screen in the Incident summarization and Change summarization skill to support third-party Large Language Models (LLMs).
- Yokohama Early AvailabilitySystem property to display knowledge article templates
- Display Knowledge article templates that you can use to create articles by using a system property. In earlier releases, the templates were displayed by default.
- Yokohama Patch 3
-
The Categorize incidents use case has been renamed to the Triage and categorize ITSM incidents agentic workflow.
The following AI agents have been added to the workflow:
- Link major incident AI agent
- Link incident to problem AI agent
The Incident categorize AI agent has been renamed to Categorize incident AI agent.
|
| Now Assist for Legal Service Delivery (LSD) |
- Yokohama patch 11
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Role configuration required for agentic workflows and AI agents
- Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add.
|
| Now Assist for Order Management |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Sales Force Automation (SFA) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Security Incident Response |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are now turned on by default
-
The following Now Assist skills for Now Assist for Security Incident Response and Now Assist for Vulnerability Response
are activated by default.
- Security incident summarization (SIR)
- Resolution notes generation (SIR)
- Post incident analysis (SIR)
- Security incident recommended actions (SIR)
- Correlation insights generation (SIR)
- Security incident quality assessment (SIR)
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Software Asset Management (SAM) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills, agents, and agentic workflows are turned on by default
- The skills are automatically available to appropriate role users for the application, such as ITIL roles on incident forms or change forms. This change simply activates the skill and does not touch the roles that may be
needed to use the skill. The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills and agentic workflows are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill, agent, or agentic workflow is turned on automatically (the AI asset was never configured and turned on, then
turned off again). Previously configured skills and agentic workflows that were turned on, then off, remain inactive.
- Role configuration required for agentic workflows and AI agents
- Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add.
|
| Now Assist for Source-to-Pay Operations |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Strategic Portfolio Management (SPM) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Telecommunications, Media and Technology (TMT) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Vulnerability Response |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are now turned on by default
-
The following Now Assist skills for Now Assist for Vulnerability Response
are activated by default.
- Recommend preferred solution for VIT
(VR)
- Vulnerable item de-duplication (VR)
- Approval Recommendation (VR)(USEM)
- Security Exposure Management (SEM) Insights (VR)(USEM)
- SPC Setup Connector (Security Posture Control)
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist for Workplace Service Delivery (WSD) |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
|
| Now Assist in AI Search |
- Yokohama Patch 11
- Now Assist in Virtual Agent conversational prompt auto-complete suggestions
- Auto-complete suggestions for Now Assist in Virtual Agent conversational prompts are only returned from the search user's domain. Suggestions are disabled if they match any exclusion rule entry from the Search Suggestion Exclusion List
[sys_search_suggestion_blacklist] table. The system scores suggestions based on how search users interact with and rate their Genius Result responses, and preferentially displays higher-scored suggestions.
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Yokohama Patch 6
- Semantic vector search indexing includes Catalog Item short descriptions
- Semantic indexing now indexes short descriptions from Catalog Item source records to improve search recall and make field indexing more consistent between legacy (keyword) and semantic indexing.
- Yokohama Patch 3
- Microsoft SharePoint Online login prompts in Knowledge Graph user citations
- If you're not logged in to Microsoft SharePoint Online, Knowledge Graph user citations in Now Assist Multi-Content Response Genius Result answers now prompt you to log in. When logged in, you can check any user citation in a Genius Result answer to see the list of files the cited user has shared
with you in Microsoft SharePoint Online.
- Now Assist Q&A Genius Results
- The Now Assist Q&A Genius Results feature is in maintenance mode. This feature will have no new enhancements but will have continued support. Similar and improved functionality is available in the newer Now Assist Multi-Content Response Genius Results feature. For more details on this feature, see Now Assist Multi-Content Response Genius Results.
- Now Assist Actions Genius Results
- The Now Assist Actions Genius Results feature is in maintenance mode. This feature will have no new enhancements but will have continued support. Similar and improved functionality is available in the newer Now Assist Multi-Content Response Genius Results feature. For more details on this feature, see Now Assist Multi-Content Response Genius Results.
|
| Now Assist in Contract Management |
- Yokohama Patch 11
- Automated obligation extraction
- Use the manage contract repository agentic workflow to automatically identify and capture key contractual obligations from signed contracts and create obligation records in the contract repository. The AI agent in the manage
contract repository agentic workflow uses the Now Assist Contract obligation extraction skill to extract key contractual obligations from contracts.
- Using contract playbook to review AI-extracted obligations
- Review extracted obligations in the contract playbook, with options to edit, approve, or reject each obligation. Approved obligations are added as obligation records in the contract repository while rejected obligations are
deactivated.
- Contract obligation extraction skill in Now Assist in Contract Management
- Configure and map use cases for obligation extraction skill in the Now Assist Admin console to automatically extract key contractual obligations from signed contracts. The AI agent in the manage contract repository agentic workflow uses the Now Assist Contract obligation extraction skill to extract key contractual obligations from contracts.
- Conversational contract search and insights Workflow
- Contract documents are often complex and stored across multiple formats and repositories, making keyword-based search inefficient and error-prone. The new Now Assist powered conversational search feature enables you to search contract documents using natural language and dialogue-driven queries.
The conversational search feature does not support searching
within contract documents that are scanned PDFs.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Now LLM LTS support for Contract Management Pro
- Long term stable (LTS) models are part of Now LLM Service and provide longer model stability windows for regulated industries. These models can integrate with tools to provide governance, monitoring, and compliance controls.
- Yokohama Patch 6
- Extract metadata from signed contracts automatically
- Use the AI agents in the Manage contract repository agentic workflow to automatically extract metadata from signed contracts and calculate the contract reminder dates for contract renewal or termination. You can review the
AI results in the contract playbook and update it if necessary before saving it.
- Contract metadata extraction use cases
- Support for 14 additional metadata fields in the CM Pro - Contract Metadata Extraction use case available in the base system.
- Yokohama Patch 3
- Configuring contract metadata extraction
- Create a use case and its associated fields for contract metadata extraction in the Now Assist Admin console to define the information that you want Now Assist to detect in a signed contract.
- Create a use case mapping in the Now Assist Admin console to map a use case to specific tables and define conditions to apply the use case for metadata extraction.
- Configuring contract analysis
- Create a use case and its associated question groups for contract analysis in the Now Assist Admin console to identify the non-standard and missing clauses in a contract.
- Create a clause mapping Now Assist Admin console to map question groups of a use case to active clauses in the clause library to display suggestions for non-standard clauses in a contract.
- Create an expected response mapping in the Now Assist Admin console to map questions of a use case to an expected response to identify the non-standard clause in a contract.
- Create a use case mapping in the Now Assist Admin console to map a use case to specific tables and define conditions to apply the use case for contract analysis.
|
| Now Assist in Document Intelligence |
- Yokohama Patch 13
- Document and visual insights AI agent enhancements
- Tools used by the document and visual insights AI agent are consolidated to improve performance.
- Now Assist in Document Intelligence skills are now turned on by default
-
The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- 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.
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Yokohama Patch 6
- Document and visual insights AI agent enhancements
- Generate a summary of document and image attachments with the document and visual insights AI agent.
|
| Now Assist in Platform Analytics |
- Yokohama Patch 13
- View recommended actions
- AI Data Explorer can suggest actions based on the insights that it generates in an exploration.
- Ask questions about FX currency data
- Query 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.
- Benefit from improvements to segments
- Segments 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.
Domain 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 are not supported for indicator sources or modules on domain-separated
instances.
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Configure ACLs for AI agents and agentic workflows
- Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all
authenticated users or publicly available.
- Query Generation skills are active by default
- If the Generative AI Controller plugin is activated, the skills for Query Generation are activated by default.
- Greater visibility into the Query Generation process
- When you call Query Generation from AI Data Explorer or another application, you see each state that the query and response goes through before completing.
- Multi-table source support
- Query Generation supports related table conditions and dot-walking in queries.
- Get insights and visualizations for Workflow Data Fabric tables
- Ask AI Data Explorer information about Workflow Data Fabric data and get insightful responses. You must first add the Workflow Data Fabric tables to the Query Generation Semantic Table Configuration table.
- Use database views in queries
- Generate visualizations or ask AI Data Explorer about data kept in database views, like SLA data. You have to add the database views to the Semantic Table Configuration table.
- Yokohama Patch 7
- Add tables to the semantic data layer
- Choose which tables your users can query with generative AI for data analysis.
- Monitor the health of the Query Generation back end
- View the state of Now Assist for Platform Analytics LLM, plugins, system properties, components, and dependent products.
|
| Now Assist in Virtual Agent |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Conversational Platform Now Assist skills are active by default
- The following Platform Now Assist skills are active by default and no longer visible in Now Assist Admin console:
- Now Assist Multi-Turn Catalog Ordering
- Now Assist Q&A Genius Results
- Now Assist Topics
- Subflows and actions
- Custom skills
- AI agents
- Yokohama Patch 6
- Additional fallback options
- There are up to five fallback options that can be presented to end users:
- Search the web: Triggers web search mode and uses the internet to search for the results.
Note: Only the last query entered into the conversation is considered when entering web search mode via the
fallback option.
- Request a live chat: Triggers live agent mode and routes you to a human support representative.
- Create a generic ticket: Creates a record.
- End this chat: Ends the chat.
Note: This option is only available to standard chat conversations.
- Custom fallback option: Presents a fallback Virtual Agent topic.
- Web search mode enhancements
- Manually enter into web search mode via the input bar for standard and enhanced chat conversations. Web search mode includes in-line citations and the associated sources. A web search mode banner appears in enhanced chat
conversations that end users can use to end the mode.
- Profanity recognition response
- If Now Assist Guardian is enabled and the end user's request contains profane content, the Virtual Agent responds with a message prompt to re-enter an appropriate request without profanity or offensive content.
- Yokohama Patch 3
- The existing Now Assist in Virtual Agent LLM conversational behavior received a terminology update and is now referred to as standard chat.
- Yokohama Early Availability
- Dynamic Translation calls
- If native translation is enabled, a Dynamic Translation call is only made if an unsupported language for native translation is used.
|
| On-Call Scheduling |
- Email redirection behavior for links in major on-call schedule email notification
- In all major on-call schedule or shift email notifications, you can now decide where the links to an on-call schedule or shift record are redirected. Instead of an on-call schedule or shift record automatically opening in
the classic UI16 interface in On-Call Scheduling, the record can be opened in SOW. The on-call schedule or shift record link in an email notification opens in SOW only if the following conditions are met:
- The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true.
- The Redirect SOW Email notification for On-call scheduling (sow_email_notification_redirect.on_call) property is set to true.
- You have the sn_sow_user role.
The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior.
|
| Operational Sustainability Management |
- Result types
- If you have the ESG manager [sn_esg.metric_manager] role, you can now configure either text, choice, or HTML format options for responses to qualitative metric data tasks that are related to manual metric definitions,
including both initial and overridden responses. These options help you achieve more precision and detail in your data collection process.
- Metric data table filters and side panel enhancements
- If you have the ESG data owner [sn_esg.data_owner] role, you can now apply filters by using the filter menu and reject or approve tasks from the metric data table side panel. Data owners can now multi-submit and assign
approvers to multi-approve or reject tasks, with the option to use choice and HTML response formats.
- Data owner assignment types
- If you have the ESG Manager [sn_esg.metric_manager] role, you can now configure the Data Owner Assignment type to be either simple or advanced for manual metric definitions. When you select the Simple option, the system
assigns the specified Data Owner or Data Owner Group to the Metric Data Task. If you choose the Advanced assignment option, which is available with the GRC: Approver Configurator application, you can set custom configuration conditions, tables, or data owners to dynamically assign data owners.
- Table added to the GRC: Metrics application
-
The following tables were added to the GRC: Metrics application:
- sn_grc_metric_import_job
- sn_grc_metric_data_import
- sn_grc_metric_st_import_log
- sn_grc_metric_st_transform_history
- sn_grc_metric_import_template
- Table added to the ESG content accelerator application
- The sn_esg_content_issb_citation table was added to the ESG content accelerator application.
- Table added to the Forecast planning analysis application
- The following tables were added to the Forecast planning analysis application:
- sn_grc_forecast_analysis
- sn_grc_forecast_context
- sn_grc_forecast_data
- sn_grc_forecast_parameter_data
- Database view added to the Scope 3 emissions management application
-
The sn_esg_scope3_asset_emissions database view was added to the Scope 3 emissions management application.
- Changes made to the sn_grc_metric_data_task table
- In the sn_grc_metric_data_task table, the job_submitted, job_errors, choice, overridden_choice, html, and overridden_html columns were added. The type="string" attribute was added to the state column.
- Changes made to the sn_grc_metric_metric table
- In the sn_grc_metric_metric table, the period_date, data_owner_type, data_owner, and data_owner_group columns were added. The type="string" attribute was added to the domain_area column.
- Changes made to the sn_grc_metric_parent_data table
- In the sn_grc_metric_parent_data table, the formula_operands columns, and html columns were added.
- Changes made to the sn_grc_metric_base_definiton table
- In the sn_grc_metric_base_definiton table, the formula_tree, result_type, choice_table, choice_field, choice_condition, data_owner_assignment_type, source columns were added. The type="string" attribute was added to the
frequency column.
- Changes made to the sn_grc_metric_data_by_entity table
- In the sn_grc_metric_data_by_entity table, the html column was added.
- Attributes modified in the sn_grc_metric_collector_data table
- In the sn_grc_metric_collector_data table, the display="true" attribute was removed from the collector_definition column.
- Attributes modified in the sn_grc_metric_data_process_queue table
- In the sn_grc_metric_data_process_queue table, the reference_cascade_rule="delete" attribute was added to the metric_definition column.
- Attributes modified in the sn_grc_metric_definition table
- In the sn_grc_metric_definition table, the type="string" attribute was added to the type, method_type columns.
- Changes made to the sn_esg_msoff_intg_o365_reporting_configuration_filter table
- In the sn_esg_msoff_intg_o365_reporting_configuration_filter table, the related_fields column was added. The display="true" attribute was added to the field_name column in the
sn_esg_msoff_intg_o365_reporting_configuration_filter table.
- System properties are added to the GRC: Metrics application
- The following properties were added to the GRC: Metrics application:
- com.glide.event_manager.grc_metrics_queue.even.load.distribution.enabled
- com.glide.event_manager.grc_metrics_queue.claim_limit
|
| Operational Technology (OT) Manager Foundation |
- Yokohama Patch 11
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
- Some Now Assist skills, agents, and agentic workflows are turned on by default
- The skills are automatically available to appropriate role users for the application, such as ITIL roles on incident forms or change forms. This change simply activates the skill and does not touch the roles that may be
needed to use the skill. The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills and agentic workflows are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill, agent, or agentic workflow is turned on automatically (the AI asset was never configured and turned on, then
turned off again). Previously configured skills and agentic workflows that were turned on, then off, remain inactive.
- Role masking
-
Role masking enables users to limit the roles and privileges of agentic workflows during tool execution. Agentic workflows and their AI agents that get installed with Now Assist applications are assigned pre-defined roles. If you select Users with specific roles for user access, you must configure the security controls to include these roles. Data access settings must also include these roles. For the instructions to change the security controls, see Define security controls for an agentic workflow.
|
| Operational Technology Manager |
- OT device related items and related lists
- The Key Value [cmdb_key_value], Software Instance [cmdb_software_instance], and Firmware Install [cmdb_firmware_install] related lists were added to the OT view on IT and OT classes to view the following information:
- Information related to the OT device populated through the integrations and captured as Key Value pairs.
- Software installed on the OT device if Software Asset Management isn't available.
- Firmware associated with the OT device.
You can view these related lists on the ServiceNow AI Platform® and in the Industrial Workspace Admin.
- OT Excel SGC - Import Task list module in the Industrial Workspace
- The OT Excel SGC - Import Task list module has been added to the Industrial Workspace list view. From the available lists, you can access the import task functionality for the Service Graph Connector for Microsoft Excel.
- OT Excel SGC - Remediation Task list module in the Industrial Workspace
- The OT Excel SGC - Remediation Task list module has been added to the Industrial Workspace list view. From the available lists, you can access the remediation task records created from an import task.
- View and edit device to device connections
- The Device to Device Connections list has been added to the OT Network menu available in the Industrial Workspace List view. You can view the device connections in detail using this list. Also, the Device to Device Connections related list was added to the Related Records tab on
the OT device record in the ServiceNow AI Platform.
- Is Virtual field for OT devices
- Identify whether an OT device is virtual through the Is Virtual field added to the OT device form in the Industrial Workspace.
- OT Subnet Mappings related list
- The OT Subnets related list has been renamed OT Subnet Mappings in both the Industrial Workspace and the ServiceNow AI Platform when viewing an OT device record.
- Manufacturer and Model Number fields
- The Manufacturer and Model Number fields have been removed from the OT device list and form views on both the ServiceNow AI Platform® and in the Industrial Workspace.
- OT Devices tab data
- The following data available in the OT Devices tab of the OT Manager dashboard has been moved to the Operational Technology Visibility dashboard.
- New OT devices discovered
- Inactive OT devices
- OT Devices overview
- Total CMDB OT devices
- Unclassed OT devices
- Unassigned OT devices
- Unmapped OT devices
- OT devices by category
- Supervisory systems
- Control systems
- Field devices
- Computers and servers
- Network Gear
- Industrial IoT
- OT devices by Purdue level
- OT devices by type (Top Level)
- OT devices by manufacturer (Top Level)
- OT devices by criticality
|
| Operational Technology Vulnerability Response |
- OT Vulnerabilities tab data
- The following data that was available in the OT Vulnerabilities tab of the OT Manager dashboard has been moved to the OTVR (PA) dashboard:
- Total OT Vulnerable Items
- New OT Vulnerable Items
- OT Unassigned Vulnerable Items
- OT Vulnerable Items by State
- OT Vulnerable Items by Risk Rating
|
| Opportunity Marketplace |
- Import Project Workspace project information to create an opportunity
- Opportunity Marketplace opportunity owners can create Project Opportunity types by importing projects from the ServiceNow®
Project Workspace.
Note: Creating a project opportunity type by importing a project file is only available to users with both ServiceNow
Project Workspace and Opportunity Marketplace installed. An opportunity owner must have the following roles assigned to them to create a Project type opportunity by importing project details from Project Workspace.
- reource_user
- If you’re assigned the resource_user role, you can be a resource requester.
- sn_ppm_read
- The sn_ppm_read role provides read-only access to the Portfolio, Program, and Timecard dashboards along with the Resources report to the assigned users.
- Select multiple user criteria groups
- Opportunity owners can select multiple user criteria groups from the Who can views this opportunity? field on the Opportunity details page. For more information, see Create opportunities in Opportunity Marketplace.
|
| Platform Analytics experience |
- Migrate more features to Platform Analytics from the Core UI
- Migration scripts are improved to support more features. All migration script improvements are applied automatically on upgrade to content that was previously migrated in compatibility mode.
- Data table configurations are migrated from the Core UI to Platform Analytics data visualizations.
- Dashboard groups are migrated to dashboard categories.
- Pareto charts are migrated.
- List component border changes are migrated.
- Follow/unfollow filter settings are migrated for Lists.
- Use more Core UI features in Platform Analytics
- Several data visualizations have been enhanced to match the capacities in Core UI reports and widgets. The migration script supports these enhancements. Each of these enhancements has an entry in the release notes with links to the product documentation.
- Use the new Box plot data visualization.
- Configure Follow filters per metric on bar or time series visualizations with multiple metrics.
- Sort values by name, report range, and element order on time series visualizations of table data.
- Choose an aggregate or separate view of breakdown elements on time series visualizations of indicator data.
- Select dates from business calendars on time series visualizations.
- Trend by Business calendars in time series data visualizations
- Business calendars are a Trend by option for table data sources on time series visualizations. (Core UI feature gap)
- Use a Fiscal calendar in date filters
- If your instance has Fiscal calendars installed, you can choose relative data ranges from that calendar.
- Export dashboards and data visualizations to PDF and PPT
- Export dashboards and data visualizations to PDF or Microsoft PowerPoint files at will or in scheduled emails.
- Show breakdown elements separately on time series visualizations of indicators
- Show multiple elements in the chart separately rather than as an aggregate value by turning on the Show filter as separate series option. (Core UI feature gap)
- Lock editing on dashboards
- Ensure that only one person can have a dashboard open for editing at one time through the edit lock on dashboards. If you are locked out of editing a dashboard, you see who the current editor is.
- Access indicator record or scoresheet from KPI Details
- Navigate either to the record of the indicator you are exploring or its scoresheet through KPI Details. Appropriate roles are required.
- Export records that underlie an indicator from KPI Details
- With Show records activated in KPI Details, you can export the list of records in one of several formats, either as a local download or as an email attachment.
- Hide axes for bar visualizations
- Control the display of axes on bar charts. On horizontal bar charts, you can hide the y-axis. On vertical bar charts, you can hide the x-axis.
- Cache indicator scorecard data
- Indicator scorecards now support data caching.
- Group by elements more efficiently in data visualizations
- Specify the maximum number of elements in a Group By you want to retrieve through the Max number of groups option. Previously, all elements from the database were retrieved and then sorted.
- Prefetch dashboard layout
- If you have a dashboard component on a page in your own workspace, improve performance by using a preset to configure a data broker that pre-fetches static JavaScript, such as layout.
- Call multiple visualizations together
- For a technical dashboard, if you have multiple data visualizations of the same type calling the same data source, configure a data resource to make a single call for all of them.
- Improvements to time-series visualizations
-
- Simplify identifying specific values on line, spline, area, or step charts through the Show markers option, which displays a symbol at each data point.
- Sort by name, report range, group bucket, and element order. (Core UI feature gap)
- Improvements for visualizations that show multiple metrics
-
- In time series visualizations, provide viewers an alternative group by, where the viewer chooses the group-by value at runtime, for up to 3 data sources. (Core UI feature gap)
- Set whether individual metrics follow filter components on the page or dashboard in both bar and time series visualizations. (Core UI feature gap)
|
| Playbooks in Workflow Studio |
- Change triggers in any playbook
- Edit triggers when you duplicate a playbook, in a variant, etc.
|
| Policy and Compliance Management | |
| Privacy Management |
- Tagging of information object tags
- Use the Data classification field to tag information objects instead of using the tag icon.
- Initiating privacy assessment
- When you initiate a privacy assessment from either an entity or a processing activity, you’re no longer redirected to the Create new privacy assessment form, instead, a new pop-up window appears where
you can specify all the assessment details.
|
| Product Catalog Management and Pricing Management |
- Product Catalog Management changes
- Multiple configurations
- Define child product offerings that can have multiple configurations in configurable opportunities, quotes, and orders. Agents can clone or split a child product offering to create multiple product offering instances. Each
quantity for an offering instance can then have its own unique configuration.
- Transient product offerings
- Define single-use product offerings, such as installation services or consulting services, as transient products that are fulfilled in ServiceNow
Order Management. After orders for transient products are fulfilled, sold product or product inventory records are created but have an Inactive status. Move, Add, Change, Delete (MACD) actions aren't supported
for the sold product or product inventory records of transient products.
- Pricing Management changes
- Configurable pricing plan enhancements
-
- Apply Renewal Adjustment step: This new step determines whether a contract renewal adjustment, either a markup or markdown amount or percentage, is to be calculated and applied. For example, as a pricing admin, you might
want to apply a pricing uplift of a fixed amount at contract renewal. This renewal adjustment step is enabled by default, but you can change or remove it in a custom configurable pricing plan.
- Extension point updates: The ListPriceExtensionPoint, which gathers the data needed to make required adjustments, now includes the adjustment data for contract renewals.
- Volume-based pricing
- Set volume discounts for product offerings based on the product quantity.
|
| Project Workspace |
- Heatmap enhancements
- The resource allocation heatmap displays the resource status, capacity, and utilization, enabling efficient planning and allocation based on availability and workload.
|
| Public Sector Digital Services |
- Constituent Service Dashboard Migration to Platform Analytics
- The Constituent Service Dashboard has been migrated to Next Experience
Platform Analytics. Next Experience is a ServiceNow AI Platform® feature that is active by default when the user loads or upgrades to the Yokohama release. The dashboard migration to Next Experience enables you to visualize historical and real-time process statistics in role-based dashboards, which enable individual stakeholders to make informed decisions. The new dashboard can be accessed by
navigating to .
|
| RPA Hub |
- Changed fields for the Unattended Robot application
- In the Unattended Robot dialog box, the RPA Hub field name has been changed to Instance URL.
- Trigger attended bot processes (attended automations) from the ServiceNow forms in the Workspace experience apart from initiating them from a classic UI or the Attended Robot application.
- Microsoft Software Installer (MSI) compatibility
- Older MSIs that are related to Attended Robot and RPA Desktop Design Studio from the RPA Hub store release versions 7.0.3 and 9.0.0 are compatible and can be used with the current store release version (12.0.X) of RPA Hub. For Unattended Robot, the latest MSI must be installed, as it is not backward compatible.
- However, there are some limitations:
- Any new automation components available in the latest version aren’t available in the older versions. For example, the SSH connector in version 12.0 doesn’t work in older versions.
- Components of the same name with different parameters aren’t backward compatible.
If robot machines use older MSIs than the current instance version, they won't have the new features from later versions. For example, features released after version 10.0 won't work in version 10.0 MSIs. Only features
from version 10.0 are available in that version.
- TerminateByName component behavior change
- The TerminateByName component stops processes or applications only within the current user session.
|
| Regulatory Change Management |
- Overview page of regulatory alerts
- The Overview page for regulatory alerts includes a drop-down menu that enables you to track the progress of a regulatory assessment. Additionally, you can view the counts of completed, open, and overdue regulatory
assessments.
- Home page updates for Regulatory Change Management
- On the Regulatory Change Management home page, within the Tracking section, a new drop-down menu has the Regulatory Assessments or Risk Assessments options. With these options, regulatory change managers can see the number
of open and overdue assessments to help them efficiently monitor the status of their assessments.
- Regulatory assessments in the Tasks pane
- The Tasks pane in the Compliance Workspace now displays all the Regulatory assessments.
- Yokohama Patch 11
- Some Now Assist skills are turned on by default
- The new default behavior works as follows:
- New customers: When you install a Now Assist product, designated skills are turned on automatically.
- Existing customers who are upgrading (starting with Yokohama Patch 11): 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.
- Changes to Now Assist usage measurement
- Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to KB KB2704710: Now Assist Usage - Overview & New Measurement Logic.
|
| Request Management |
- Sorting configuration items in requested item forms
- The list of configuration items (CIs) displayed for the Configuration item field in the Requested item form is now displayed and sorted based on the CI names in alphabetical order instead of sorting by
CI class and then presenting the CI names in alphabetical order within a class. This change means you can determine whether a particular CI is available more quickly.
|
| Resource Management Workspace |
- New resource heatmap view
- The resource allocation heatmap view provides more relevant information such as resource status, remaining capacity, and utilization of resources which helps resource managers to plan efficiently and allocate the resources
based on their availability, bandwidth, and work requirements.
|
| Security Incident Response | |
| Self-service and omnichannel engagement for CSM |
- Manage and view customer-related information and past conversations while interacting with customers via email.
- Receive comprehensive and detailed answers with intelligent search and conversational experiences using Now Assist in Virtual Agent. The search results are synthesized from Knowledge Base articles, Virtual Agent articles, and catalog items with links to the sources. The agent retains conversation context across multi-turn questions, promoting continuity and relevance in
responses.
|
| Service Operations Workspace for ITSM |
- Incident record page changes
- The Incident record page has the following changes:
- The caller card is placed first on the Record information side panel for tier 1 agents.
- The origin card itself is no longer clickable to reduce usability issues with the card and its clickable elements.
- Reference field behavior changes in SOW
- Selecting any reference field in SOW now displays only the recent selection values instead of automatic searching and displaying the results of the field values available in the system. This change increases the
overall performance of the reference fields. By default, this change is enabled. To revert this change, set the Reference search on click (ref_search_on_click) UX page property to
set to true.
- Viewing Assign to me option
- Users with the incident_read role can no longer view the Assign to me option for an incident record.
- Email component issues on SOW Incident
- Email components are now accurately displayed for SOW Incident when the email is selected from the activity stream, stacked view, or email template is applied.
- Resetting filter conditions
- Filter conditions are now reset when switched from one related list to another related list.
- Saving interaction record loads recent tasks
- When a new interaction record is created and saved, the sidebar now loads record Information instead of recent Tasks.
- Problem Management state transitions
- Sections that are configured to be expanded now automatically expand when you transition to a new state, without requiring a page reload.
- GenAI email templates for communication
- Use the GenAI capabilities for composing email with GenAI email templates in all major incident communications. The GenAI email templates are visible in a separate section when the email templates field is selected and the
following conditions are met:
- Any GenAI variable is available in the email templates.
- Now Assist for ITSM is installed and activated.
- GenAI skills are enabled.
- User have the required roles to execute the GenAI skills.
- Close an incident in Resolved state using the itil_admin user role.
- Resize modals on the SRP and list pages
- Ensure flexibility and efficiency by enabling users to resize the modals on the SOW SRP and list pages. This helps in adjusting screen space allocation, enabling multi-tasking, and optimizing content visibility for different tasks and screen sizes.
|
| Service Portal | |
| ServiceNow AI Lens | |
| ServiceNow AI Platform core feature | |
| ServiceNow SDK |
- Version 3.0
- Subcommands replaced with parameters on the auth command
- Configure authentication credentials with the
--add, --delete, --list, and --use parameters of the now-sdk auth command.
- Dependencies command installs type definitions
- Download TypeScript type definitions for Glide APIs and script includes from a ServiceNow instance based on the scripts in your application.
- Build command includes --frozenKeys parameter
- Validate that the auto-generated keys.ts file is up to date for continuous integration (CI) builds by setting the
--frozenKeys parameter to true with the now-sdk build
command.
- Deploy command renamed install
- Install or update an application on a ServiceNow instance using the
now-sdk install command.
- Automated Test Framework Test API supports two-way synchronization
- Synchronize changes to Automated Test Framework tests made outside of source code into source code definitions and back to metadata.
- Table API supports licensing configurations
- Create a licensing configuration [ua_table_licensing_config] to track subscription counts for a table with the licensing_config object in the Table API.
- Table API supports remote tables
- Create a remote table with the scriptable_table property in a Table object.
|
| ServiceNow Studio |
- The App settings icon in ServiceNow Studio used to open a small modal where only a few settings could be updated and the app could be deleted. In this release, the icon opens a Core UI view of all the app settings and related links for the app.
- As of version 27.2.4, the available options at the success page for creating an application changed from Go to app dashboard to View App Details and Create
File.
|
| Software Asset Management | |
| Strategic Planning |
- Changes in planning item forms
- The dates in the Planned start date and Planned end date fields are editable for all planning item types other than Demand and Project planning item types. Also, the
State field is editable for EAP planning items and its child items.
|
| Subscription Management | |
| System Update Sets |
- Application
installations
- You can add specific applications or versions as an app installation and configure to track them in an update set.
|
| Third-party Risk Management |
- Pre-populate responses using questionnaires
- If you have the Third-party risk assessor [sn_vdr_risk_asmt.vendor_assessor] or Third-party risk manager [sn_vdr_risk_asmt.vendor_risk_manager] role, you can enable third-party and engagement contacts to review and update
responses only if necessary by pre-populating questionnaires for engagements and entities with responses from completed questionnaires that are associated with the same third party. The attachment, duration, and signature type
responses are excluded. This feature also helps ensure data consistency and accuracy.
- Microsoft Excel questionnaire template
- Streamline the due diligence process by enabling third-party and engagement contacts to respond to questionnaires using a Microsoft Excel template by downloading the questionnaire as a template, completing it according to the included instructions, and importing the final version into the Third-party portal. This feature update
enhances flexibility by enabling third-party and engagement contacts to provide information outside the third-party portal. Third-party risk assessors [sn_vdr_risk_asmt.vendor_assessor] and Third-party risk managers
[sn_vdr_risk_asmt.vendor_risk_manager] can access this feature and respond to questionnaires on behalf of Third-party and engagement contacts through the Vendor Management Workspace.
- Codes and additional identification information for ICT third-party service providers
- If you have the third-party assessor role [sn_vdr_risk_asmt.vendor_assessor], help ensure compliance with DORA regulations by adding additional code types and a legal name to third-party and third-party engagement records in the digital resilience third-party registers within
the Vendor Management Workspace. Include this information when the legal name of a third party differs from its commonly recognized name, or when you need to record multiple identification codes like a EUID, LEI, or
Country code. When supply chain, assessment, or contract records are associated with a third party or third-party engagement using the EUID code type, all relevant fields will be automatically populated.
- Function types for ICT third-party service providers
- If you have the third-party assessor role [sn_vdr_risk_asmt.vendor_assessor], help ensure compliance with DORA regulations by using Business capability as an additional function type for function records in the digital resilience third-party registers within the Vendor Management Workspace.
- Multiple legal entities making use of the services for contracts
- If you have the third-party assessor role [sn_vdr_risk_asmt.vendor_assessor], add multiple legal entities that are using services as part of a contract record in the digital resilience third-party registers within the Vendor Management Workspace. Including all entities that are using services associated with a contract is essential for maintaining transparency, helping ensure compliance, and enhancing operational resilience.
|
| Threat Intelligence Security Center | |
| Upgrade Center |
- Upgrade Plan enhancements
- Experience a seamless upgrade on your instance with the Upgrade Plan, offering the option to either include or bypass skipped records and customizations during its building.
|
| Usage Insights |
- New custom user property configuration
- An easy way to configure which user-related fields are available to use as filters and in user details. Configured user properties are available for all applications. Previously created custom user properties are no longer
supported and must be recreated in the new UI.
- Country consent policies are set by default to No Consent Required
- Default country consent policies are now set to No Consent Required. If you have previously updated your country consent policies, they will retain the custom setting. Existing users who have set their tracking preferences
will retain their settings. New users will not require consent for tracking unless you update your country consent policies.
- Longer user history
- Detailed data for users and sessions extended to two years.
- Optimized the way metrics are calculated
- Percent time on app and Average duration per page calculations changed compared to the application view in Xanadu or prior releases. Percentage time on app was Percentage time on site in Xanadu or prior releases.
- Client page load and Full page load aggregated in the same visualization
- All performance metrics associated with Client, Network, Page Load, and Server time are aggregated together.
|
| Virtual Agent |
- Yokohama Patch 6
- Test assistant options
- The Test button in the Virtual Agent Designer canvas directly opens up the chat widget.
- Dynamic Translation calls
- For Now Assist, if native translation is enabled, a Dynamic Translation call is only made if an unsupported language for native translation is used.
- Use the new Show links for each record toggle switch to activate links for each record in the output in your Virtual Agent conversation.
|
| Visa Spoke |
-
Visa Resolve Online (VROL) version 25.1 updates
-
Updated the following Visa Spoke actions to align with Visa Resolve Online (VROL) release 25.1 revision changes:
- Submit Fraud Report Request Builder
- Look up Fraud Report Details Response Parser
- Look up Dispute Response Details Response Parser
- Look up Dispute Details Response Parser
- Submit Dispute Questionnaire
- Visa Resolve Online (VROL) version 25.2 updates
- Updated the following Visa Spoke actions to align with Visa Resolve Online (VROL) release 25.2 revision changes:
- Submit Dispute Questionnaire
- Hypersearch Request Builder
- Hypersearch Response Parser
- Create Dispute Pre-Arbitration Request Builder
- Create Dispute Pre-Arbitration Response Parser
- Look up Dispute Response Details Request Builder
- Look up Dispute Response Details Response Parser
- Look up Dispute Pre-Arbitration Response Details Request Builder
- Look up Dispute Pre-Arbitration Response Details Response Parser
- Look up Dispute Pre-Arbitration Details Request Builder
- Look up Dispute Pre-Arbitration Details Response Parser
- Look up Dispute Details Request Builder
- Look up Dispute Details Response Parser
|
| Vulnerability Response Integration with Claroty CTD |
- Updates made for Claroty CTD v5.1
- The following updates were made to support Claroty CTD v5.1:
- There's no limit now on the number of Common Vulnerabilities and Exposures (CVEs) that you can import.
- The Minimum CVSS Score field was replaced with the CVSS V3 Score field.
|
| Workspace |
- Context-based suggestions with @mentions
- Receive suggestions for users with access to the record when using @ mentions.
- Expand all tiles in the Activity stream
- Set a user preference to keep all tiles in the Activity stream expanded across cases and user sessions.
- Access control security model for the Activity stream
- Data filters and access rules provide role-based access control for viewing and editing tables in the Activity stream.
- Multiple records added from the multi-record associator load in the background
- Work on a record while the multiple records that were selected from the multi-record associator are added in the background.
- Attach display text to knowledge base links in the email composer
- Manage your email's appearance by attaching display text to knowledge base links.
- Infinite scroll for lists
- Use the Record List bundle to scroll through lists infinitely without pagination.
- Live updates for lists
- Use the Record List bundle to view live updates on lists without refreshing the page.
- Temporary lists available in the list menu
- Temporarily access personalized lists that are sent to you as links within the My Lists menu.
- Filter for hierarchy in condition builder
- The is within hierarchy field in the condition builder enables you to filter your list within a hierarchy instead of only direct reports.
- AI filter assist
- Convert everyday language into an encoded query with AI filter assist.
|
| Zero Copy Connector for ERP | Yokohama Patch 3
- From the Zero Copy Connector for ERP system form, view detailed system information including machine type, node name, supported database, and
Unicode status.
- Preview model entities before adding to a model
- In the Model Manager, confirm you are adding the correct entity by examining and verifying read table entities before adding the entity to a model.
|