Importing automation package components from your repository to Pega Robot Manager
During migration, you first import an automation package component to Pega Robotic Automation Importer and then you publish it to your repository in the target environment. Finally, you import the package component to the target environment's Pega Robot Manager.
- Ensure that the automation package component is available in the target environment repository. For more information, see Publishing automation package components to a repository in the target environment.
- Ensure that you have the pxPostPackageMetadata privilege that is required to run the pxImportAutomationPackageFromRepo activity.
- Copy the automation package component ID and file name from the target environment repository.
- If you want to export only a specific version of the automation package component, copy the version number from the target environment repository.
Log in to your Pega Robot Manager instance in the target environment.
In the the Dev Studio header, search for and open the pxImportAutomationPackageFromRepo activity.
In the AutomationPackageId field, enter the unique identifier of the package component.The package component ID must match the package component ID on the repository.
Perform one of the following actions:
- To import a single version of the package component, in the AutomationPackageVersion field, enter the version number, for example 2.0.
- To import a package component with all historical versions, leave the AutomationPackageVersion field blank.
In the ArchiveName field, enter the automation package component file name, for example
- Publishing automation package components to a repository in the target environment
An automation package component published in Pega Robotic Automation Importer is automatically relayed to the depository in the original environment. The package component versions are also kept synchronized.