Advanced Risk
If you're upgrading from a previous version of
Advanced Risk , you can begin using the
Advanced Risk new
features immediately. All updates to
Advanced Risk are only available in
the
ServiceNow Store .
Note: This upgrade process applies only to applications that
are downloaded to production instances. If you're downloading applications to
non-production or development instances, it's not necessary to get entitlements. For more
information, see
Activate a ServiceNow Store application .
Asset Management
New system properties are added in the
Paris release.
The system property glide.create_alm_asset.async controls whether
assets are created immediately when a configuration item (CI) is created, or are created
after a delay. A delay in asset creation allows large numbers of CIs to be created
quickly. When this property is set to true , assets are created by
a scheduled job that runs every 15 minutes. When this property is set to
false , assets are created immediately.
The system property glide.asset.create_ci_with_ire enables CIs to
be created from assets using the ServiceNow®
Configuration Management Database (CMDB) Identification and Reconciliation engine
(IRE). This property affects CI classes that have an identification rule on serial
number and have no dependent relationships.
The default value of the properties is
true if you are a new
user on
Paris . The default value of the properties is
false if you are upgrading to
Paris from
an earlier release. Before updating these properties, review
Asset and CI management .
Authentication
When you upgrade to the
Paris
release, you must enable a blacklist property to enforce the explicit assignment of
snc_external roles. This property works with the new self-registration feature. The property
glide.security.explicit_roles.enable_internal_user_blacklist must be
set to true by the admin role.
Note: For a new or zBooted instance, this property is already
set to true.
Automated Test Framework (ATF)
Copy and customize quick start tests
provided by the Now Platform® to validate that your instance
works after you make any configuration changes. For example, if you apply an
upgrade or develop an application.
The tests can only produce a pass result when you run
them on a base system without any customizations and with the default demo data that is
provided with the application or feature plugin. To apply a quick start test to your
instance-specific data, copy the quick start test and add your custom data. See Available quick start tests by
application or feature .
Change Management
After you upgrade, note the following:
Choose whether to use the change.conflict.show_conflict_message
property, which enables you to show or hide the scheduling conflict message for a change
request. This property is included with the Change Management - Collision Detector
(com.snc.change.collision) plugin.
Enable and use the
com.snc.change_request.event.state_updated.enabled property to
generate the sn_change.state.updated event when the state of a
Change request is updated. By default, this property is disabled.
Enable and use the change.conflict.consolidated_conflicts
property to generate a comprehensive list of conflicts for an Affected CI when you check
conflicts for your change request.
Cloud Insights
Cloud Insights
release 1.2 is supported on New York , Orlando , and Paris platforms.Paris release: Upgrade Cloud Insights to release 1.2
Cloud Provisioning and Governance
The Cloud Provisioning and Governance application is incompatible
with and cannot be used simultaneously with the legacy v1 Cloud Management
application. You can upgrade to the Cloud Provisioning and Governance (previously Cloud Management ) application from any version of Cloud Management v2,
which was introduced in the Jakarta release.
Configuration Compliance
If you're upgrading Configuration Compliance , the
initial Paris version (10.0) is available immediately in your
instance. Going forward, all updates to Configuration Compliance are only available
in the ServiceNow Store .
Adding or deleting test results from test result groups is
not immediately available when you upgrade and must be added manually.
If you've previously installed Configuration Compliance and want an update from the ServiceNow Store , you
don't need to activate the Configuration Compliance Dependencies (com.snc.vulc_dep) plugin
before you install the Configuration Compliance update.
Application administration is not enabled by default in
Configuration Compliance for upgrades. If you add custom tables that rely on
inherited ACLs, you must recreate the ACLs in that custom table. If you add custom roles or
custom ACLs, and you enable Application administration, retest those roles and ACLs after
upgrading. Ensure that the
assignable by attribute on the roles is set
correctly to enable access to application administration.
Note: Once enabled, Application
administration cannot be disabled.
Integration upgrade information
Configuration Management Database (CMDB)
During upgrade, data precedence rules are matched and then merged
with reconciliation rules, according to discovery sources. Reconciliation rules in the Paris release are updated with discovery source priorities from the
data precedence rules, and the data precedence rules are set as inactive.
Connect Support
If you're currently using Connect Support , you can continue to use it after upgrading. However, Connect Support no longer receives enhancements or non-priority bug fixes. For
details, see the Deprecations section.
If you activated Connect Support
before upgrading but did not use it, your fulfiller user interface defaults automatically to
ServiceNow®
Agent Workspace . You can change the fulfiller interface to Connect Support using the Chat Setup form .
DevOps
To continue using Jenkins integrations after upgrading from
version 1.11 or earlier, install the DevOps Integrations application
from ServiceNow Store applications, and the Jenkins plugin for ServiceNow
DevOps version 1.12 or later.
See KB0745378 to download the Jenkins plugin for ServiceNow
DevOps .
After upgrading DevOps to version 1.12 or
later, also upgrade the DevOps Insights application
from ServiceNow Store applications.
After upgrading the DevOps Insights application to version 1.14, also install the DevOps Insights dashboard using the Solution Library to complete
the DevOps Insights application upgrade.
Starting with version 1.14, unless
previously customized, activate and set the Run As credentials to
System Administrator for DevOps scheduled job
[DevOps] Daily Data Collection to collect daily Insights data.
Emergency Self Report
Starting in version 1.0.9, users can localize
strings with the sn_imt_quarantine.crisisSubmitMessage and
sn_imt_quarantine.openTasksInfoMessage properties, which were moved to the sn_imt_quarantine_emergency_self_report_ui_configuration table. If you didn't change the default English strings, the strings will be localized after you upgrade to version 1.0.9 or later.
Flow Designer
In the
Flow Designer interface, action
numbers now start with 1 and then increment by 1 as you add more actions to your flow.
Legacy action numbering incremented by 1 for each main section and then incremented by .1
for each nested subsection, such as in a
Do the following in parallel flow
logic block. If your flow
actions contain any inline scripts that reference legacy action numbers, you have the option
to automatically update your scripts according to the new numbering method.
Figure 1. Prompt to automatically update action numbers in inline scriptsNote: If you choose not to have Flow Designer automatically update the
action numbers in your scripts, your flows can still run as expected. However, if you make
changes to a flow containing inline scripts with legacy action numbering, you can't save
or publish your newly updated flow.
For more information about new action numbering
in
Flow Designer , see
flow actions .
Governance, Risk, and Compliance
If you're upgrading Governance, Risk, and Compliance products, the
initial Paris versions are available immediately in your instance.
Going forward, all updates to GRC products are only available in the
ServiceNow Store .
If you've previously installed GRC products
and want an update from the ServiceNow Store , you don't need to activate the
Dependencies plugins for GRC products before you install the product
updates.
When you download and install GRC products
from the ServiceNow Store , dependency plugins are automatically activated. For
example, when you activate the ServiceNow® Policy and Compliance Management
product, the Policy and Compliance Management Dependencies plugin is automatically
activated.
If you've previously installed the ServiceNow® GRC : Vendor Risk Management and GRC :
SIG Questionnaire applications, and want to upgrade them to the Paris release, be sure to update GRC : SIG Questionnaire first, because it
will update all applications that use SIG, including GRC : Vendor Risk Management . If you update GRC : Vendor Risk Management first, be sure to manually update GRC :
SIG Questionnaire after the GRC : Vendor Risk Management update
is complete.
HR Service Delivery
If you are upgrading from any release
prior to Kingston and you have customizations that reference script includes,
you might experience Restricted Caller Access (RCA) errors. For more information, see HR Service Delivery upgrade information .
ITOM Optimization
The Cloud Provisioning and Governance application is incompatible
with and cannot be used simultaneously with the legacy v1 Cloud Management
application. You can upgrade to the Cloud Provisioning and Governance (previously Cloud Management ) application from any version of Cloud Management v2,
which was introduced in the Jakarta release.
To correctly discover cloud resources on your
infrastructure, install the May 2020 (1.0.63) or the latest available release of
the Discovery and Service Mapping Patterns
(com.sn_itom_pattern) plugin from the ServiceNow Store .
Investment Funding
After you upgrade, the new release makes the
following changes to your existing investment and funding records:
Business cases in investment records are mapped with that of project and demand
records.
Cost plans and benefit plans associated with project or demand records are mapped to
investment records.
The Viewable by field on the investment form is updated with
the source investment owner.
MID Server
All installation and upgrade packages are now digitally
signed by ServiceNow to verify the packages have not been tampered with. Manually downloaded
installation packages can be verified using the jarsigner tool, which is available for free
with JDK. During an upgrade, MID Server will automatically verify the signature and throw
exception if something wrong. The error will be recorded in the agent log and the MID Server
issue table.
If you have installed your own Java Runtime Environment
(JRE), the upgrade process takes the following actions to ensure that the
MID Server uses a supported JRE (minimum version 1.8.0_231):
If a MID Server is using an unsupported version of the
Java Runtime Environment (JRE) when it upgrades, the upgrade process replaces that JRE
with the OpenJDK bundled with the MID Server
installer.
If a supported JRE is running on the MID Server host, the
upgraded MID Server uses that Java version.
All MID Server host machines
require access to the download site at install.service-now.com to
enable auto-upgrades. For additional details, learn how the system manages MID Server
upgrades.
Only one Windows MID Server
service is permitted per executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder
cannot start. See MID Server fails to start for more information.
For more information about
MID
Server upgrades, see:
Mobile
Customers upgrading from the London release or
earlier can transition from ServiceNow Classic to the new ServiceNow mobile platform. For details on the migration process, see
Migrate from Classic mobile to
ServiceNow mobile .
Customers upgrading from the Madrid release
must migrate their existing ServiceNow mobile applications to take advantage
of the improved features and continue editing within Mobile Studio . For
details on this process, see Migration from Madrid to New York
mobile .
Operational Intelligence
After you upgrade all the Operational Intelligence
ServiceNow®
MID Servers in the MID Server distributed cluster to Paris , restart the MID Servers in the
cluster:
Policy and Compliance Management
If you're upgrading from a previous version of
Policy and Compliance Management , you can begin using the
Policy and Compliance Management
new features immediately. All updates to
Policy and Compliance Management are only available
in the
ServiceNow® Store.
Note: This process applies only to applications downloaded to
production instances. If you're downloading applications to sub-production or
development instances, it's not necessary to get entitlements. Proceed to
Activate a ServiceNow Store application .
If you've previously installed Policy and Compliance Management , you don't need to install the Policy and Compliance Management Dependencies (com.snc.grc_policy_dep) plugin prior to installing the Policy and Compliance Management update.
Starting with version 10.1, you can use the
new policy exception capabilities in Policy and Compliance Management from within the ServiceNow®
Vulnerability Response application. To use this feature, upgrade Policy and Compliance Management before upgrading Vulnerability Response . If you've already
upgraded Vulnerability Response before Policy and Compliance Management , and you want to
use this feature, perform the upgrade procedures again in the correct order.
Project Portfolio Management
After you upgrade, the new release makes
the following changes to your existing records:
The Retain users & resource plan state as confirmed / allocated when
project moves property is set to True by default. If you are upgrading to
the Paris release and have used Resource Management
previously, this property is set to False by default.
If you are upgrading to the Paris release and have configured
the columns in Resource Finder in your previous version, the Detailed View is displayed
by default and the column configuration is retained.
Security Incident Response
If you're upgrading Security Incident Response
directly from the Jakarta or Kingston releases to the New York release (skipping the London release), navigate to , and run the Update integrations to multi domain fix
script. Run this script to enable certain integrations to define multiple configurations.
For example, if you have multiple Splunk
instances, you can create connections and queries that run across sightings searches for
multiple Splunk instances. After you run the fix script, navigate to and deactivate the fix script. Don't run the script more than one time.
Software Asset Management
For information about upgrading from the
Software Asset Management Foundation (com.snc.sams) plugin, see Revert Software Asset Management
Customizations.
Subscription Management
After upgrading to Paris , any unmapped tables will be listed in the Custom Table
Inventory module. Map these custom tables to associate them to a subscription. See managing custom tables
for more information.
Upgrade Center
Upgrade Preview
module The Upgrade Preview module enables you to have an
unprecedented insight to an instance prior to an actual upgrade. You can explore and
preview upgrades to different ServiceNow release versions and see how your instance might
be impacted with your current configurations. The Upgrade Preview utility helps you to
plan, schedule, and prepare for an upgrade. Preview skipped list
prediction Reduce post-upgrade review time by previewing the
records that have been customized and are different from the upgrade version being
previewed and might get skipped due to your customizations in the instance. Upgrade Monitor
module Schedule an upgrade and monitor the status of an
ongoing upgrade using the Upgrade Monitor module. You can also view the upgrade summary
and the list of records causing conflicts in your instance once the upgrade is
complete. Upgrade History
module The Upgrade History module tracks every upgrade
made to an instance. You can also view the complete report of an old upgrade or a recently
completed upgrade version using this module. Administration The Administration module contains properties for
managing Upgrade Center .
Vendor Risk Management
If you're upgrading from a previous version of
Vendor Risk Management , you can begin using the
Vendor Risk Management new
features immediately. All updates to
Vendor Risk Management are available only in
the
ServiceNow Store .
Note: This process applies only to applications downloaded to
production instances. If you're downloading applications to sub-production or
development instances, it's not necessary to get entitlements. Proceed to
Activate a ServiceNow Store application .
If you're upgrading to GRC: Vendor Risk Management
v10.0.2, a new version of the Vendor Assessment Portal (GRC: Vendor Portal v10.0.2) is
automatically loaded as a dependency application. For more information, see GRC: Vendor Risk Management v10.0.2 upgrade details .
Virtual Agent
Migrating Virtual Agent conversation topics and topic
blocks: Conversation topics and topic blocks that you created in previous releases are
fully supported in this release and do not change during the upgrade. After the
upgrade, you can continue to use and develop topics that use Natural Language
Understanding (NLU) or keywords for topic discovery.
Migrating setup topics: Setup topics that you used or customized in earlier releases
are fully supported in this release. After upgrading, you can continue to use your
setup topics as before.
However, starting with this release, prebuilt setup topics are shipped as read-only.
You can duplicate and modify any of these setup topics and your previous setup topics.
To differentiate between the read-only setup topics and your previous setup topics,
the read-only setup topic names have a period at the end of the setup topic name (for
example: Live Agent Feedback. ). When you upgrade, the
read-only setup topics are inactive by default, and your previous setup topics are
displayed to your end users.
Migrating the chat branding configuration from New York or earlier
releases: This release supports multiple branding configurations for the web-based
chat client. When you upgrade to this release, your existing branding configuration
and chat menu (Contact support menu) are preserved as the default configuration.
After upgrading, you can view the default configuration in the Brandings
[sys_cs_branding_setup_list] table (navigate to ). You can also create additional chat branding configurations if your
instance supports multiple customers and brands, as well as customize the chat menu
displayed to users. For details, see Configure chat branding and chat
menu options .
Vulnerability Response
If you're upgrading from a previous version of
Vulnerability Response , the initial
Paris version (10.0) is
available immediately in your instance. All updates to
Vulnerability Response are only
available in the
ServiceNow Store .
Note: This process applies only to applications
downloaded to production instances. If you're downloading applications to sub-production
or development instances, it's not necessary to get entitlements. Proceed to
Activate a ServiceNow Store application .
Upgrade information from version 10.0, or version
9.0 to version 10.3: The process described in KB0819117 to create change requests and use change
management with ITSM legacy Change Management plugins is now fully supported.
Starting with version 10.1, you can use new
policy exception capabilities in GRC : Policy and Compliance Management
from within v10.3 of the Vulnerability Response application. To use this feature, upgrade
Policy and Compliance Management before upgrading Vulnerability Response . If you've
already upgraded Vulnerability Response before Policy and Compliance Management , and you
want to use this feature, perform the upgrade procedures again in the correct order. For
more information, see Allow policy exception requests from
other applications .
Version 10.0: The Vulnerability Group Rules (VGR)
form views have been revised. If you've customized your rules form, the new fields are not
available and your customized version may no longer work to create new rules. Customization
prevents some updates from taking place. Existing customized rules still work, however,
they're displayed on the new form. To use the new form fields after upgrade, see KB0815967 for instructions on enabling the new form.
Version 10.0: If you perform an upgrade or install
to v10.0 and the VI age is not displayed in the Vulnerable Items list view and in the Age
and Age closed fields on active VI (VIT) records in Days/Hours/Minutes (9 Days, 18 Hours, 29
Minutes) format, the Age column is not current in your instance. For more information about
how to resolve this issue after an upgrade, see KB0749231 .
Version 9.0: Ignore some configuration item (CI)
classes by setting the ignoreCIClass
[sn_sec_cmn.ignoreCIClass ] system property. While this
property is present after upgrade, it doesn't work automatically. For upgrade instructions
on how to enable this functionality, see KB0788209 .
Upgrade information from the London
(version 8.0 of Vulnerability Response ) to Paris release: The VR
Setup Assistant module is overwritten with an incorrect URL. When upgrading from Madrid v7.0 to v8.0 Vulnerability Response on the Paris platform, a duplicate Setup Assistant module appears. See KB0749805 to remove the redundant module and fix the incorrect URL
issue.
Paris upgrade information
from any release before
Madrid :
If you've installed a version of Vulnerability Response prior to Madrid , you don't need to install the Vulnerability Response Dependencies (com.snc.vul_dep)
plugin prior to installing the Vulnerability Response update.
If you upgraded from a version of Vulnerability Response before Madrid , your original Overview page becomes the Overview (Legacy) module in the application
navigator. If you created a customized home page overview, the overview is overwritten
by the new reports dashboard. To access your customized home page, Create a new module for your customized home page and add
it to the Vulnerability Response application.
Paris upgrade information
from the
Kingston release and earlier:
Unmatched configuration items (CIs) imported from Kingston
or earlier versions of Qualys and Rapid7 are transferred
and listed in the Discovered Items module during upgrade. However, these unmatched CIs
cannot be reclassified using the Reclassify button. Unmatched CIs
must be reclassified manually. To manually reclassify the CIs, see Manually reclassify unmatched
configuration items from Discovered Items .
For releases prior to Orlando , during upgrade the Vulnerable Item table
is reparented to improve performance. If you have a large number of vulnerable items,
the upgrade process may take additional time. No special handling is needed, however,
stop any Vulnerability Response activities prior to the upgrade and record your
vulnerable item count.
Vulnerability Response integrations
Table 1. Version 10 Integration upgrade information
Integration
Version
Upgrade information to Paris
Qualys Vulnerability Integration for Security
Operations10.0
Retry for API failures such as timeouts
Rapid7 Vulnerability Integration for Security
Operations10.0
Retry for API failures such as timeouts
