Skip to main content
Question

How to deploy a new AARI process to Production and link it with bots

  • October 30, 2025
  • 1 reply
  • 26 views

Forum|alt.badge.img+1

Hi everyone,

I’m trying to deploy a new AARI process in the Production environment but can’t find clear documentation on how to do it.

My questions are:

  1. How can I properly add a new process to a team in AARI so team members can access it?
  2. When creating the process, how should I link it with the correct Control Room bot(s) — especially if the process needs to call multiple bots?
  3. What’s the correct procedure to promote or publish a process from DEV to PROD in AARI?

Any step-by-step guidance or best practices would be really helpful.

Thanks in advance!

1 reply

Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • October 31, 2025

Hi ​@sufanzada,

 

1. Add a New Process to a Team in AARI

  • Role Required: Co-Pilot Admin (with AAE_Robotic_Interface Admin role).
  • Steps:

                   1. Log in to Automation Co-Pilot (AARI web interface).
                   2. Navigate to Manage > Process Setup.
                   3. Select the process you want to assign.
                   4. Click Edit Process, then:

                              i. Add description/tags if needed.
                             ii. Under Teams, click + to add teams.
                            iii. Select the team(s) and set one as Default.

  • Save changes.

               Tip: If only the default team is assigned, you must add another team before removing the default. 


2. Link the Process with Control Room Bots

  • Create the process in Process Composer:

                   1. Log in as Bot Creator in Control Room.
                   2. Go to Automation > Create new > Process.
                   3. Add Bot Tasks for each bot you need to call.
                   4. Configure input/output variables so AARI forms can pass data to bots and receive results.

  • Best Practice for Multiple Bots:

                    1. Use conditional routing or parallel tasks in Process Composer.
                    2. Ensure all bots are checked in and available in the Public folder before linking.

  • Deployment Settings:

                     1. Under Manage > Process > Deployment tab, choose:

                     2. Default resource or Custom resource (assign device pool or role).
                     3. Enable Pop-up handling for resiliency.
                     4. Assign a default team for request ownership. 


3. Promote/Publish from DEV to PROD

  • BLM handles migration:

                  1. In Control Room, go to Automation > Public > Manage bots > Promote.
                  2. Select bots, forms, and processes to move.
                  3. Include dependencies and packages.
                  4. Provide the target Control Room URL (must be whitelisted).
                  5. Complete the promotion wizard. 

  • Checklist Before Promotion:

                 1. Ensure teams and roles exist in PROD.
                 2. Validate device pools and credentials.
                 3. Test in UAT if possible.