- Click Migrate to view libraries based on the type of solution you select. For example, if you select Reference Data solutions, all reference data type libraries on the destination app will be displayed.
Libraries on which you have the Developer role on the destination site will be displayed.
- You can rename the Solution Name from the grid (column name: Destination Name) when migrating the data.
| Migrate Option | Description |
| Overwrite (Optional) |
Unchecked (default): If the option is unchecked and solutions exist on the destination app, the error “Solutions already exist” appears or the solutions are created without an error. Checked: If the option is checked and solutions exist on the destination app, solutions are overwritten without an error (a new version of the solution is created). |
Start Migration
- Click Start Migration to launch a view of the migration displaying file-by-file progress.
- If the migration process does not start for any of the pending files, you can quit (stop) the migration.
- The final view will show the migration status for all the files.
- Click Link for error and warnings to see error and/or warning information for the selected entity.
- If you switch the app, the migration status will be changed accordingly.
- You can apply filters on the displayed columns according to the data you require.
Migration Status
| Migration Status | Description |
| Success | The record has successfully migrated. |
| Error | The record migrated with errors. |
| Migrated with Warnings | The record migrated with a warning. |
Item Count
In the light gray text in the below screenshot, the filtered items count is 3 and the total item count is 4. This is displayed in the format 3 (4).
Solution Migrated with Warning
A macro-based template will be flagged with a warning when the migration is complete.
Migration Mapping
After a successful migration, the data below is displayed. The data corresponds to the migrated record.
| Mapping Field | Description |
| Created by | The user who is logged into the Evolve App to migrate materials. |
| Created Date/Modified Date |
The time when the utility is running with the purpose of importing solutions. |
Delete Feature from Tree View
- This will delete all data from the local storage for the selected node.
- Select the app and click Delete to delete all subfolders within this app.
- Select the Evolve Site URL and click Delete to delete all site data.
- The Delete button is only available for use with subfolders. For example, in Connection node, if you select the node, the delete button is not visible. It is visible only when you select individual folders within the Connection node (such as SAP Connections, Data Connections, or External Web Services).
Refresh from the Tree View
This will refresh data from the Evolve server and the data will be displayed in the grid. Refresh will add the newly added data only; it will not delete or update the existing data in local storage.
| Node | Description |
| Policies/ Groups/ Email Templates/ Solutions | Newly added data is pulled from the Evolve server and is shown in the grid. Data is fetched according to the ID (the Policy ID or the Group ID, for example). |
| Solution Data Libraries/ Name Templates/ File Libraries/ Connections | Newly added data is pulled from the Evolve server and is displayed in the grid. Data is fetched by Item Name (Connection Name, for example). |
Download Functionality when data on the source site has been changed
If you select data from the tree view (“fetch” data) and have not downloaded it, and data on the source site is changed, the fetched data will not be overwritten if you hit Refresh
.
| Entity | Action |
|---|---|
| Policy/ Groups/ Email Templates/ SAP Connections/ Data Connections/ External Web Services/ Solution Data Library /Name Templates/ Solutions |
If data for one of the entities listed in the “Entity” column at left has been changed on the source site (data such as the name, description, or information for any other field) and you attempt to download the content, you will get the following error: “Metadata for the file you are downloading has been changed. Please delete the file from local storage and download it again.” |
| Solutions |
If you create a new version of the solution on the source site and you then attempt to download the content, you will get the following error: “The file you are downloading metadata is changed, kindly delete from local storage and download it again.” |
| File Library | File library data cannot be edited from the site. |
Download Error when deleting the data from the source site
If you fetch data and have not downloaded it, and data is deleted from the source site, you will receive a “Not Found” error when you click Download. This will occur when downloading data for any of the following: Policies, Groups, Connections, Email Templates, Solution Data Library, Name Templates, File Library, and Solutions.
Migrating Solutions without permissions on any library
If you do not have Solution Developer permissions on any library on the destination site to which you want to migrate data, you will receive the error message below when you click Migrate.
Migration Logs
- Migration logs are within a separate menu to the left. They include history for all migrations which used the same instance of the utility executable.
- You can export details to Excel.
- You can apply a filter on the columns according to the data you require.
| Migration Details | Description |
|---|---|
| Status | The migration status (Error, Success, or Warning). |
| Entity Type | The data type (for example, Policies or Groups). |
| Entity Name | The entity name. For policies, the policy name is displayed. |
| Source URL | The URL for the Evolve site URL from which you are downloading data. |
| Destination URL | The URL for the Evolve site to which you are migrating data. |
| Migration Time | The time required to migrate the data. |
| Detail | If you receive errors or warnings when migrating the data, it will appear in the Detail column. If there are no errors or warnings, this column will be blank. |
Key Migration Information
- This migration works for Studio Manager and Evolve for the following elements only: Policies, Groups, Email templates, Connections, Solution Data libraries, Name templates, File libraries, Custom workflow solutions, Forms, and Reference Data solutions.
- Standard Workflows (NDR, 1-step, and 2-step) are not within the scope of the migration.
- Only solutions with production status are migrated. Solutions with rejected, in-review, or archived status are not downloaded to the local storage utility.
- Only the latest version of the solution is migrated – in tandem with the associated latest template. Once metadata and contents from the source have been downloaded to local storage, hitting Refresh will not overwrite information. Instead, hitting Refresh will add new entries.
- Datafiles (templates submitted as a datafile) are not migrated.
- Users are not picked when exporting and importing Groups from Windows to a SAML setup. Users are identified by their identity and both authentication systems will have discrete identities for the same username.
-
In the workflow, the form gets stuck when a Webservice is executed in a swimlane where no user is assigned .
Example: If you do not have Username assigned to the swimlane Warehouse then the Webservice (Winshuttle Update) for Process Material Determination cannot be executed. This happens regardless it is indicated that the script should be executed by system runner or not. This behavior is different from Foundation. In foundation there is a key WinshuttleUpdateLegacyOperation, if its set to true then the workflow get completed when no user is assigned to the swimlane. However this is not available in Evolve. In Evolve, Object Reference not set to an instance of an object error gets displayed when you click Save and Route button for the form, if no user is returned in the swimlane. - If a user migrates data from one SAML set-up to another, user credentials from the first
log-in to the source site will be picked by the destination site as well.
- If the source and destination logged-in site or the User are the same, the user credentials used on the source site will be used on destination site.
- If the source and destination logged-in site or the User are different, do the following: Sign- in to the source site, download the contents, and close the utility to migrate the data with the different credentials. Then, relaunch the utility and log in on the destination site with the required credentials and migrate the same.
Additional Details
- Multi-script solutions are available.
- Supporting files for all solutions are migrated along with each solution.
- You can migrate data from one set-up to another.
- You can migrate data from one app to another app within the same set-up.
- You can migrate data from a Windows to a SAML set-up.
- You can migrate data within a localized set-up.
- Template formatting and macros remain the same when you migrate the solution from the utility.
- Composite scripts can now be migrated from one Evolve environment to another Evolve environment" or "Support migrating scripts with round trip scenarios (having Qsq and Txr scripts), template having more than one published solution.