Top 5 Reasons to Upgrade to Automation 360 (as Explained through Emojis!)
Top 5 Reasons to Upgrade to Automation 360
Automation 360 is the first and only cloud-native robotic process automation platform. In this blog, we’ll take a look at Micah’s top 5 reasons for upgrading to Automation 360 and break down each reason to understand what advantage is offered over previous Automation Anywhere Versions.
The Bot Agent is what runs locally on a development machine and a bot runner (attended or unattended) to establish a connection between the local machine and the Control Room.
Beyond the Bot Agent being a lightweight application for running bots, what really makes this a top 5 feature is the ability for CoE leads or system administrators to automatically (or manually) update the bot agent all from the Control Room.
For additional details on automatic Bot Agent updates, take a look at the documentation portal for a detailed description of how updates to Bot Agent devices can be controlled.
AARI (Automation Anywhere Robotic Interface) introduces the capability for humans and bots to collaborate in new ways.
While you may be familiar with running bots through scheduling or triggers – AARI enables users to kick off tasks that can be sent to a bot and also enables for an interface for the bot to communicate back with users
Great for situations like call centers where bots can do research in support of human efforts, or for front office use cases where users may want to kick off a task to a bot while they go and work on other things.
Cloud is a key product differentiator – Automation 360 is Cloud-Native, not just cloud compatible.
Built from the ground up to run on Cloud infrastructure, Automation 360 offers a scalable, highly reliable RPA experience
If you’ve ever had any experience managing the architecture, failover, and high-availability of on-prem enterprise software, you’ll recognize how big of a benefit it can be to offset that to a cloud provider that can handle that infrastructure for you.
With the introduction of Automation 360 came the Automation 360 Package SDK – enabling developers to create and modify their own custom packages that can be installed and used in Automation 360 just like the packages that come built into the product.
The flexibility of package development means that organizations that have custom in-house apps, services, or interfaces that they want their bots to work with – can create customized packages built to the specific needs of those target apps.
Bonus: If you want to see how many of the Automation Anywhere created Bot Store packages work, head over to our GitHub for the full source code for 20+ packages!
The Modular Design of Automation 360 enables expanded bot resiliency when platform upgrades or package updates occur.
When a bot is created – the bot keeps track of the specific versions of each package it is using.
When that bot is sent to a bot runner for processing – the bot runner is also made aware of the specific package versions that were referenced in the creation of the bot
Should you develop your bot using the 2.2.20200208.1.2 version of the Excel Basic package, that version would continue to be distributed/referenced with your bot during bot processing – even if a newer version of the Excel Basic package has also been installed.
This modular design should enable RPA practices to upgrade bots on their own schedule, and reduce any interruptions that bots may have otherwise faced after an upgrade.
There’s no shortage of reasons to upgrade to Automation 360, and the top 5 reasons list provided in this article only begin to scratch the surface of the benefits of a fully cloud-native and web-based RPA platform. As you continue to test, build, and run bots on Automation 360 it’s likely that you too will appreciate some of the features mentioned above as well as many others that solve issues unique to your organization.
Haven’t tried out the Automation 360 platform yet? Head over to the Automation 360 product page to learn more about product features, request a demo, or try out a free trial today!
What "Type" of bots is your organization creating? Let's take a look at 4 common bot types and see if it might spark some creativity in the way that your team approaches the creation of new automations. Read More