You can set up the deployment settings for processes or bot tasks in Automation Co-Pilot.

When setting up deployment settings for processes or bot tasks, follow these best practices:

Always check that the role/team exists in the environment, especially when moving from development to production.
Use Pop-up handling to maintain high resilience in dynamic user interfaces.

Procedure

Navigate to: Manage > Process in the Control Room interface.
Select a Process: Choose the process you want to set up from the Process Setup page.
Click the Deployment tab to see and change deployment settings.
In the Process deployment resource section, choose from these options:
- Default resource: Uses the assigned run-as users and device pool.
- Custom resource: Lets you assign a specific role. Click Choose... to assign a role when using the custom resource.
In the Deployment type section, decide how the bot will run:
- Run on pool of device: Runs on any available device in the pool. It overrides the user's default device.
- Run only on default device: Runs only on the user's default device. Make sure the Bot Runner owns the device; otherwise, it might not work if the device ownership is shared or missing.
Default assigned role/team: Choose a default role or team that will be responsible for the requests created by this automation.
In the Resiliency settings section, for Pop-up handling, you can choose to Ignore unexpected pop-ups (enabled by default). This helps prevent execution failure by telling the bot to skip unknown or unexpected pop-up dialogs during run time, which improves automation stability.

Note:
This is especially useful for bots triggered via Automation Co-Pilot where environments can vary.
After configuring all necessary settings, click Close to save and exit.

Use Case: Streamlining Finance Approvals with Resilient Automation Deployment

Use Case Overview: This use case shows how to set up deployment settings in Automation Co-Pilot to make a process more resilient and ready for enterprise-use—especially for Co-Pilot-triggered automations in important departments like finance.

For this use case, the Global Financial Services Corp wants to automate the multi-step finance approval process (Finance_Payment_Approval) triggered through Automation Co-Pilot. This ensures smooth bot execution even with UI inconsistencies (like pop-ups).

Business Challenge: The finance team often faces problems with:

Unattended bots failing due to unexpected pop-ups from browser or application updates.
Ensuring that the right teams (for example, finance_role) consistently receive all request assignments.

Configuring the Deployment Settings: The Co-Pilot Admin sets up the deployment for the Finance_Payment_Approval process using these steps:

Process Deployment Resource: Chooses a Custom Resource and assigns the bot to the finance_role to ensure proper run-as and execution privileges.
Deployment Type: Selects Run on pool of device to spread the load across available Bot Runner machines and improve scalability.
Default Assigned Role/Team: Sets finance_role to automatically route Automation Co-Pilot requests to the correct user group without manual reassignment.
Resiliency Settings: Checks Ignore unexpected pop-ups to stop automation from failing when unexpected dialogs appear (like software update prompts or JavaScript alerts).

Use Case Outcome:

Increased resiliency: Bots now complete executions even when there are UI interruptions.
Operational efficiency: Reduces manual interventions and troubleshooting overhead.
Team alignment: Ensures the finance team owns all tasks and requests generated from the process.

Automation 360

Configure deployment settings for process or bot task