- Release notes
- Getting started
- For administrators
- RPA workflow projects
- Creating an RPA workflow from an idea
- Creating a project
- How to start an RPA workflow
- Managing project files and folders
- Connecting RPA workflows to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- App projects
- Agentic processes
- About agentic processes
- Creating an agentic project
- Process modeling
- Agentic process elements
- Configuring agentic process elements
- Debugging an agentic process
- Publishing, deploying, and upgrading an agentic process
- Solutions - Preview
Studio Web User Guide
Publishing, deploying, and upgrading an agentic process
To publish an agentic process project:
- Open the project.
- Select Publish at the top of the designer.
- In the Publish automation window:
- Enter a name and description for your automation. If you are republishing a project you already published before, you can't edit the name.
- Select where to publish:
- Orchestrator Personal Workspace Feed - The automation is published to your personal workspace and will only be available to you. This is the default selection.
- Orchestrator Tenant Processes Feed - The automation is published to the global tenant feed and will be available to all users assigned to folders that use the tenant feed.
- Select a version. A version is generated automatically starting with 1.0.0 when you first publish, and then incremented automatically every time you republish.
- Click Publish.
You can then access your published agentic process after deploying it in Orchestrator.
- Agentic processes published to the Orchestrator Personal Workspace Feed are automatically deployed in Orchestrator and can be run immediately.
- Publishing to the Orchestrator Tenant Processes Feed requires you to have a Tenant permission for Packages create, or use the predefined Allow to be Automation Publisher role.
- When publishing to a Folder feed you will need to have a Folder permission for Folder Packages create, or use the predefined Automation Publisher role.
To deploy a published agentic process project, navigate to Orchestrator and:
- Select the Orchestrator folder you wish to deploy your project in.
- Navigate to the Automations page and select the Add process button.
Note: We recommend that you have the Allow to be Folder Administrator tenant role and the Folder Administrator role in the folder you want to deploy to.
- Choose the agentic process project you want to deploy from the Package Source Name drop-down menu, followed by the version from the Package Version drop-down menu, and the entry process from Entry point drop-down menu (if available).
- Select Next to advance to the Package Requirements page and provide any package requirements.
- Select Next to advance to the Additional Settings page and finalize the deployment configuration.
- Select Create to deploy your agentic process project.
After deployment, your process is listed in the Processes page. Selecting the
process, then the Edit
button opens the Edit process page, where
you can update the process configuration, requirements, and additional settings.
To learn more about managing processes, see the Orchestrator guide.
- Select the More actions
button on the right of the process.
- Select Upgrade to latest version from the drop-down menu.
- In the Update package version window, select Confirm.
An agentic process uses the same concepts as a robot in terms of permissions. We recommend creating one robot account in the folder where the process is deployed, with the following roles:
- Automation User folder role.
- Allow to be Automation User tenant role.
These roles will have all the need permissions for the agentic process and any other automations, apps, connectors, or business rules.
