Can we create a product in Pega to deploy Automation Package from dev to test.

Can we deploy automation packages by creating a product file of (Data-Robotic-AutomationPackage) class instances including DeploymentLevel, Version and Config from dev to Test.

I am trying to move the above mentioned class instances. Is it correct practice? If so, is their anything else that we need to capture as part of the product file.

I am aware of deploying the package through Studio and then about Robot Manager. But want to know if done through Pega what all needs to be included.

Version - Pega 8.1 and Robot Manager 6.1(it was upgraded from 5.1 to 6.1).

***Edited by Moderator: Lochan to update platform capability tags***


Keep up to date on this post and subscribe to comments

September 10, 2019 - 10:21pm

Robotics product doesn't consider or support it as a best practice to move product files for robotics package references. You should point the robotics studio/studio plug-in to appropriate Robot Manager instance when deploying the package. You can use the same package server across the environments as the version selected will be the one pulled by runtime. 

September 12, 2019 - 6:02am
Response to Rushabh Shah

We have 3 environments - Dev,Test and Prod. We have Robot Manager instances in each of it (it's not one Robot Manager in all 3 environments). Single Robot Manager can publish to all 3 environments but we have 3 Robot Managers and we want to move the solution from dev to test to prod.

How to achieve that.