Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Upgrade and migration tasks by application or feature

Upgrade and migration tasks by application or feature

Complete the upgrade tasks where necessary to prepare an application or feature for the upgrade process, and complete appropriate migration tasks after the upgrade to protect your data and customizations from changes to the system.

Changes to applications and features

Application or feature Details
Change Management If you upgraded from a release prior to Geneva, you must update old state labels to new state labels after you activate the Change Management state model.
Email configuration Starting from the Geneva release, the email accounts plugin is active. Email administrators need to set up their organization's POP3, SMTP, or IMAP accounts through the Email Account form, rather than email properties. Existing properties for accounts are migrated to email accounts during the upgrade to Geneva. For details, see Email setup.
Event Management During an upgrade to the Geneva release, a script converts and moves Event Management rules and events for the release. Even though this script runs automatically, there are additional upgrade tasks that you may need to complete after the upgrade. In addition, the following actions are also affected in Geneva:
  • Import rules and events
  • Review imported rules for Event Management
  • Create a manual service
  • Import a business service as a manual service
  • Update manual service relationships
For details, see Upgrade tasks for Event Management
Field Service Management Mobile The plugin (com.snc.work_management_m) automatically installs or upgrades the Field Service and Mobile UI plugins.
Human Resources
  • The Human Resources Service Management Service Management: Employee Change plugin was merged into the Human Resources Service Management Service Management: Core plugin.
  • After the upgrade to Geneva, employee change catalog items and workflows will be installed in your instance, even if you did not activate the Employee Change plugin in Fuji.
  • The [hr_change] table is merged with the [hr_case] table. All HR cases and changes are placed in the [hr_case] table and the [hr_change] table is removed. Any customizations you made to either table are applied to the [hr_case] table.
  • The HR Catalog has been upgraded with a number of new HR catalog items.
  • HR Portal is a new module in the Self-Service menu.
  • Geneva introduces updated and new HR templates.
  • Only active Assignment Rules are preserved during a Fuji-Geneva upgrade. For details, see Human Resources upgrade information
Knowledge Management

Knowledge Management has changed with Knowledge v3, which is enabled by default for all instances. For migration information, see Knowledge Management v3 migration.

Some of the key differences between Legacy Knowledge and Knowledge v3 are:
  • Multiple knowledge bases (instead of one knowledge base)
  • Separate customizable workflows available for each knowledge base (instead of a single lifecycle shared by all articles)
  • Category structure that supports any number of levels (instead of a two-level organizational structure using Topic and Category)
  • Permissions defined per knowledge base and article, using user criteria (instead of per article, using roles and ACLs)

For additional upgrade considerations, see the links under Migrate.

Legacy custom Discovery identifiers Custom identifiers created in a prior release must be converted to CMDB identifier rules after an upgrade to Geneva to use the new unified framework. When you upgrade to Geneva, your scheduled discoveries can continue to use the identifiers they were configured to use, including any custom identifiers you have created. You can use the CMDB identifiers provided with the Geneva release for new Discoveries or continue to use the legacy identifiers.
MID Server
  • To ensure that your MID Servers can upgrade successfully, run a series of manual tests for free disk space, access to the download server, and file permissions on the MID Server host. For details, see Test the MID Server before an upgrade.
  • MID Servers that exist prior to upgrading to Geneva are automatically validated to avoid interrupting automation tasks that such servers may be performing.
    Important: After all MID Servers have been upgraded to Geneva or higher, complete the post-upgrade steps listed in the Workaround section of KB0597396.
  • In Geneva, the MID Server can run SSH commands using either the J2SSH client or the proprietary ServiceNow® SNCSSH client. When you upgrade from Dublin or earlier, the MID Server property that controls the SSH client selection is not active in your upgraded instance, and the MID Server will use the J2SSH client by default. To enable the SNCSSH client, you must add the MID Server property and set it to true. Instances upgraded from Eureka or later have the SNCSSH client enabled by default, and no configuration is required. For details, see MID Server properties.
OAuth email authentication OAuth 2.0 support is available starting with the Geneva release.
  • The OAuth implementation supports IMAP and SMTP accounts only.
  • POP3 is not supported.
  • OAuth 1.0 is no longer supported.
You must activate the Email - OAuth support for IMAP and SMTP plugin to use OAuth with email. If you upgrade to Geneva or later and are already using OAuth 1.0, activate the plugin again.
REST Table API version differences Versions v1 and v2 of the Table API are available. Version v2 is available starting with the Geneva release. For details, see KB0551763.
Service Catalog In Geneva, the Service Catalog UI changed from UI11 to UI15.
User interface For upgraded instances, administrators may need to activate UI16, the User Guide plugin, and/or the Checklist plugin. For details, see the User interface release notes.

Changes to activities, identifiers, and tables

Type Product Details
Orchestration activities (deprecated) Deprecated activities for Exchange, Active Directory, and PowerShell. Orchestration activity packs for Exchange, Active Directory, and PowerShell replace activities by the same name available in releases prior to Geneva. If you have a workflow created in a previous version that uses these deprecated activities, your workflow will continue to work normally after upgrading to Geneva.
Reactivate a deprecated activity Orchestration activities that were converted to activity packs in the Geneva release are deprecated for upgraded instances but can be reactivated for use in new workflows.
Run SCP activity This activity is deprecated in the Geneva release and is not available for use in new workflows. If you have a workflow created in a previous version that uses this activity, your workflow will continue to work normally after upgrading. The custom Secure Copy activity replaces the Run SCP activity in the Geneva release.
Discovery identifiers In the Geneva release, identifiers for new and existing discoveries are completely replaced for new ServiceNow instances with CMDB identifiers from the CMDB Identification and Reconciliation framework. Instances without Service Mapping that are upgraded to Geneva can still use the legacy identifiers for existing and new Discoveries. Both identifier versions are available in these instances, but only the legacy identifiers are used.
Planned tasks Planned Task_v2 plugin If the Planned Task_v2 (com.snc.planned_taskv2) plugin is active when, the system adds the Task column to the Planned Task [planned_task] table. The Task column is of type Composite Field, and stores the Short Description and Number of the task. During the upgrade, the system updates all records in the Planned Task table to add a value for this column. Expect to see a new date in the Updated column for each task in the system.
For detailed, product-specific upgrade information, refer to the following documentation: