Automation 360 v.21 Community Edition Release Notes
Release date: 02 June 2021
Review the new features in the Community Edition of the Automation 360 v.21 (Build 9664) release.
To verify which Bot agent version is compatible with this release, see Compatibility with Automation 360 builds.
|Automation 360 navigation
We have enhanced the overall readability and accessibility of the Automation 360 interface. To make navigation easier, menus and views are organized based on frequently used features and related tasks.
The interface includes the following updates:
workload automation on a multi-user Windows terminal
To optimize workload automation and multi-user devices, you can deploy workload automations on a multi-user Windows terminal server so that a single device can process multiple work items concurrently.
|New actions in the SAP BAPI package
Use the following new actions:
Use the following new actions:
Common table expression supported in Database
You can now use common table expression (CTE) in the Read from action using the WITH keyword in SQL-compliant databases such as Oracle and MySQL. Use CTE statements within a SQL query to simplify complex joins and subqueries.
|Support for large numbers in Number
package (Service Cloud case
You can now perform mathematical operations for large numbers with more precision in the Number package.
|Snowflake database support using
OBDC driver (Service Cloud case
Snowflake OBDC driver is now supported in the Database package. You can connect to the Snowflake database using ODBC-based client applications.
The following actions support this feature:
new features and enhancements (Service Cloud Case ID:00740585)
|Universal Recorder new features and
attribute use to password fields only (Service Cloud
When you create or edit a credential attribute, ensure that bots input the attribute value only in fields that are identified as password fields by selecting the Set this attribute as a password option.
|Default names for output
When you configure an output variable for the actions in the Error handler and Python Script packages, the Control Room automatically generates a descriptive default variable name. If you create more than one output variable for an action, the subsequent variable names are appended with a -1, -2, -3, and so on to avoid a variable name conflict.
|New string action to support nested
Use the action to compare a user-specified string variable with the string variables in the bot. If a match is found, the action returns the value of the matching variable.
A user with the AAE_Admin role can delete a global value from the All global values page.
|ODBC driver support
for all connection
(Service Cloud Case ID: 00748887, 00777676)
An Open Database Connectivity (ODBC) driver is now available to support all the ODBC connection strings in the same way it was used in the Enterprise 11 version. Using SQL as a standard for accessing and managing data, you can connect to MySQL, Google BigQuery, Snowflake, and other databases using the ODBC driver.
|Share a DLL
You can now share a DLL session between bots.
Automation Anywhere Robotic Interface (AARI)
delete, or view files in browser in initial forms or
Users can now use the Select File element to download files that are uploaded to the initial forms or tasks, and they can also delete files or access the hyperlink file to view the file in within the browser. The uploaded file can be accessed as a hyperlink, and new icons are available for download and delete.
|Enhancement to team
The AARI team consists of three roles:
An AARI admin or manager can edit their teams and update their team members' roles. They also have the option to add or remove team members. The AARI manager is the team admin by default when they create a team.
|Assign to me feature
When a task is unassigned and users access the tasks, use the Assign to me option to allow the tasks to be assigned to the current user so that they can immediately access the form.
When AARI team members with attended Bot Runner licenses access the web interface, they are automatically redirected to AARI Assistant. Users can view all the bots created by them on this page. They can also pin, search, and sort their assigned bots.
|New team reference in
Request and Process
The user can now reference the team from which a request is created by referring to the new Team column in the Request page or the team name added in the process tile in the Process page, to help guide their team assignment.
Cloud case ID: 00718119)
Request visibility enables users to allow or restrict access to a request they created to other team members. When the Request Visibility field is set to Shared, all the requests are accessible by all members, owners, and team admins. If the field is set to Private, the requests are available only to the user who has created the request, owner, and the team admin.
The following enhancements are available on the Processes page:
|AARI Assistant for attended Bot Runners
The AARI Assistant application enables users with the attended Bot Runner license to access their bots without logging in to the Control Room. AARI web users can use the AARI Assistant when the attended Bot Runner license is enabled along with their AARI User license without impacting their existing functionality.
|Add rows from
header row context
Only the header row is displayed when a form that has a table is launched during bot runtime. Use one of the following methods to add new rows to the table:
|Sort for a
process tile from the Processes
You can now use the sort field to help you locate a process tile quickly. From the Processes page, use the drop-down menu to sort on a process tile based on the process name in alphabetical order. Alternatively, you can sort in the order of the newest process created to the oldest process and vice versa.
|Enhancements to opportunities
You can now review and analyze automatically generated (or system-generated) opportunities immediately from the Opportunities page. Auto-generated opportunities are created when at least two recordings are approved by the user. You can create a custom opportunity from an auto-generated opportunity and apply the Model and Filter options to target a specific opportunity for automation.
You can now prioritize opportunities based on a simple formula for all recordings in a process. From the Opportunities table, you can view the cost without automation and savings for an opportunity. The system automatically calculates the cost and potential savings for each opportunity generated. You can customize these metrics based on your organization's model for cost and savings.
files are available on your local
The generated PDD file for an opportunity is now stored locally on your server for On-Premises deployments. The existing PDD files are automatically moved to the new location and are not deleted when a re-installation or upgrade is performed in the Control Room.