Upgrade Considerations

On this page

For the upgrade procedure itself, see Upgrade a Production Installation.

Before upgrading, review the Upgrade considerations in the Release Notes for changes that apply to your current version.

Backward-incompatible changes the wizard lists

During an in-place upgrade, the wizard may display a Backward-Incompatible Changes page with changes relevant to your database version. Review these warnings before proceeding.

Checks after upgrading

Access and sharing

Review the workspace access of your security roles, including the built-in Administrator role. All Workspaces includes workspaces added later, so check that each role has the intended scope.

If your upgrade converts classic views to Web App views, check that the views you need are available. Converted shared views are visible to every account; their previous role restrictions are not carried over. Review their sharing settings. A view that fails to convert is not copied, and the wizard does not report the failure.

Check the widgets on your dashboards after an upgrade that converts legacy widgets. A widget that fails to convert is left unchanged. For changes that apply to older installations, see the Upgrade considerations in the Release Notes.

Workflow in older installations

If your upgrade converts ticket descriptions and activity details from plain text to HTML and you keep your existing workflow, review any Memo-type virtual fields, parameters, and variables that supply those fields. Those not updated automatically must be changed to the HTML type manually.

For other considerations when upgrading older installations, see the Legacy upgrade considerations.

Customization preservation

The following rules apply to configuration updates imported during an upgrade. The Install Default Workflow option replaces configuration as described below.

What How the upgrade treats it
Work calendars Your existing calendars and their customizations are kept.
System performance, Self Service Portal authorization, and regional settings Not changed by the workflow import.
Self Service Portal settings The workflow import keeps these settings. However, the upgrade replaces the default settings' view configuration and adds missing view kinds to other portal instances. Back up any changes to the default view configuration before upgrading. See Self Service Portal Settings.
Dashboards and widgets Not replaced by the workflow import. Some upgrades include separate changes to widgets; review the Release Notes for your upgrade.
A stock action you disabled Stays disabled.
Workflow parameters The definitions are updated; the values you set are kept.
Services, user groups, and announcements Existing records are kept as you edited them.

An upgrade can overwrite customized workflow forms, templates, and functions. The result depends on whether a component is shared by several actions or embedded in one action, and whether the upgrade updates the component itself or the action that uses it:

  • If the upgrade updates a shared form, template, or function directly, it replaces that component, including your customizations.
  • If the upgrade updates an action, it replaces the forms, templates, and functions embedded in that action. Existing shared components used by the action are kept unless the upgrade also updates them directly.
  • Updating a function replaces its operations and, for a shared function, its parameters. Updating a form replaces its fields, layout, and validation.

Supplied reports follow their own rule:

  • A supplied report that changed in the new version and is not marked as custom is updated in place, including any edits you made to it.
  • A changed supplied report that is marked as custom is kept, and the new version is added beside it with (Updated in version) added to its name.
  • A supplied report that is not yet in the database is added. Only a new detail report gets (New in version) added to its name.
  • Added summary reports, and only those, are filed into a category created for them: New in Alloy Navigator version or Updated in Alloy Navigator version.

A supplied report is marked as custom when you replace its report file with your own .rdl file using Replace. Renaming, hiding, moving the report to another category, or changing its permissions does not protect it from being overwritten during an upgrade.

Workflow changes

For how an upgrade affects your workflow, see Default Workflow Configuration.

During an upgrade, a standard lookup value may be updated. If you renamed it, its original name may be restored.

If a new standard value has the same name as an existing non-system value, the upgrade may add *** to the existing value's name. Both values remain in the database.

Install Default Workflow

Install Default Workflow replaces the existing workflow with the Default Workflow and deletes configuration items, including customizations. Plan to re-create the customizations you need in the new database.

This option is available when you create a pilot database from an Alloy Navigator database. On the Workflow Upgrade page, Keep Existing Workflow is selected by default. An in-place upgrade or an incremental migration does not offer this choice.

When you create a pilot database from Alloy Navigator Express, the wizard clears the configuration and loads the Default Workflow without offering a choice. For more information about the Default Workflow, see Default Workflow Configuration.

Choosing Install Default Workflow first clears the existing configuration, then loads the Default Workflow:

  • Every form, ticket template, e-mail template (the Self Service Portal's included), Recurrent Ticket job, and workflow parameter and parameter category is deleted, whether or not you customized it.
  • Of the workflow actions, triggers, scheduled tasks, functions, and macros, and of lookup values such as statuses, lifecycle stages, types, categories, closure codes, urgencies, impacts, priorities, ticket media, and data segments, only the items marked as system items stay. Your own items and most Default Workflow content are deleted.
  • Every voting-method value is deleted, system item or not.

If an item cannot be deleted, the process skips it and continues.

The Default Workflow restores the stock web views, dashboard views, and security roles. Your dashboards, dashboard role assignments, role memberships, and personal views are kept.

Retired components

Standalone Node.js

The Self Service Portal includes Node.js and does not require a separate installation. If a standalone installation of Node.js is no longer needed by other tools on the server, you can remove it manually. The upgrade does not remove it automatically.