Import process dependencies

When you import an AARI process, you might encounter some issues where the import might not work as intended. This topic shows you the scenarios for you to import successfully.

Overview

For these scenarios, a Parent process has dependencies with a Child process and Test form, and needs to import from Environment A to Environment B. To goal is to successfully import from Environment A to Environment B.

Parameters

Parent process uses Child process and both uses Test form in Environment A.
Export Child-only zip file that contains Child process and Test form.
注： You have to manually export the proper files.
Export Parent-only zip file that contains Parent process and Test form.
Export Parent-and-Child zip file that contains Parent process, Child process, and Test form.

Scenario A (Best case)

Environment B has no files.
Import Child-only zip file into Environment B, files of Child process and Test form will now exist in the repository.
AARI receives a bulk import event of Child process and Test form files, and a new process called Child Process is successfully created..
Import Parent-only zip file into Environment B, files of Parent process and Test form will now exist in the repository.
AARI receives a bulk import event of Parent process and Test form files, since Child Process exists in AARI, then Parent Process is successfully created.
Your import is successful as the Child Process and Parent Process are created in AARI.

In this scenario, the import from Environment A to Environment B was successful as the Child-only zip file was imported before the Parent-only zip file, therefore the Child Process and Parent Process was successfully created in AARI.

This is the best case scenario for a successful import.

Scenario B (Conditional Case)

Environment B has no files.
Import Parent-only zip file into Environment B, files of Parent process and Test form will now exist in the repository.
AARI receives a bulk import event of Parent process and Test form files, because Child Process does not exist, then this failed to created a Parent Process.
Import Child-only zip file into Environment B, files of Child process and Test form will now exist in the repository.
AARI receives a bulk import event of Child process and Test form files, and a new process called Child Process is successfully created.
Import Parent-only zip file again with Overwrite existing files into option selected to Environment B, files of Parent process and Test form will then overwrite in repository.
AARI receives a bulk import event of Parent process and Test form files, since Child Process now exists in AARI, then Parent Process is now successfully created.
重要： If the Overwrite existing files into is not select, then no bulk import event is generated because files of Parent process and Test form already exists in repository, therefore Parent Process cannot be created in AARI.
Your import is successful as the Child Process and Parent Process are created in AARI.

In this scenario, the import from Environment A to Environment B can fail if the Parent-only zip file was imported before the Child-only zip file, as the Parent Process can only be created if the required dependencies from the Child Process exists, and since Child Process did not exist in the repository, then Parent Process could not be created.

In order to workaround this issue, the user can import the Parent-only zip file again with Overwrite existing files into option selected to overwrite the existing repository, only after the Child Process was created, to successfully create Parent Process. This is a conditional success, only if the Overwrite existing files into option was selected by the user, if this option was not selected then the Parent Process cannot be created.

To avoid this issue, the user should use Scenario A for a successful import experience.

Scenario C (Worst case)

Environment B has no files.
Import Parent-and-Child zip file into Environment B, files that contains Parent process, Child process, and Test form will now exist in the repository.
AARI receives a bulk import event of Parent process, Child process, and Test form files. However, due to the fact that the Parent process and Child process relations are not known from the bulk import event, the Parent process might first be processed. Since the Child Process does not exist, then this failed to created a Parent Process.
Your import failed as the Child Process and Parent Process were not created in AARI.

In this scenario, the import from Environment A to Environment B failed since when the Parent-and-Child zip file was imported because the bulk import event does not understand the relation between Parent process and Child process. The the bulk import event might process the Parent process before the Child process, which means the Parent Process cannot be created as the Child Process does not exist, therefore no new process is created in AARI.

To avoid this issue entirely, the user should use Scenario A for a successful import experience.

Automation 360