RPA Orchestrator FAQs

RPA Orchestrator is where you run your Bots in production. Unlike RPA Studio (where you design and test your Bots), RPA Orchestrator persists the results.

For more information, see "How Tricentis RPA works".

RPA Orchestrator is available on demand. Please contact us via https://www.tricentis.com/products/robotic-process-automation/rpa-orchestrator.

For information on pricing and licensing, please contact us via https://www.tricentis.com/products/robotic-process-automation/rpa-orchestrator.

RPA Orchestrator offers the following security measures:

• Secure connections. You can configure RPA Orchestrator for HTTPS.

• User management. Only users that have been green-lit by an administrator have access to RPA Cockpit.

• Bot management. Administrators determine who gets to publish Bots, i.e. move Bots into production. Moreover, administrators determine who gets to handle which Bot in production. Users can only view, run, or check Bots that they have been assigned to. If a user is not assigned to a particular Bot, they don't even see it.

• Agent management. You determine which machines execute your Bots in production.

No. To use RPA Orchestrator, you must have a running Docker environment for Windows. Tricentis has no plans for a standalone version.

Yes. RPA Studio is where you turn your business processes into automated processes. In other words, where you design your Bots.

Without Bots, you cannot use RPA Orchestrator.

No. You can work independently of Tricentis Tosca.

Yes. For information on how to do so, see the Developer Guide section of the manual.