Pega Robotics Studio .OpenSpan deployment

Hello everybody!

We are planning to have a centralized repository where all the .openspan automations will be placed. Our idea is to configure our virtual machines to have access to that server in order to execute the corresponding automations. (A scheduled script will be executed in the VM and run the .openspan automatically).

I would like to know if its mandatory to copy the .openspan file in the local machine to run the automation, or if the file could reside in other server and be called from the VM where it is executed.

Thank you for your attention.

***Edited by Moderator Marissa to update platform capability tags****


Keep up to date on this post and subscribe to comments

April 8, 2019 - 5:40pm

The .OpenSpan and .Manifest files are collectively known as the deployment package. This package is intended to be distributed from a central location (either via Robot Manager vis-a-vis the Package Server or via a network location). When you place the deployment package on a network share, it will get checked by Runtime whenever it is started. If you are not using Robot Manager, then placing the files on a network share is actually recommended versus keeping them locally.

November 26, 2019 - 2:14pm
Response to tsasnett

Hi tsasnett...

There Is possible to upload a deployment file to RobotManager without Studio?

November 26, 2019 - 2:24pm
Response to JonathanPereira

No. Studio is required to publish package metadata to Robot Manager. The package itself gets uploaded to the package server and not actually into Robot Manager.

January 15, 2020 - 3:43pm

Hi, We are in a process of defining deployment process for PEGA robotics in a client organization. Is there a way that we can configure azure devops to push the deployment files to respective pega run times.



January 15, 2020 - 5:01pm
Response to UDUGAMAL

You should ask this in a new thread and provide some more specific details about what you are asking.