b4800617-33aa-4b32-a55b-25e1baebe6e6.png

UiPath’s vision for the “Automation First” era has led to the addition in its market-leading Enterprise RPA Platform of dedicated official out-of-the-box IT Automation capabilities that empower all co

IT Automation

We were founded in 2005 in a tiny apartment in Bucharest, Romania as DeskOver.

Fittingly, it was a customer who, in 2012, first saw the immense possibilities for us in the fledgling RPA market. Our desktop automation product launched in 2013. In 2015, we introduced our enterprise platform along with our new name.

Today, UiPath is the fastest-growing enterprise software company in history with scores of offices, thousands of employees, partnerships with the world’s best consulting and BPO firms, a **500,000-strong developer community**, and **5MM+ robots at work** in over **5,000 global enterprises.**

Our mission is to deliver the leading Robotic Process Automation platform to our clients for an automation first mindset.

We build software robots that automate repetitive processes. Our software robots take on the tedious, mind-numbing work and free people to do the more stimulating, creative work worth doing.

But no matter how much we’ve grown, one thing hasn’t changed. We’re still building a company we love to work for

22ac2b39-8e69-4be8-8c56-879cf6d99177.png

82b8b1fb-5ebd-4949-99b1-bef87be0f814.jpg

Product Management & Strategy, Engineering

ab893b62-0d74-4c0d-b883-f7b2e759ac96.zip

The Robots Auto Scaling solution is implemented with the help of the official UiPath IT Automation activities - they empower us to automate use cases from all areas of our IT Ecosystem, in both on-premises datacenters and public clouds.

  

As part of the auto-scaling process, the robot machines are started / stopped automatically as a function of:

  

1\. Defined Scaling Strategy

*   _hot_ Robots count - their machines are always running
*   _cold_ Robots count - their machines will be allocated/deallocated dynamically

2\. Client’s Current State:

*   Jobs (pending, running, completed, stopped, faulted)
*   Robots (available, disconnected, busy)

  

**Solution Components**

  

1\. Client Tenants – Orchestrator Webhooks

The managed clients need to have configured in the Webhooks area the url associated with the Webhook Receiver’s endpoint for the events job. created / completed / faulted / stopped. These events act as triggers for the autoscaling process and they are processed in bulk, to minimize concurrency risk for servers start / stop operations. 

  

2\. Database

The SQL Server database with the client Orchestrator acces data + AutoScaling Strategy robot counters can be deployed anywhere and it only contains the Tenants table (sql create script provided). The connection to the DB is done with the UiPath.Database activities – the connection string is retrieved from the TenantsDbConnectionString text Orchestrator asset (from the Management Orchestrator).

  

3\. Webhook Receiver. Webservice / Function

This component consists of minimal code that is designed to receive events, parse their data and forward them to the Management Orchestrator as new queue items.

  

4\. Management Orchestrator

Most of the RAS solution items are to be configured in an Orchestrator tenant, in a dedicated folder: Processes (ProcessQueueItems, ..), Assets (for DB connection, infrastructure access), Queue + Job Trigger (on new item added). The RAS solution can be deployed in the same Orchestrator tenant as one of the managed clients, as long as it is configured in a folder that is not associeted with a client from the DB.

  

  

**Process Flow. Event Driven**

  

One deployment of the RAS solution can perform autoscaling for multiple clients at the same time – this is possible by leveraging the Orchestrator’s capability to emit job events via webhooks. The job events that are incoming from the managed clients are received by a small web-service / function and forwarded to a Queue in the Management Orchestrator for processing.

  

As part of the processing step, a _ProcessClient_ job connects to the Database and tries to identity the client of an event in the Tenants table - if found, the information from the selected row has the client Orchestrator API acces data + the scaling strategy for the client’s folder or folder+environment.

  

The processing job connects to the client’s Orchestrator and retrieves its current state (jobs running/pending, robots available/disconnected/busy). With all the data available, the job will evaluate the state + scaling strategy robot counters, selects the impacted robot machines and proceeds to apply the neccesary actions (start / stop server).

  

**Process Flow. Scheduled (pooling)**

  

This mode doesn’t require any of the job events related RAS components (webhooks, events receiver service, queue): the autoscaling process is triggered periodically (scheduled start at each 5+ min), according to a specified scheduled processing job (1 for each client DB entry).

  

  

**Notes**

