Updating & Migration

You are here:
< Back

Updating Designer

The update of the Designer application needs to be performed by your ServiceNow admin and takes around 10-15 minutes. It is a full handsfree update and needs to be performed on all installed instances.

NOTE: The update is available automatically on your instance.
Update for trial installations is not supported by ServiceNow!

Update Preparation

We recommend to backup the following tables by creating an XML export:

  • Class Definitions x_inpgh_des_class_definitions
  • Class Fields x_inpgh_des_class_fields
  • Diagrams x_inpgh_des_diagrams
  • Filters x_inpgh_des_filters
  • Indicators x_inpgh_des_indicators
  • Indicator Breakdown x_inpgh_des_indicator_breakdown
  • Relationship Definitions x_inpgh_des_relationship_definitions
  • Relationship Fields x_inpgh_des_relationship_fields
  • Shapes x_inpgh_des_shapes
  • Shape Libraries x_inpgh_des_shape_libraries
  • Templates x_inpgh_des_templates

You can reimport any necessary backup XML after the user acceptance test.

Update Instructions

To update the application on pre Madrid instances:

  1. Log in to the ServiceNow instance on which you want to install the app.
  2. Navigate to System Applications > Applications.
  3. Click the Update tab.
  4. Locate the Designer app and click Install. The application is automatically updated on your instance.

To update the application from Madrid onwards:

  1. Log in to the ServiceNow instance on which you want to install the app.
  2. Navigate to System Applications > All Available Applications > All.
  3. Search for the Designer app.
  4. Select the version you want to upgrade Click on Update. The application is automatically update on your instance.

Migrating Designer

To occasionally migrate data from one instance to another, you can export the XML data from one instance and import it to another.

This method ensures that all fields and values are transferred exactly. Exporting and importing data in XML files is commonly used for records created in a development instance that must be migrated with the update sets as part of a migration procedure.

Here is the list of typical files required:

  • Class Definitions x_inpgh_des_class_definitions
  • Class Fields x_inpgh_des_class_fields
  • Diagrams x_inpgh_des_diagrams
  • Filters x_inpgh_des_filters
  • Indicators x_inpgh_des_indicators
  • Indicator Breakdown x_inpgh_des_indicator_breakdown
  • Relationship Definitions x_inpgh_des_relationship_definitions
  • Relationship Fields x_inpgh_des_relationship_fields
  • Shapes x_inpgh_des_shapes
  • Shape Libraries x_inpgh_des_shape_libraries
  • Templates x_inpgh_des_templates
  • Cross scope privileges sys_scope_privilege

Designer is fully dependent on the following tables which needs to be migrated, too if configuration changes have been made:

  • Images db_image
  • Relationship Types cmdb_rel_type
  • Suggested Relationships cmdb_rel_type_suggest

Additional configurations done on or in relation to Designer needs to be migrated, too. Those changes should be captured and migrated by UpdatedSets:

  • Field extensions (captured via UpdateSet)
  • Dashboards
  • Reports
  • Workflows