Automation Workspace v.27 release
- Dernière mise à jour2026/02/16
Automation Workspace v.27 release
Review what's new and changed, and the fixes and limitations in Automation Workspace for the v.27 release.
What's new
| Control Room, devices, and Agent robot |
|---|
|
Windows 365 Cloud PC now supported as Bot Runner
(Service Cloud case ID: 01792699) We support Windows 365 Cloud PC as a Bot Runner to create and run robots on Windows 365 Cloud PC. |
|
Oracle Database is now supported on Linux (Service
Cloud case ID: 00726728) We now support Control Room with Oracle Database on Linux, so you can now choose to install the Control Room with Oracle Database on Linux. Installation de la Control Room sur Linux | Exigences de base de données |
|
Microsoft Edge offline extension is supported
(Service Cloud case ID: 01829649, 01880289) You can now install the Microsoft Edge offline extension for Microsoft Edge Enterprise browser users even when the device is offline. When the Bot Runner machines do not have Internet connectivity, you can use these features with the Microsoft Edge offline extension:
The Microsoft Edge offline extension is transparent and works similarly to the Microsoft Edge online extension for users. Installer Agent robot et enregistrer l\'appareil Windows | Extensions de navigateur pour Automation 360 |
|
Centralized notifications repository for various events and capability
updates
You can now track all the platform and automation events through a centralized repository. With this feature, you can identify the severity of events, consider possible actions based on the severity of events, and then take appropriate actions. You can also be notified about platform updates, such as robot export and package updates. Thus, it improves platform and user productivity. |
|
Automatically select the number of Bot Runners
(Service Cloud case ID: 00821020, 00715598, 00723191, 00784822,
01830238, 01870817) You can enable Automation 360 to automatically select the Bot Runner users for specific tasks to:
This capability ensures that when you run or schedule an automation, the system automatically picks the available run-as users from the specified list. Sélectionner automatiquement le nombre d'utilisateurs Bot Runners | Planifier une automatisation |
|
Manage domain accounts using gMSA (Service Cloud case ID:
00731119) You can use a group Managed Service Account (gMSA) to manage and run Control Room and other Automation 360 services. |
|
View keyboard shortcuts in Éditeur de robots
In Éditeur de robots, you can now open a menu to view the available keyboard shortcuts. Liste des raccourcis clavier pour Windows |
|
Validate device credentials prior to bot deployment
Prior to robot deployment, you can select to validate the device credentials for Bot Creator, attended Bot Runner, Développeur citoyen, and unattended Bot Runner users. This provides users additional security for robot deployment. Basculer l\'enregistrement de périphérique entre des instances de la Control Room |
|
Export roles to view users and their permissions (Service Cloud
case ID: 01804955) You can export selected roles and their permissions to CSV files to view the following information:
|
|
TLS 1.3 encryption support for a more secure connection
to Control Room services (Service Cloud case ID:
00549240, 00606859, 01925085) Automation 360 Sur site supports both TLS 1.3 and TLS 1.2 cryptographic protocols for HTTPS and TCP communications between our components. Prise en charge des protocoles sécurisés | Configurer le protocole TLS (Transport Layer Security) de l'application |
|
Enhanced Automation Anywhere Debugger tool
The Automation Anywhere Debugger tool is available in the Bot Assistant utility to provide a better user experience. When you invoke the Debugger tool from the Éditeur de robots, you can add, update, or delete actions and variables in a robot. By default, the Watched variables lists is empty. With a single click, you can add all the used variables in a robot. These variables display in a pop-up window where you can select or deselect, one or more variables, from the list. |
|
Google Chrome and Microsoft Edge certification
for operating systems
Google Chrome and Microsoft Edge extensions are
certified for the following operating systems:
|
| Packages, actions, and Éditeur de robots | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Notification for package updates
When you add or update a package or upload a custom package to the Control Room, you are now notified about this platform event. This notification is displayed to all the Control Room users through the Notifications repository. Capacités prenant en charge des notifications | Ajout de packages à la Control Room | Ajoutez un package personnalisé à votre Control Room | Chargez un package personnalisé à votre Control Room |
||||||||
|
ServiceNow package
You can use the ServiceNow package from Automation 360 to authenticate and perform several actions with records and attachments in ServiceNow tables. |
||||||||
|
ServiceNow triggers
You can use ServiceNow triggers to call an action when there is a new or updated record. Création d\'un déclencheur de nouvel enregistrement ServiceNow |
||||||||
|
Cut, copy, paste keyboard shortcuts added for TN3270 and TN5250
Terminal Emulator
In the Terminal Emulator package, the following
keyboard shortcuts are now available specifically for TN3270 and TN5250:
|
||||||||
|
Quick assistance at hand for the developers in the Éditeur de robots
The accessibility and usability of the Éditeur de robots, actions, and packages have been improved.
As a citizen developer or an RPA developer, when you are creating robots, you can quickly look up information about the actions without navigating outside the Éditeur de robots. Under the Actions
pane, quick help is enabled with contextual information about actions. Additionally, an icon is configured with a
link to the documentation. If you want more information about an action, you can click the link, which redirects you to
the relevant page in the documentation portal. This feature is
currently available in the following actions and packages.
|
||||||||
|
Enhanced user experience through refreshed and intuitive icons
With the new and intuitive icons for actions in the Éditeur de robots, citizen developers and RPA developers can quickly locate the correct action while creating automation for a day-to-day task. These unique and renewed icons are developed according to brand and global standards. |
||||||||
|
Seamless package updates
When a package version is added to the Control Room, either from a Cloud download or Control Room update, as an administrator, you have the flexibility to disable the new version of packages. This feature helps you to restrict users from using the new package version until it is verified. Mettre à jour les packages dans la Control Room | Mises à jour automatiques du package pour Sur site Control Room | Mises à jour automatiques du package pour la Control Room |
||||||||
|
New option in Read from action of Base de données
package
(Service Cloud case ID: 01263940) A new check box is available when you use the Read from action to retrieve records from the database and save the retrieved data in a CSV file. When you select this check box, no CSV file is created if the executed SQL query does not return any data. |
||||||||
|
Proxy support for EWS-OAuth2 (Service Cloud case ID: 00771400,
01574715, 01815888) When you create a robot with the E-mail package that uses EWS OAuth2 for authentication and the Bot Runner machine is configured behind the firewall, then all outbound requests are routed through the proxy server configured on the Bot Runner machine. |
||||||||
|
64-bit ODBC driver now supported in Base de données
package
(Service Cloud case ID: 01256142, 01829360, 01849908) We now support connecting to databases by using the 64-bit ODBC driver. This option is available when the connection mode is the default. Organizations transitioning to Microsoft 365 will benefit from leveraging this enhancement and can sustain automation build with 32-bit ODBC drivers. |
||||||||
|
OAuth 2.0 support in E-mail and Email trigger
packages
(Service Cloud case ID: 01798311, 01803702, 01791859,
01828526) Microsoft is deprecating the ability to
use Basic authentication in Exchange Online for these specific protocols:
|
||||||||
|
Retry mechanism supported in credential variables (Service Cloud
case ID: 01786319, 01887182) The credential variables support the retry mechanism. When you create a robot that uses credential variables, if the robot fails during run time to retrieve those variables from the Credential Vault because the Control Room is disconnected or the Control Room services stop intermittently, then the robot tries three times to retrieve the credential variables from the Credential Vault. Note: Ensure that the Agent robot version installed on
your system is the version that is released with Automation 360 v.27.
|
||||||||
|
Support of other domain name in the Active Directory
package
(Service Cloud case ID: 01807358, 01910765) We now support Active Directory user operations by logon name with domain and can provide the domain name to extract user details. When you retrieve the user property or perform any user operation based on the logon name (userPrincipalName), and if the user domain name differs from the domain specified in the LDAP path, the user properties are now successfully retrieved with or without a domain name. For example,
LDAP Path: LDAP://ADServer/DC=automation,
DC=net
The following list of actions supports logon name with domain.
|
||||||||
|
Shared mailbox support for E-mail automation
(Service Cloud case ID: 00797231, 01816574, 01829499, 01854615,
01871861, 01933058, 01834152, 01829684, 01853949, 01880386, 01869636,
01894591, 01867553, 01911371. 01925438) The E-mail package supports the email automation of a shared mailbox in Outlook for Office 365/Microsoft 365 using IMAP/EWS protocols, and OAuth 2.0 authentication using Client Credentials and Authorization Code with PKCE grant flows. You can automate emails retrieved from a shared mailbox and perform all email-related tasks by accessing each folder(s) and its subfolder(s) in the shared mailbox. |
||||||||
|
New action in Fichier texte
package
You can use the new Read variables
action in the Fichier texte
package to read the values of variables from the text
file.
Note: The Import string from text file
action in the Chaîne
package has been deprecated and will not be
available for new robots. We recommend that you use
the new Read variables
action with enhanced capabilities. This deprecation
does not impact any existing robots or robots which were migrated previously and they will
continue to run properly. See Politique de support et d\'obsolescence appliquée aux packages for package lifecycle and deprecation policy.
|
||||||||
|
Call an existing JavaScript function in a webpage
You can use the new Call a JavaScript function action in the Navigateur package to call an existing JavaScript function directly in a webpage or in an iFrame within a webpage in Google Chrome and Chromium-based Microsoft Edge browsers. In the robot, you can also pass one or more input parameters to the JavaScript function and process the return value from the function. |
||||||||
|
Automate controls using Microsoft UI Automation (COM) technology
You can use the Microsoft UI Automation (COM) technology to automate
the following scenarios:
Actions effectuées sur des objets capturés avec Enregistreur universel | Capturer à l'aide d'une technologie spécifique |
||||||||
|
Capture objects on applications running in administrator mode
You can use the Enregistreur to capture objects on applications running in administrator mode. To capture the object, select the Capture and run with admin privileges option from the Éditeur de robots. |
||||||||
|
Enhanced robot performance when using global values
across robots
When you use global values across a parent robot and a
child robot, the robot performance is
enhanced by reducing the robot execution time. To enable
enhanced robot performance, you must set the
Bot compatibility version to
3 in the Advanced
settings page of the Éditeur de robots.
Note: Ensure that the Agent robot version
installed on your system is the version that is released with Automation 360 v.27.
|
||||||||
Enhanced user interface for Define functionality in AISense Recorder
Utilisation d'une ancre de variable | Capturer les zones de texte, les cases d'option, les cases à cocher et les zones de liste déroulante | Capturer la valeur de texte avec l'AISense Recorder | Bouton Capturer le lien par l'AISense Recorder | Bouton Capturer l'image avec l'AISense Recorder |
||||||||
|
New virtual key added to the Simuler les frappes de touches package
In the action, a new key named Return has been added to the virtual keyboard for Enter functionality and the Enter key in the Number pad has been renamed to Num Enter. As a result, the Return key is the main Enter key on the keyboard. This enhancement keeps the keyboard in sync with the physical keyboard. The nomenclature has been changed to avoid confusion between the Enter key on the keyboard and the Enter key on the Number pad. |
||||||||
|
Support for global variable for all Datetime actions
In the Date/heure package, you can use the Datetime global variable across all Datetime actions. You can select to use either String variable or a Global variable in the Source date and time variable option. This avoids creating multiple local variables and reduces the total number of actions used in a robot. |
||||||||
|
The resiliency of the File/Folder trigger has been improved to continue listening after a network disruption has occurred. Previously, a network error caused the trigger to lose connection with the Agent robot. Service Cloud case ID: 01769532, 01773584, 01834098, 01867418 |
| Building and running robots |
|---|
|
Notification for robot export
When you export a robot in the Control Room, you are now informed through the Notifications repository. This notification is sent only to the user who exported the robot. Capacités prenant en charge des notifications | Exporter robots |
|
Code analysis runs automatically for all unscanned robots
in public workspace
Code analysis now runs automatically on all the robots with the Not Scanned status in the public workspace. This ensures visibility on the coding best practices for policies configured in the Control Room and will show the results of code analysis for all the robots in the public workspace without the need to run code analysis on each robot one by one. |
|
Check out multiple robots and files
(Service Cloud case ID: 00628344, 00822352)
You can now select multiple robots and their dependent files from different folders that belong to the same process and check them out from the public to the private workspace. You can check out a maximum of 10 parent robots, but there is no limitation on the number of dependent child robots. |
|
Choose specific version of non-bot dependency to check out with parent
robot
When you check out a parent robot, you can now choose the version of a non-robot file dependency to check out. Every version of a parent robot can have different versions of non-robot file dependencies. With this feature, you can roll back the dependencies while rolling back the parent robot. You can make changes to a specific version of the dependent non-robot file. |
|
Compare robot version in private workspace (Service
Cloud case ID: 01761840, 01771389, 01763432, 01904500, 00798356,
01780116) You can now see the changes made to your robot logic in the private workspace before checking in your robot. As a Bot Creator, it was difficult to identify the changes made to the robot logic, input, and output parameters. With this functionality, you can now easily identify where you have made the modifications to the robot logic, variables, triggers, dependencies, and packages compared to the latest version or any other previous version of the robot. |
|
Edit non-empty folder description in public workspace (Service
Cloud case ID: 01820406) You can edit the description of non-empty folders in the public workspace. Meaningful descriptions provide more insight of the robots contained in that folder. This feature enables an administrator or a user with rename folder permissions to better manage the repository when it contains many folders. |
|
Specify queue running times in workload automations (Service Cloud
case ID: 01816260, 00331357, 01924895, 01274769) You
can set the specific time period when to run a workload automation.
When creating the workload automation, you can set the queue running
days and time to ensure that the automation does not run during these scenarios:
|
|
Check for duplicates when adding work items (Service Cloud case
ID: 00825850, 01792046, 01806516) You can check for duplicate work items before adding them to the queue. This feature prevents re-processing the same work items multiple times, thus saving time and resources. You can either move the work items marked as duplicate for re-processing or discard them. |
|
Generation of API Key is audited
The generation of the API key is now audited and will display the expiry time of the api-key in the audit logs. |
| APIs and integrations |
|---|
|
Workato Integration
You can integrate the Automation 360 platform and Workato by using the Automation Anywhere connector. You can establish a connection with the Automation Anywhere Control Room and perform various operations using the Control Room APIs. |
|
SnapLogic Integration
You can now integrate the Automation 360 platform and SnapLogic. You can establish a connection with the Automation Anywhere Control Room and perform various operations by using the Control Room APIs. |
| RPA Bots for Salesforce |
|---|
| Now when creating new connections, you have the option to include an API Gateway certificate. |
What's changed
| Control Room, devices, and Agent robot |
|---|
|
Automated reprocessing of failed WLM work items (Service Cloud
case ID: 00825872) When you create or edit a queue, you can now use the Max auto retry attempt option to ensure that failed WLM work items are reprocessed automatically. With this option, you can specify the number of times for which the automatic reprocessing of failed work items will be attempted. Automatic reprocessing of failed work items is attempted after all the work items in a queue are processed. |
|
Better device management with improved device permissions (Service
Cloud case ID: 01264963, 01871530) You can now view and manage Agent robot devices even if you have not registered
them by using the enhanced Edit the device(s)
permission. The Edit the device(s) permission
is improved as follows:
|
|
Enhanced bot Compare versions page
The bot Compare versions page shows changes in the dependencies between two versions of the robot. It shows changes for the first level of dependencies only and displays those dependencies sorted in alphabetical order. |
|
Specify time period to put work item on hold (Service Cloud case
ID: 00825875) You can put a work item on hold for a specific date and time. This ensures that the work item moves automatically to processing (new state) on the specified date and time and no longer requires you to manually move it for re-processing. A new column in the Edit queue page displays the hold status of the work item, either date and time or indefinite if you do not specify the date and time. |
| Packages, actions, and Éditeur de robots |
|---|
|
Control Room version compatibility check with specific
packages
When you manually upload a package or a robot in the Control Room, the system now checks if the specific packages used in the robot are compatible with the Control Room version. |
|
Analyze button renamed in Éditeur de robots
The analyze button of Bot Insight (Analyze Task Bot) has been renamed to Bot Insight "Analyze" dashboard in the Éditeur de robots page. |
Fixes
Build 16701: This build includes the following fixes (along with fixes from the previous builds):
| Fix for inconsistencies that were observed on
the In-progress activity page. Service Cloud case ID: 01949323, 01950696, 01944637, 01951100, 01953055, 01950639, 01951722, 01929156, 01954486, 01954920 |
Build 16694: This build includes the following fixes (along with fixes from the previous builds):
| If the Manage my activity
feature is enabled for a user role, then the user can view the pause,
resume, and stop status on the In progress activity
page. If this feature is disabled, then the user cannot view these statuses.
Previously, users were able to view these statuses even when the feature was disabled. Service Cloud case ID: 01937106 |
Build 16667: This build includes the following fixes:
| When synching with the Active Directory (AD), the user mapping no longer overwrites the Description field in the Control Room with blanks. |
| The Automation 360 Control Room no longer generates an error in the User Management log when a mapped security group has no members. |
| The In progress
activity page no longer shows robots after
they are run. Previously, the page incorrectly showed robots in the active state even after execution. Service Cloud case ID: 01914651, 01924866, 01923265, 01928088, 1918956, 01922321, 01931985, 01921849, 01938985, 01939812, |
| When a user is assigned an admin role to
create schedules and later the admin access is removed for that user, an
audit log will be logged when the schedule is canceled because of the
user not having the admin privileges. Previously, when such schedules were canceled, no audit logs were logged indicating that the schedule was canceled because the user did not have the required privileges. Service Cloud case ID: 01830359 |
| The page and the Control Room banner displayed
on the same licenses page now display correct information about license
expiry. Previously, the correct information about license expiry was not displayed. Service Cloud case ID: 01807324 |
| When you edit a role, the Edit
role audit log page now displays the correct old, new, and
run-as user values. Previously, these values were not displayed. Service Cloud case ID: 01759116 |
| When you edit your first or last name on the
My profile page, the description and auto login
values on the Edit user audit log page will not be updated. Service Cloud case ID: 01846878 |
| You can correctly filter the status for
activities on the page. Previously, some filters were not displaying the correct status for activities. Service Cloud case ID: 01869361, 01875216 |
| Users without permission cannot view the
activities of other users on the In progress
activity page. Previously, some users were able to view the activities of other users even though they did not have permission. Service Cloud case ID: 01911289, 01910582 |
| If you configured the log collection level as
Debug, the logs collected from some packages do
not include customer data. Previously, the logs collected from some packages included customer data. Service Cloud case ID: 01862053, 01870001 |
| If
the CPU utilization and device memory threshold values are outside the
percentage range defined by the Control Room administrator
in the , a clear error message now indicates the device
unavailability and provides an appropriate action. Previously, when the CPU utilization and device memory thresholds values exceeded the defined value, robot deployment failed with an unknown error message. |
| Device shows an accurate status when the Agent robot is disconnected from the Control Room. Previously, due to the default time (15 minutes) of the WebSocket connection, a device was shown as connected even when the Agent robot was disconnected from the Control Room. Service Cloud case ID: 01843990 |
| In
the Oracle Database environment, a checked-in robot is now automatically refreshed and can be viewed in the
Public folder. Previously, to view a checked-in robot in the Public folder, you had to manually refresh the Automation page by using the Refresh button. |
| When a
Stop Task command is used, WLM work items are
now marked as completed successfully and show the correct status in the
Control Room. Previously, WLM work items were marked as failed even if the robot was executed successfully. Service Cloud case ID: 01841320, 01840748 |
| When you run WLM automations, if the Control Room restarts during deployment, the WLM deployment
continues without delay when Control Room services are
active. Previously, after the Control Room restarted, there was a delay of 15 minutes before the WLM deployment continued. |
| When you run a bot by using the Run bot
with queue option, the correct value of the work item is now
selected, irrespective of the modification source. Previously, when the
value of a work item was modified through the API or bot setting, the
older value was selected by the bot Service Cloud case ID: 01786785 |
| In an Oracle
Database environment, when you select the number format and sort order
for the work items in a queue and then run bot by using the
Run bot with queue option, the queues are now
deployed successfully. Also, the correct log entry is shown in the
Audit log or Activity
page. Previously, queues were not deployed, and no errors were shown in the Audit log or Activity page. |
| In a clustered environment, the robot deployment progress is no longer stuck and the Bot Runner device connects to the Control Room successfully. Previously, the robot deployment progress would get stuck sometimes and show an error message Waiting for user: <username> and/or device: <device-name> on the page. Service Cloud case ID: 01830285 |
| When a robot keeps running for a few hours, an error no longer
occurs due to high memory usage with the Enregistreur
package version 2.9.2 or later. Previously, an increase in memory usage caused the robot to fail after a few hours with a Java heap space error. Service Cloud case ID: 01911565 |
| When you read emails within a loop using a
Microsoft Outlook Client connection with a subject filter, use the
Delete
action and run the robot, the robot now completes the set iteration and deletes the emails
from the specified folder. Additionally, the variable that was used to
display the count of total emails versus deleted emails now displays the
correct counts in the message box. Service Cloud case ID: 01845642,01857791,01880424 |
| When you establish a connection with the
EWS server, and emails are read within a loop
to filter and move all emails from a subfolder created within the custom
folder, the robot now executes without an
error. Previously, an error occurred because the robot could not read the emails from the folders created outside the predefined folder, such as Inbox, Junk, or Draft. Service Cloud case ID: 01823238 |
| You can now
successfully create a robot by using the Upload
file
action from the Microsoft 365 OneDrive
package. Previously, the robot displayed
an error when you used the Upload file
action and if the file name had special characters such
as brackets [].
Note: Brackets [] are now supported in the file
name.
Service Cloud case ID: 01798568 |
|
When you choose the variable option to perform a task and during robot creation process you delete the variable you created (Your variables), and when you click the Add option in the variable field to insert a variable (such as global variable), the option is now enabled. Previously, the Add option for inserting the variable was disabled.Service Cloud case ID: 01869139 |
|
When you create a robot, you can now use the Update node action of the XML package to update the value of a node. Previously, the attributes were removed when you updated the text value of an XML element. Service Cloud case ID: 01805643 |
In the E-mail
package, connect to the EWS server
and use . If the source mail is sent on behalf of some other user,
for example, user xyz@aa.com sent mail on behalf of user
abc@aa.com, the email dictionary variable
emailFrom now returns the correct sender ID, which
is abc@aa.com.Previously, the email dictionary
variable emailFrom returned the sender ID as
Service Cloud case ID: 01856149 |
| When you
run a stored procedure in Oracle and it returns SYS_REFCURSOR, the
Run stored procedure
action closes the cursors. Previously, the Run stored procedure action was not closing the cursor after the maximum cursor limit was reached. Service Cloud case ID: 01842046, 01898572 |
| In the Active Directory
package, when you perform a user account operation such as
Add users to group, Delete
user, Disable user account, or
Rename user, and if the username has an
asterisk (*), open parenthesis, or close parenthesis, you can now add a
user without any error. Previously, the username did not support the following special characters: asterisk (*), open parenthesis, and close parentheses. Service Cloud case ID: 01884962 |
|
When you create a folder in Outlook with a percentage (%) in its name (for example, Clients%ClientA), create a robot using the Connect action from the E-mail package and then use the Folder exists or Folder does not exist condition, the robot finds the Clients%ClientA and retrieves mail from it. Previously, the robot was not able to retrieve mails from the folder because percentage (%) was not supported in the folder name. |
When you connect to
the Microsoft Access Database with JDBC and specify the database path, if
you use the following specific aggregation functions in the query, an
error is no longer encountered when you run the robot: |
| When using the Task Bot: Run action,
you can search dictionary and session variables to use as input
parameters. Previously, no results displayed when using this Advanced
search feature. Service Cloud case ID: 01879539 |
| A Robot de tâches no longer fails when
you debug or run it when any in_Window input
variable is set. Previously, in edit mode, when you debugged or ran a Robot de tâches with an input variable by selecting the Use as input check box, the bot failed. Service Cloud case ID: 01919263 |
| When you
use the Save
action in the E-mail
package, and if the email subject includes a comma (,),
the emails are saved successfully. Previously, if the email subject included a comma (,) and you saved the email, the comma (,) was replaced with an underscore (_). Service Cloud case ID: 01786211 |
| When you select the Package details page, and select the Availability tab, if the package (all users or selected roles) is changed, then the Package details page displays the last modified information of the user who made the changes, and the changes made at the access level (all users or selected roles). |
| You can create
robots using the Download file
action of the Google Drive
package. Previously, when you used the Download file action and marked the Overwrite existing file option to overwrite the file of the same name, the downloaded file became corrupted. If you then used the action to open this file, or manually tried to open the Excel file, an error message displayed indicating that the Excel file was corrupted. Service Cloud case ID: 01833815 |
| You no
longer have an incorrect starting date when you create an event using the
Google Agenda
package. Previously, when you created an event in Google Agenda and entered the value in the Start Date field with the event type set to All Day, the Google Agenda package decremented the day value by one when you selected the All Day option. Service Cloud case ID: 01815644 |
| When you
use the
action to open an Excel spreadsheet which did not exist
and then run the robot, the robot now displays
the correct error message in Japanese. Service Cloud case ID: 01857992, 01925567 |
| You can
successfully extract fields from a PDF file when you use the or Extract text
actions. Service Cloud case ID: 01818304 |
| When you use the
3.6.1-20220428-010115 version of the Simuler les frappes de touches
package to enter keystrokes against specific webpages
running in the Microsoft Edge browser with IE mode, the
robot processes the keystrokes faster. Service Cloud case ID: 01820418 |
| When you use the
action to split multiple PDFs into various folders and
then use the For each file in folder iterator to
run the robot in a loop to split each file in the specified
folder, the robot no longer encounters an error. Service Cloud case ID: 01803983 |
| When you use
the
action and choose the dynamic file path option to select a
file from the Control Room repository, the robot no longer encounters an error. Previously, even if the
uploaded file was available in the Control Room, the robot failed and displayed this error message: Get
Resource failed: Error: Could not find the file at the Control Room
path. Check the file path and try again. Service Cloud case ID: 01805364 |
| When you use the
action to rename and overwrite an existing file, the robot no longer shows an incorrect error message. Previously,
when you tried to rename an existing file, the robot showed
an incorrect file name in the error message. Service Cloud case ID: 01845943, 01858350 |
| You can
successfully rename the file and remove an extension from the file name
by using the
action. Previously, when used the
Rename
action to remove an extension from the file name, the robot trimmed the last character from the file name instead. Service Cloud case ID: 01842995 |
| When you use the Enregistreur to capture objects on an application that is installed on a virtual machine, finish the recording after the objects are captured, and then relaunch the Enregistreur, the robot successfully launches the Enregistreur and no longer inserts any actions that were recorded earlier. |
| When you use the action to automate Citrix virtual apps running on Google Chrome and Microsoft Edge browsers, add a delay of 60 seconds and run the robot, then if the object does not exist, the robot waits for the specified time (60 seconds) in the Keep trying for (seconds) field before executing the next steps. |
When
you run the robot using the following sequence of actions,
the robot shows accurate data for each loop iteration:
Service Cloud case ID: 01817192, 01853717, 01880154, 01940546 |
| An error no
longer occurs when you use Enregistreur
package 2.8.6 and later versions to perform a click
operation on a link element that opens a pop-up window on a web page
running in Microsoft Edge with IE mode. Service Cloud case ID: 01845776, 01858872, 01923003 |
| When you install
the AARemoteAgent_2.0, the DLL files are now copied to the correct
A360 Remote Agent folder and the
AARemoteAgent_2.0 runs properly. Previously when you installed the
AARemoteAgent_2.0, the DLL files were copied to an incorrect
A360 Remote Agent\Java folder. Service Cloud case ID: 01935630 |
| You can now successfully use the
action to extract values from a PDF that contains a string
data type with the dollar sign ($). Service Cloud case ID: 01848220 |
| You can now successfully run all migrated web
actions of the Automatisation héritée
package in multiple steps of a robot in Microsoft Edge with IE mode. Service Cloud case ID: 01853563, 01865846 |
| In the
action, when you use a variable that contains a number
sign (#) instead of a file path to locate the file that you want to copy,
the robot no longer encounters an error. Service Cloud case ID: 01808009, 01845923 |
| When exporting data to Excel CSV files,
Boolean values return accurately. Previously, a bug caused values to
return as -1 while using OLE DB Driver for SQL Server (version 18 or
later). Service Cloud case ID: 01826530 |
| Updating the Agent robot version sometimes failed. However, when you select the Automatically update all bot agents option, the Agent robot updates to the latest version without failures. |
|
Control Room now supports Windows NT in French. Service Cloud case ID: 00682337 |
All DELETE
/v1/configurations endpoints are not accessible anymore.Service Cloud case ID: 01920980 |
| While installing Automation 360 on a three-node cluster, the installer prompts you to enter the Elasticsearch password for the first node only and replicates this data across the other two nodes. |
|
Bots that are running for longer duration display
correctly on the In progress activity
page. Previously, these robots displayed only after robot updates and were removed after the page refresh. Service Cloud case ID: 01921149 |
| You can now update
Internet Explorer
robots created in Automation 360 to
Microsoft Edge with IE mode using the
Update Bot wizard even if these robots (or its dependencies) contain a '.' (dot) character in
its name. Service Cloud case ID: 01809003, 01814904, 01822014, 01858820 |
| If you selected the Log off
windows session post bot execution option under
Auto-login settings in the Control Room, data in the resource folder is cleared after
the robot run. Service Cloud case ID: 01795752, 01778828, 01804711,01864871,01923299, 01823515 |
| If you delete a device entry from in the Control Room, the device
registration properties are removed. This enables you to reregister the device. Service Cloud case ID: 01808450 |
| You can successfully log in to Automation 360 using Active Directory
credentials when the Auto-login users into Control
Room option is enabled, without encountering any issues.. Service Cloud case ID: 01808170, 01826805 |
| The generated Control Room
operational log files contain readable characters. Service Cloud case ID: 01872473 |
| The Repository Management
(/v2/repository/files/<file_id>/content) API now returns file
contents only for the files the logged-in user has permission to view.
The content of these files cannot be updated using a different
API. Previously, this Repository Management API returned file contents for the files that the logged-in user did not have permission to view. And the user could update the content of these files. Service Cloud case ID: 01819101 |
|
Bot deployment now resumes and completes without any issue
when the action executes before or while the runtime window is
loading. Previously, the resume option was not displayed in the runtime window, and the robot deployment was not completed. Service Cloud case ID: 01835794 |
| You can create a folder within the
Bots folder in the public
workspace. Previously, folder creation failed with an error in the public workspace. Service Cloud case ID: 01257981 |
| You can now successfully compare different
versions of your robots and dependencies in both the public
and the private workspaces. Previously, comparing the robot versions failed with a timeout error. Service Cloud case ID: 01770115, 01905037 |
| When you export the user data to a CSV file,
it now shows the correct user type and device license information for all
users. Previously, user data exported to the CSV file showed incorrect information. Service Cloud case ID: 01840507 |
| You can now check in a robot
successfully to the public workspace. Previously, the robot check in failed because the audit trial was processed unsuccessfully. Service Cloud case ID: 01860361 |
The BLM export is an asynchronous call and
when used with the existing API endpoint
/v2/blm/status/{requestId}, there is a delay
associated with the API call. Due to this delay, you cannot retrieve the
current status of the export if there is not enough time gap between the
export and the status call. To bypass this limitation, a new API endpoint
has been added GET
/v2/blm/status/{requestId}/timeout/{timeout} which introduces
a time delay that waits for the export process to complete and then
retrieves the status.Service Cloud case ID: 01806109 |
| Updated Swagger UI and Swagger
Editor to version 4.15.5 to fix a security vulnerability. Service Cloud case ID: 01843148 |
When you create
robots that use the action and set the Cell Range with
an expression (such as
B1:$SampleNumber.Number:toString$), the Éditeur de robots no longer displays an error and the action now
works properly.Service Cloud case ID: 01941537 |
| When you use the File
trigger to modify a BAT or VBS file, the trigger is generated once.
Previously, the trigger would generate twice when you enabled the
file modified scenario. Service Cloud case ID: 01816589, 01877498 |
| You no longer encounter issues with bot
check-in or cancel check-out after the bulk package update operation.
When you try multiple bulk updates of packages, now an appropriate error
message indicates to perform bulk updates of one package at a
time. Previously, when you performed multiple bulk updates of packages, it resulted in check-in or cancel check-out errors. Service Cloud case ID: 01849828, 01881950 |
|
Bots with a large number of automations complete
successfully without any pre-processing issues or errors. Service Cloud case ID: 01949415, 01949372, 01949033 |
Security fixes
| The version of Springframe Work is updated
to 5.3.22 and does not exhibit the security vulnerability. Service Cloud case ID: 01850811 |
Limitations
| When you create a device pool with a temporary (disconnected) device, the device deletion job does not complete successfully. Additionally, the Audit log page shows the device is deleted, whereas the Device list page shows the deleted device in the list. |
| When you check out robots in bulk, you cannot check out the robots for which you have the required permissions. This is because robots for which you have the required permissions are also excluded along with the robots for which you do not have the required permissions. |
The robot checkout fails in
the following scenarios:
|
| The Service Web SOAP
action does not support handling empty responses from web
services and the command might fail to process the result or generate an
error if the invoked SOAP service returns an empty response. Service Cloud Case ID: 02229471 |
| When you compare robot versions from the View history
page in a Public workspace, the Compare
versions page shows an error message.
Workaround:
To fix this error, perform one of the following actions:
Service Cloud case ID: 01949094, 01946533 |
| In Windows and Linux operating system, notifications are not working with the Oracle Database. |
| We
use a third-party parser to convert from HTML format to plain text. As a
result, when you convert an email from HTML format to plain text, you
will see that, sometimes, the text is not converted into plain text and
is not displayed in the correct format. For example, you might see that
some lines are added or skipped. Service Cloud case ID: 01822614 |
|
In any package, when you select the Add argument option, select String or Number as the Argument type, and then try to insert a value, you might not be able to navigate through the options using the scroll functionality. |
| When you use the action to select the list of environment variables to return the system parameters of the device, some environment variables might not be visible. |
|
When you use the option to read the values of variables from the text file, use the condition to execute actions based on the value of the specified source string, and run the robot, the robot might fail if the key value added to the mapped variable does not match the value in the text file.
Workaround: To pass null values successfully, perform the
following steps:
Alternatively, use the condition to validate if the key is present in the text file. You can then assign value to the string variable accordingly. |
| After you update to Automation 360 v.27, if a new package (first version) is added to the Control Room and in the setting for packages you selected Disable for the new version of package, you will see that the package will have status as Enabled and set as default instead of Disable. |
| In an Oracle Database environment, when you update to Automation 360 v.27, the new package versions
that are shipped through the installer remain in the disabled state and
are not set as the default version. Workaround: You must enable each updated or new package manually and set the package as the default version. |
| In the Automation
page, column customizations made on the Files and
folders are not retained when you navigate away from that
page. For example, if you customize the columns in the private workspace,
move out, and navigate back to the private workspace, the previous
customization is not retained. It returns to the default
view. Similarly, searches and customizations such as filters, sort orders, custom columns, and partially completed edits are not retained when you navigate away from the page. |
|
When you run the v1/audit/messages/list API in Control Room swagger, the following error message is displayed: Workaround: Run the v1/audit/messages/list API using Postman application to avoid the error. Service Cloud case ID: 01988096 you |
| When you check in a robot or a file, it might not reflect immediately in the
public workspace and takes sometime to appear. Recommendation: Ensure that you do not attempt to check in the same robot or a file again while the check in is in progress. Service Cloud Case ID: 02067111 |
| Limitations from previous releases |
|---|
|
When you run a robot in the Google Chrome or Microsoft Edge browser, use the Si, Boucle, or Attendre action, select the webpage from the list of active tabs in the Browser tab, close the browser window, and then run the robot, the robot might take two minutes to open the webpage in the browser irrespective of the timeout value mentioned. Workaround: Move the Si, Boucle, or Attendre action inside the If block and use the Application is running condition with same browser application to check whether the browser is running. |
|
You will encounter an error when you run a standard workflow in the SAP BAPI package. Workaround: To execute SAP BAPI, use the Run Function call (RFC) with a combination of Create function, Set or Get field value, Set or Get structure, and Set or Get table actions. |
When you migrate a robot that
contains , after migration, the robot encounters the
following error: No node found at XPath while executing the Get
Single node command
Workaround: If the XPath expression is not starting with
(/) , apply XPath starting with “/“
so that at the time of execution, the modification can be skipped or the
XPath expression can be designed to get the desired result. |
|
When you use the Capture action with the Enregistreur package (version 2.9.x or earlier) to navigate to another web page in the Google Chrome browser (version 105.0 or later), and then use another Capture action to automate objects in the navigated web page, the robot might encounter an error. Workaround: Before you use the action in the robot, maximize the Google Chrome window . |
| When you use the Si package, add a specific condition with a variable, then add specific conditions within a group, save the robot, and if you rename the variable that was used, the name of the variable might not update for the Group conditions but is only updated for the conditions in the Condition tab. |
| Command prompt API allows you to switch the device registration even if the Allow devices (single user) to be switched to another Control Room without reinstalling bot agent option is disabled. |
| When you update from Automation 360 v.25 to a later version, although you enabled
code analysis in the Control Room, the rules set in the
policy are not retained after the update. Workaround: Before updating, we recommend that you keep a note of the rules enabled in Automation 360 v.25 and then re-enable them after updating to a later version. |
| When you uninstall Automation 360 from the Control Panel, the name of the file is displayed incorrectly (for example, 3e592.msi) on the User Account Control window. |
| While running a robot in debug mode, the robot will fail if the variable size gets greater than 3 MB. An error message appears showing that a variable has exceeded the 3 MB limit. |
| When you set the default package version using the
Update bots to default package version option
for robots in the public workspace that are using the
action, the Robots de tâches do not display the
session name and file path values.
Workaround: Perform one of the following workarounds:
|
Updates to the interface
| Automation Workspace |
|---|
The Max auto retry
attempt option is added to reprocess the failed WLM work
items automatically. |
The drop-down menu
in the Éditeur de robots now includes an option to open a menu
for keyboard shortcuts. Keyboard shortcuts |
The Device(s) from my device
pools and Run as users default
device(s) options are added in the Edit the
device(s) permission to manage registered and
non-registered devices. |
The gMSA option enables you to manage your domain
accounts across multiple servers.
|
The Custom number of bot
runners option allows you to choose the number of Bot Runners that you want to use to run robots.
|
| The Automation Anywhere
Debugger tool is now available within the Bot
Assistant utility to provide a better user experience.
|
Updated and intuitive icons for all the actions and
contextual help for Database and Email actions. Enhanced user experience through intuitive icons | Quick assistance at hand for the developers in the Bot editor |
The drop-down menu in the Éditeur de robots now includes the Capture and run with
admin privileges option that enables you to capture
objects on applications running in administrator mode. |
Contenu lié
- Automation 360 Notes de version v.27
- Publication de Process Discovery v.27
- Version Automation Co-Pilot pour les utilisateurs professionnels v.27
- Publication de IQ Bot et Document Automation v.27
- Publication de Bot Insight v.27
- Packages mis à jour dans la version v.27
- Mise à jour vers la version v.27
- Mises à jour de la migration pour la version 27
- Extensions de navigateur pour Automation 360