*   The current version works with classic folders and can allocate/deallocate robot machines from Azure, AWS, VMware, Citrix 
*   Next releases will work with modern folders too and will add support for Hyper-V and Google Cloud

UiPath Robots Auto Scaling (RAS) is a workflow based solution that helps optimize IT Infrastructure costs by making RPA Deployments run more efficiently.

f0330a50-ad19-42bf-ba7a-0d110cb153b9.PNG

640e25fe-8f8c-479d-82b1-8d2fd25d57e6.PNG

deeede2a-e0c7-4dcc-b43d-7ef7750d075f.PNG

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Visual Basic

939c76a9-f823-4fd8-b69f-115366fe9a1c.pdf

3b4ae95f-685c-4704-927b-5c8190366b6f.pdf

f3ad2e2a-5f70-4553-b4a6-eea3702b4063.pdf

d2fa89ef-c151-4a79-8d42-3d6180c184b6.zip

49c5e832-3c7d-44b9-9c11-ec1360deff3c.zip

d8794e15-11a0-4404-947f-d236103073bf.zip

fb882b8d-17fe-476d-b18e-3601b8a70ad3.zip

a55aa696-a919-40ed-9e27-309e6ba94db1.png

The Robots Auto Scaling solution is implemented with the help of the official UiPath IT Automation activities - they empower us to automate use cases from all areas of our IT Ecosystem, in both on-premises datacenters and public clouds.

  

As part of the auto-scaling process, the robot machines are started / stopped automatically as a function of:

  

1\. Defined Scaling Strategy

*   _hot_ Robots count - their machines are always running
*   _cold_ Robots count - their machines will be allocated/deallocated dynamically

2\. Client’s Current State:

*   Jobs (pending, running, completed, stopped, faulted)
*   Robots (available, disconnected, busy)

  

**Solution Components**

  

1\. Client Tenants – Orchestrator Webhooks

The managed clients need to have configured in the Webhooks area the url associated with the Webhook Receiver’s endpoint for the events job. created / completed / faulted / stopped. These events act as triggers for the autoscaling process and they are processed in bulk, to minimize concurrency risk for servers start / stop operations. 

  

2\. Database

The SQL Server database with the client Orchestrator acces data + AutoScaling Strategy robot counters can be deployed anywhere and it only contains the Tenants table (sql create script provided). The connection to the DB is done with the UiPath.Database activities – the connection string is retrieved from the TenantsDbConnectionString text Orchestrator asset (from the Management Orchestrator).

  

3\. Webhook Receiver. Webservice / Function

This component consists of minimal code that is designed to receive events, parse their data and forward them to the Management Orchestrator as new queue items.

  

4\. Management Orchestrator

Most of the RAS solution items are to be configured in an Orchestrator tenant, in a dedicated folder: Processes (ProcessQueueItems, ..), Assets (for DB connection, infrastructure access), Queue + Job Trigger (on new item added). The RAS solution can be deployed in the same Orchestrator tenant as one of the managed clients, as long as it is configured in a folder that is not associeted with a client from the DB.

  

  

**Process Flow. Event Driven**

  

One deployment of the RAS solution can perform autoscaling for multiple clients at the same time – this is possible by leveraging the Orchestrator’s capability to emit job events via webhooks. The job events that are incoming from the managed clients are received by a small web-service / function and forwarded to a Queue in the Management Orchestrator for processing.

  

As part of the processing step, a _ProcessClient_ job connects to the Database and tries to identity the client of an event in the Tenants table - if found, the information from the selected row has the client Orchestrator API acces data + the scaling strategy for the client’s folder or folder+environment.

  

The processing job connects to the client’s Orchestrator and retrieves its current state (jobs running/pending, robots available/disconnected/busy). With all the data available, the job will evaluate the state + scaling strategy robot counters, selects the impacted robot machines and proceeds to apply the neccesary actions (start / stop server).

  

**Process Flow. Scheduled (pooling)**

  

This mode doesn’t require any of the job events related RAS components (webhooks, events receiver service, queue): the autoscaling process is triggered periodically (scheduled start at each 5+ min), according to a specified scheduled processing job (1 for each client DB entry).

  

  

**Notes**

*   The current version works with both classic and modern folders and can allocate/deallocate robot machines from Azure, AWS, Google Cloud, VMware, Citrix
*   Next releases will work with modern folders too and will add support for Hyper-V

