There are 4 steps involved in exporting an object
Step One: Choose the Migration Package Type
Navigate to the Migration Package screen in the source system. Click
in the Migration Package Export History Grid to create a new export.
Open the Migration Package Type drop down list and choose a value from the list
For more details regarding the different Migration Package Types including information about what will not be migrated with the package click on the below links:
Business Rule - includes referenced components (Maths, Functions, Table Lookups, Variables, Other Business Rules and Multi-Contexts)
Dashboard Layouts - includes widgets and dependencies (prerequisite reports, user report types, and user tables used by these reports)
Landing Experience Dashboard - includes widgets and dependencies (user reports, pre-requisite reports, user report types, and user tables used by these reports)
Merge Documents - includes Merge Documents based on User Reports, E-Signature Documents, and PDF fillable documents.
User Report (include Prereq and Type) - includes User Tables
Widget - includes Reports (prerequisite reports, User Report Types, and User Tables used by these reports)
Step Two: Choose the Object to Migrate
When the Migration Package Type is selected, the second drop down list populates with the objects of the selected type that are available to migrate. If applicable, a note in parentheses will indicate whether the item is a system-level or company-level item. Note - generally, users cannot create a migration package for Equus standard objects (objects that have been delivered by Equus and have an Equus System Code).
Step Three: Enter a Description
Enter a description in the Description field. This description will be listed in the Migration Package Export History grid and will help identify the work in the new environment. Click
Step Four: Generate the Export Package
After clicking
, the export will either generate a string of text in the Export Package (Copy this Code) field or a downloadable file.
When text is generated, highlight the text and copy and paste it into the destination system when exporting the package to the destination system.
A download file will always be created for package types: Dashboard Layout, User Report (includes Prereq and Report Types), User Table and Widget. For other types, a downloadable file may be created if the encrypted script of the migration package or if the package is bigger than 2 MB. Certain parts of the package may not be included as part of the migration package and these are displayed in the warning box.
Next, import the selected object in the target system.
Changing the Size of the Migration Package
To change the size of the package to be smaller or bigger than 2 MB, navigate to the System Preferences screen in power user mode and enter the system code: MIGPACSZMB. Click on the pencil icon to modify the size of the package. Contact your Equus Client Solutions Manager for details about power user mode.
Another way to set the size of the package to be smaller or bigger than 2 MB is through the System Preferences, and choosing "Migration Packages" as the Category from the dropdown field. In this screen, the following can also be updated:
Delete Migration Package after days - set a numerical value for the amount of days it will take before the system will automatically delete the migration package from the Migration Package Export History and Migration Package Import History sections.
Migration Package Export as Code Threshold - Legacy migration packages are exported as a text code if they are below the specified amount (in MB) in this field, and as a package file (.PAK) otherwise. 1 MB is the minimum value for this field, and if a smaller value is entered, the system will default it to 4MB
Migration Package Max File Size - The specified value here will be the limit of the exported migration package file.
