Requisitos previos

Maestro is based on Studio Web. To find out what are the requirements for using Studio Web, see the Automation Cloud System Requirements.

Use this checklist to verify your environment is ready for Maestro. It covers tenant enablement, user roles and app permissions, and Unattended licensing across tenant, machine template, and folder. Missing any item commonly results in pending jobs or a disabled Open in Process Mining button.

• Your tenant has Unattended robot runtimes allocated. Read more in the Managing your licenses chapter.
• At least one user or Robot account is enabled for Unattended and assigned to the tenant (and added to the target folder). Read more about Unattended robot setup / Robot accounts and Managing robots.
• Your folder has a Machine Template with production Unattended Runtimes assigned. Read more about machine templates.
• You have the following permissions in the Orchestrator folder where the Maestro process is published:
  • Processes.view and Processes.edit — to view or edit Maestro processes.
  • Jobs.view and Jobs.edit — to view or edit process instances (jobs).

    Alternatively, equivalent permissions can be granted at the folder level. Read more about Default roles and permissions.

• You need the PM Developer role only to edit data transformations in the auto-created Process Optimization app. Existing Maestro permissions will allow you to see the Optimize tab and have access to the Process Optimization app.
• Process Mining is enabled on your tenant. Read more on Enabling the service in Automation Cloud.
• To edit data transformations in the auto-created Process Optimization app, you need the Process Mining Developer role assigned. Existing Maestro permissions will allow you to see the Optimize tab and have access to the PO app. Refer to Setting up the users for more information.
• You have Edit data, Edit dashboards, and View permissions for the Process Optimization app in Process Mining. Read Managing access for Process Mining apps for more information.