Follow these instructions to Package your Integration, ready for migration between ServiceNow instances.
How to package and export an Integration ready to be imported to another instance:
In Unifi Integration Designer, navigate to and open < Your Integration >.
Click the 'Integration' icon to open the Details page.
Click Package.
Confirm by clicking Package.
Notice: the modal tells us how many records were processed and the name of the Update Set that was created (the integration name prepended with the date/time).
Copy the name of the Update Set.
Click Done to close the modal.
Navigate to the downloaded Update Set and Show in folder*.
Congratulations! You now have the Update Set containing the complete Integration available to be imported to your other instance.
You can find more information on how to Load customizations from a single XML file in the ServiceNow Product Documentation.
The Package Integration modal is displayed.
Unifi packages the Integration into an Update Set which is automatically downloaded.
The Integration Package Worker modal is displayed.
*Example shown in Chrome. Other browsers may vary.
Then rename the file (using your Update Set name in order to easily identify it when uploading to the other instance).
This guide will demonstrate just how easy it is to package up all the elements of an integration so that it can be migrated between ServiceNow instances - 1-click easy!
We are very pleased to be demonstrating this exciting feature in Unifi which makes moving Integrations between instances simpler and easier than ever.
This document will guide you through the Packager feature. It will demonstrate how straightforward and efficient the task of moving your Integration can be.
Prior to the release of this feature we recommended that you build your Integration in its own Global Application in order to facilitate moving integrations between instances as efficiently as possible. This was the best method available using OOTB native ServiceNow functionality.
As good as that method was, there were issues to overcome when migrating integrations that belong to the same Process. There are a few records which are shared by multiple integrations (Trigger Business Rule, Web Service & Process - one per Process) and so the application/integration being migrated may or may not contain one or more of those records - depending on which application scope they were configured in. They may have had to be migrated separately.
This feature solves that problem. The Packager will pull together all of the relevant records and place them in an Update Set ready for migration.
NOTE: The ServiceNow System Administrator (admin) role is required to see the automatic download and view updates in the Update Set (and to select Application Scope - if required).
We will demonstrate packaging the Integration configured in the Bidirectional Incident Guide so that it’s available to import to another instance.