Round-trip Scenarios for 10.x, 11.x, and 12.x Sites - Automate_Studio_Manager - Automate_Evolve - Latest

Automate Studio Manager Migration Guide
Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio Manager
Version
Latest
ft:locale
en-US
Product name
Automate Studio Manager
ft:title
Automate Studio Manager Migration Guide
First publish date
2018
ft:lastEdition
2024-02-16
ft:lastPublication
2024-02-16T10:31:20.160000
  1. Round-trip scripts are “composite” scripts. A script is marked composite if the template contains more than one script information from the same site. The information of the composite is marked only by clicking the download button on the source site.
  2. We recommend migrating single and linked files before migrating composite scripts.
  3. When migrating composite scripts, read the preceding script and check its migration status.

    If it did not migrate (‘errored’), an error message will direct you to migrate that script first.

  4. After the preceding script is migrated, go to subsequent composite scripts from the same site to continue the migration. The composite script migration process examines local storage to identify migration information for the preceding script; this information (including for example the solution name and TeamSpace) is burned into the template.
  5. The local storage offers key criteria for the composite script migration process; as noted in #4 above, data for the preceding script is fetched from local storage. Across machine precedence script migration (from utility) will not help.
  6. Round-trip scenarios and multiple scripts published in templates via non-standard routes (except for the multi-script submissions wizard feature) are not supported. As an alternative, migrate only the latest script and associated latest template. (That script is the only one that will remain published in the migrated template.)

Note: You will not be able to migrate round trip scenario solutions/scripts from Foundation to Evolve when the same template name has been used at the time of submission of these scripts. Error about migrating precedence script will appear. If previous version of Migration utility has been used to migrate the parent scripts, then these will need to be deleted first and then the migration needs to be done again.
  1. All scripts in a composite script bundle are on the same TeamSpace.
  2. Published scripts from other source foundation sites are removed from the template.
  3. Published Connect-only mode scripts are removed (for all templates independent of round- trip scenarios).
  4. Conflict resolution will restrict each template migration if reference scripts do not exist.