6bea87b7-e193-4337-8db4-99759cfb0878.pdf

f3851f29-6f73-442a-b187-77aab6adf375.pdf

fa2ceb06-0622-4f59-845b-c0812d5343ab.zip

The Robots Auto Scaling solution is implemented with the help of the official UiPath IT Automation activities - they empower us to automate use cases from all areas of our IT Ecosystem, in both on-premises datacenters and public clouds.

  

As part of the auto-scaling process, the robot machines are started / stopped automatically as a function of:

  

1\. **Defined Scaling Strategy**

*   _hot_ Robots count - their machines are always running.
*   _cold_ Robots count - their machines will be allocated/deallocated dynamically.

2\. **Client’s Current State:**

*   Jobs (pending, running, completed, stopped, faulted)
*   Robots (available, disconnected, busy)

  

**Solution Components**

  

1\. Client Tenants – Orchestrator Webhooks

  

The managed clients need to have configured in the Webhooks area the URL associated with the Webhook Receiver’s endpoint for the events job created / completed / faulted / stopped. These events act as triggers for the autoscaling process and they are processed in bulk, to minimize concurrency risk for servers start / stop operations. 

  

2\. Database

  

The SQL Server database with the client Orchestrator access data + AutoScaling Strategy robot counters can be deployed anywhere and it only contains the Tenants table (SQL create script provided). The connection to the DB is done with the UiPath.Database activities – the connection string is retrieved from the TenantsDbConnectionString text Orchestrator asset (from the Management Orchestrator).

  

3\. Webhook Receiver. Webservice / Function

  

This component consists of minimal code that is designed to receive events, parse their data and forward them to the Management Orchestrator as new queue items.

  

4\. Management Orchestrator

  

Most of the RAS solution items are to be configured in an Orchestrator tenant, in a dedicated folder: Processes (ProcessQueueItems, ..), Assets (for DB connection, infrastructure access), Queue + Job Trigger (on new item added). The RAS solution can be deployed in the same Orchestrator tenant as one of the managed clients, as long as it is configured in a folder that is not associated with a client from the DB.

  

  

**Process Flow. Event Driven**

  

One deployment of the RAS solution can perform autoscaling for multiple clients at the same time – this is possible by leveraging the Orchestrator’s capability to emit job events via webhooks. The job events that are incoming from the managed clients are received by a small web-service / function and forwarded to a Queue in the Management Orchestrator for processing.

  

As part of the processing step, a _ProcessClient_ job connects to the Database and tries to identity the client of an event in the Tenants table - if found, the information from the selected row has the client Orchestrator API acces data + the scaling strategy for the client’s folder or folder+environment.

  

The processing job connects to the client’s Orchestrator and retrieves its current state (jobs running/pending, robots available/disconnected/busy). With all the data available, the job will evaluate the state + scaling strategy robot counters, selects the impacted robot machines and proceeds to apply the neccesary actions (start / stop server).

  

**Process Flow. Scheduled (pooling)**

  

This mode doesn’t require any of the job events related RAS components (webhooks, events receiver service, queue): the autoscaling process is triggered periodically (scheduled start at each 5+ min), according to a specified scheduled processing job (1 for each client DB entry).

  

  

**Notes**

*   The current version works with both classic and modern folders and can allocate/deallocate robot machines from Azure, AWS, Google Cloud, VMware, Citrix.
*   Next releases will add support for Hyper-V.

Version	Release Date	Download Link
2.1.6	October 6, 2021
added backwards compatibility with Orchestrator v20.4 API for ModernFolders added AmazonAWS_IAM_Role as option for connecting to AWS infrastructure
2.0	September 20, 2021
added support for ModernFolders infrastructure types: added Google Cloud
1.6	Invalid Date
added option to make the robots selected for deallocation instantly unavailable at Orchestrator level; works with 20.10+ (see asset RobotStatusToggle) as well as older versions (see asset Common_TemporaryEnvironmentName) improvements & bugfixes
1.5	October 5, 2020
Added ProcessClient pooling mode, bugfixes, reduced risk of race conditions
1.0	August 28, 2020
Release 1.0 works with: Classic Folders Azure, AWS, VMware, Citrix Upcoming: client automatic onboarding: orchestrator setup + servers deployment virtual Robots Modern Folders Google Cloud, Hyper-V

UiPath Unattended Robots Auto Scaling