After exporting an object, the next step is to import the selected object to the target site.
Navigate to the Migration Package screen in the site that will receive the object (target system).
Click
in the Migration Package Import History Grid to create a new import.
Migration Package Types with Components
These include Business Rules, Dashboard Layouts, Landing Experience Dashboards, Merge Documents, User Reports (include Preq and Type), User Tables and Widgets.
Navigate to the Upload File tab to upload the generated downloadable file.
Click
and choose the appropriate file.
Click
After Uploading the file, click
to open the Migration Package Data Decisions page.
The Migration Package Data Decisions page shows a list of records included in the package. Each prompt on the page appears as its own collapsible sub-section. Prompts that have been resolved are collapsed by default and those that require a user response are expanded. To view the details of a resolved prompt, simply click on the chevron to expand the sub-section.
Provide a response to any prompts requiring action. Click
to save and check for any remaining data conflicts.
An example of a prompt requiring action:
If a record with the same name or system code already exists in the environment, the user will need to decide whether to use the existing record, or to insert a new record. They will need to enter new identifiers (name and system code) for the new record. The system code cannot begin with "EQ".
Note - For Business Rules, currently the system prevents you from creating a business rule with the same name as the existing business rule in the target system regardless of whether it is a system or company level business rule. The same applies to business rules components. The logic to validate unique object names by company when importing migration packages will be addressed in the future.
A progress bar is shown whilst the package is being reanalyzed. The Migration Package Data Decisions page appears once the reanalysis is complete. When all conflicts are resolve, click
When the report is successfully migrated to the destination system, click the link in the Created Object field that reads Navigate to [Object] to view the imported object in the target system.
Errors that occur during migration are specific per Migration Package Type and will be listed at the top of the screen.
Migration Package Types
These package type are types without components. These does not includes Business Rule, Dashboard Layout, Landing Experience Dashboard, Merge Document, User Report (include Preq and Type), User Table and Widget
When the migration package generates a text string, paste the copied code from the export record into the field in the Paste Code tab in the Migration Package Import grid and click
.
Wait for the inspection process to finish and then enter additional information on the Migration Package Import screen. Replace “Equus Script” in the User Name field with the user name of who completed the import so that the object record will carry this information in its “Created By” and “Last Updated By” timestamps. Click
to continue.
Similar to Migration Type with components, it will generate a link in the Created Object field that reads Navigate to [Object] to view the imported object in the target system once done.
Things to Note
Equus recommends that all users review and test the created object to ensure accuracy - just because a Migration Package was successfully applied does not mean the created object is accurate.
Some objects can be migrated at a company level or a system level. Enter the target system Company ID in the Target Company ID field to create the object at a company level. Enter 0 in the Target Company ID field to create the object at a system level.
All objects migrated using the Business Rule, Dashboard Layout, User Report (include Preq and Type), User Table and Widget migration package types will carry "Equus Script" in its “Created By” and “Last Updated By” timestamps. There is no option to edit this during the migration process.