Automation Workspace v.26 release

Review what's new and changed, fixes and limitations, and the feature deprecations in Automation Workspace for the v.26 release.

What's new

Control Room, devices and Bot Agent
Microsoft Windows 11 Enterprise now supported (Service Cloud case ID: 01252605, 1252605, 1253745, 01255134, 01379865, 01801610, 01810148)

We now support Microsoft Windows 11 Enterprise, so you can now install and update the Bot Agent and run bots on the Windows 11 Enterprise operating system.

Bot Agent compatibility

Support for Manifest V3 extensions
Automations that use Google Chrome Manifest V2 based extensions will stop working sometime after June 2023. The deprecation timelines of Manifest V2 based extensions are currently under review and subject to change by Google.This might impact your existing automations that use Manifest V2 based extensions for Google Chrome and Microsoft Edge browsers. Automation 360 v.26 and later includes Manifest V3 extensions by default to support features that use Google Chrome and Microsoft Edge browsers.

You can automatically enable Manifest V3 based extensions for Google Chrome and Microsoft Edge on all the Bot Runner devices by enabling the Browser extensions option from the Control Room. Enabling this option applies the browser extension settings on all the registered Bot Agent devices.

Note: We will continue to support Manifest V2 based extensions for Google Chrome until June 2023. To know about Microsoft Edge Manifest V2 based extensions timelines, see Overview and timelines for migrating to Manifest V3.
Note: Manifest V3 extension is supported on Google Chrome and Microsoft Edge browsers version 91 and later only.

Configure browser extensions | Chrome and Edge Manifest V3 extensions

Bot Agent updates by using installation file from local drive
You can now download the Bot Agent installation file to your local drive as a one-time activity and then update the Bot Agent on several devices by providing the local drive path to the installation file. This way, you can avoid downloading the installation file multiple times from the Control Room for several devices.
Important: This functionality is implemented in v.26 and can be used from v.27. That is, after you update your Bot Agent to v.26, future updates can be performed from the local drive.

Automatically update the Bot Agent | Update the Bot Agent from a local drive

Oracle Database now supported (Service Cloud case ID: 00726728)

We now support Oracle Database, so you can now choose to install the Control Room on Oracle Database.

Note: Oracle database for Control Room installation is supported only in Custom mode and not in Express mode. Oracle Database support on the Control Room starts with the v.26 release.

Installing Control Room using custom mode for Oracle installation | Configure Oracle database type and server | Database requirements

Active Directory mappings filters stored in the database

When you update to a newer version of the Control Room, you no longer have to define the Active Directory mapping filters again after installation. This is because the Active Directory mapping filters defined in the um.properties file are now stored in and can be referenced from the database. However, if you define new filters in the um.properties file, the Control Room references the filters defined in the um.properties file and overwrites the ones stored in the database.
Packages, actions, and Bot editor
RBAC on packages

Based on your business requirements, you can now control the access that Bot Creators have to packages in the Control Room. As an administrator or user with the Manage package permission, you can restrict access to packages to either all the users or users with specific roles.

Depending on the access that is configured by the admin, Bot Creators and Citizen Developers can view and use specific packages:
  • Bot Creators can access a broad set of complex packages and create bots, which can be reused.
  • Citizen Developers can access simpler and easy-to-use packages and build automations quickly.

RBAC on packages | Configure RBAC for packages

Salesforce command package

You can now authenticate from Automation 360 to access Salesforce and run several command actions by using the new Salesforce command package.

Salesforce package

SAP GUI 770 version now supported (Service Cloud case ID: 01793132, 01792775, 1776805, 01792623, 787725, 01805482, 01805479,01792623, 01810356, 01822839, 01851451, 01853577, 01860050)

SAP GUI 770 (patch 6) is now certified and supported with Recorder and SAP package.

Recorder actions supported in various SAP versions

Configure and use custom proxy configuration in REST Web Service package (Service Cloud case ID: 01271527, 01765084, 01839282)

REST Web Service package is now enhanced to support custom proxy configuration for each Delete, Get, Patch, Post, and Put action. This provides you more flexibility in calling REST APIs with different proxy configuration and allow you to create hybrid API automation.

REST Web Service package

Keyboard shortcuts to reduce scrolling

When developing large bots, you can now use keyboard shortcuts to expand and collapse individual or all sections and move through the lines of code quickly instead of scrolling and minimizing sections individually.

Keyboard shortcuts to expand or collapse elements in bot logic

Set value in any editable control field to be blank in SAP application (Service Cloud case ID: 00821861, 01807129)

When you use the Set text action of the SAP package, you can now set the value in any editable control field in the SAP application to be blank. For example, you can set the value in the text field or the date field to be blank.
Loop through emails and move them one at a time (Service Cloud case ID: 00749763, 01807189, 01840743)

You can now loop through all the emails in a mailbox and move one email at a time to a destination folder by using the Move action in the Email package​.

Move action

Configure p12 certificate for SOAP-based automations (Service Cloud case ID: 00757213)

In the SOAP Web Service action, you can now select the p12 certificate file and provide a password for user authentication. With this enhancement, you can now access web services that use the p12 certificate-based authentication (a more secure type of SSL certificate).

Example of using the SOAP web service action

Improved accessibility, usability of content on Terminal Emulator window (Service Cloud case ID: 01609467)

You can now have improved accessibility and usability of the content displayed on the Terminal Emulator window. When you use the enhanced Get text action of the Terminal Emulator package, you can now view and extract all the lines and text present in the Terminal Emulator window and perform an operation based on your requirement.

Using Get text action for Terminal Emulator

Run bots with or without window title matching in letter case

You can now run bots even when the title of a captured window does not match the letter case. For a bot to identify a static window or browser titles and titles with a wildcard character, you can opt for a case-sensitive match if you want the letter case to be matched, or a case-insensitive match otherwise, by using the Case sensitive option.
Control image preview and storage in Control Room during secure recording

You can now choose whether or not the object images are available for preview and stored in the Control Room during secure recording by enabling the Recorder preview image setting. When you enable the setting, the image is previewed in the Bot editor and stored in the Control Room for 60 minutes. If you choose not to preview, images are not captured.

Secure recording | Secure recording mode | Configure Settings

Automate Microsoft Excel spreadsheets from SharePoint

You can now automate Microsoft Excel spreadsheets that are uploaded and shared on SharePoint. Use Excel advanced > Open action to open the Microsoft Excel spreadsheets from SharePoint location.

Using the Open action for Excel advanced

Automate Citrix Virtual Apps in Edge with IE mode

When using the Recorder, you can now automate Citrix Virtual Apps running on Microsoft Edge Chromium with IE mode.
Automate controls using Microsoft UI Automation (COM) technology
For automation, you can now use the Microsoft UI Automation (COM) technology in the following scenarios:
  • Capturing controls with secure recording mode
  • Capturing and automating combo box and list view controls
  • Using Object exists and Object does not exist Recorder conditions in If, Loop, and Wait packages

Capture using specific technology | Actions performed on objects captured with Universal Recorder

Seamless automation of Citrix Virtual Apps and other Citrix applications

With the new Automation 360 remote agent for Citrix, you can now seamlessly automate all types of Citrix Virtual Apps and other Citrix applications that are supported on desktop applications using the Recorder.

The new Automation 360 remote agent for Citrix supports the following browsers and technologies:
  • Google Chrome
  • Internet Explorer
  • Microsoft Edge
  • Microsoft Edge with IE mode
  • Mozilla Firefox
  • Java
  • Electron apps
  • Microsoft Active Accessibility (MSAA)
  • Microsoft UI automation

Installing Automation Anywhere remote agent on Citrix servers | Using the Recorder on Citrix Virtual Apps servers

Important: For information about the supported packages, see Automation 360 previous release versions.
Building and running bots
Implement coding standards with code analysis
You can now implement best coding practices by configuring coding rules in the Control Room. This feature helps you prevent potential errors, improve bot reliability, and makes the code more uniform, accessible, reliable, and efficient.
  • As an administrator or a user with View policies and Manage policies permission, you can configure the code analysis policy for all users.
  • As a Citizen Developer, you can run code analysis to analyze your bots against readability, maintenance, security, and compliance best practices.

Code analysis

Choose specific version of child bot to check out with parent bot (Service Cloud case ID: 01771388)

When you check out a parent bot, you can now choose the version of the child bot to check out. Every version of a parent bot can have different versions of child bot dependencies. With this feature, you can roll back the dependencies while rolling back the parent bot. You can make changes to a specific version of the dependent bot.
Easily move bots and files between folders in the private workspace (Service Cloud case ID: 00733125)

You can now move bots and files effortlessly and without requiring any permissions from one folder to another in the private workspace. With this feature, if a bot is placed in an incorrect folder, you no longer have to clone it in the correct folder and then delete it from the incorrect folder.

Move a bot

Better organization with bulk checkin of related bots and files

You can now select multiple bots or dependent files from different folders that belong to the same process and check them in, in bulk, from private to the public workspace with the same check-in message. You can check in a maximum of 10 parent bots, but there is no limitation on the number of dependent child bots.
Email notifications for failed checkins (Service Cloud case ID: 01598642)

As an administrator, you can now configure sending email notifications to bot developers whenever their checkins fail. Without such email notifications, bot developers will be unaware of their failed checkins because although the checkin status is always logged in the audit log, they cannot access the audit log access without permission. With email notifications, bot developers can know about their failed checkins and retry immediately.
Export work items for offline records (Service Cloud case ID: 01769378, 01798514)

You can now export work items to a CSV file for offline audits and records. With this feature, you can export selected, filtered, or all work items to a CSV file.

Export work items to CSV file

Export and import queues for efficient and flexible usage

You can now export and import queues across development, testing, and production environments. This way, you can create a queue in the development environment, test it in the testing environment, and then promote it to the production environment to efficiently execute business process workload. You can also include work items when importing a queue.

Export queues| Import queues

APIs and integrations
Connect Bot Agent to Control Room through v1/registration/auto API

You can now use the V1/registration/auto API to register and connect your device to a Control Room automatically. You must specify the Control Room URL and the userName properties in the API Request.

Using Auto registration API

Fetch execution details for specific execution IDs with new Control Room API

You can now fetch the execution details, such as botOutVariables and CallbackInfo, for a specific execution ID by using the new API endpoint, V3/activity/execution/<id> API.
Authorization with bearer token

Automation 360 supports the Authorization header with a Bearer token for API requests to the Control Room. This header was previously unsupported and ignored on API requests. Obtain the Bearer token from our OAuth services. All API calls must contain either an authentication token from Authentication API (generates JSON Web token) or a bearer token from OAuth services. You cannot use both together in an API.

What's changed

Control Room, devices, and Bot Agent
Missed schedules redeployed automatically

You can now ensure that schedules missed because of Control Room shut down (Control Room maintenance or update) are automatically redeployed.

When you use the Redeploy the schedule again option, an audit log entry identifies the event type as Schedule misfired, and the bot is automatically redeployed after the Control Room is restarted.
Low disk space issues resolved with automatic deletion of temp files

Automation 360 now supports automatic clearing of the files in the temp folder, thereby resolving low disk space issues.

During bot import operations, temporary files were written to the following path, leading to increased usage of disk space and resultant low disk space issues: C:\Users\<aa cr admin account>\AppData\Local\Temp. As a result, the bots failed, and the temp files had to be cleared manually.
Enhanced Active Directory role mappings page

The Active Directory role mappings page no longer has default validation of mappings.

Validating all the role mappings can take a longer time on slow networks and with a higher number of mappings because it requires communication between the Control Room database and the Active Directory server. Also, changes in security groups and roles are infrequent and do not require frequent validation on this page. The Active Directory role mappings page now displays only the list of mappings which loads at a faster speed as validation of mappings is not done.
Enhanced autologin functionality for Bot Agent (Service Cloud case ID: 01788805)

Bot Agent autologin now works successfully even if the Interactive logon: Do not require CTRL+ALT+DEL group policy is disabled.

Previously, for the Bot Agent to autologin successfully, you had to enable this group policy, which was not possible due to the security policy. As a result, Bot Agent autologin failed.
Improved administration for WLM automations
You can now view all the queues with the AAE_Admin role. Also, you can pause, resume, and stop all WLM automations.
Note: If you are not an owner, participant, or consumer of that queue, you can view only queue names and not the queue details.
Packages, actions, and Bot editor
Run DLL file without namespace (Service Cloud case ID: 01765712)

You can now run a DLL function even if the namespace is not specified because the Enter the namespace field in the Run Function action of the DLL package is now optional.

Note: The package versions are now automatically added when DLL or Excel session variables are created. Previously, an issue in Automation 360 v.25 prevented package versions from being added automatically when DLL or Excel session variables were created.
Casing and format changes in Technology and Control types

When you use the Recorder to capture objects, you can now read and identify the names of technology types and control types easily because the names of the properties now use a more user-friendly casing and format. For example, MS_ACTIVE_ACCESSIBILITY is renamed Microsoft Active Accessibility.
Loop condition evaluated with every iteration

When you run a sequence of actions repeatedly for a specific number of times within a loop, the end condition within the loop is now evaluated in every iteration.

For example, when you loop through a Data Table that has 10 columns, enter dynamic values of column count for the end condition in the loop, use the Data Table > Delete column action to delete the column of index 0 inside the loop body, and then run the bot, the bot deletes a column in every iteration. Hence it reduces the iteration count because the loop end condition is evaluated in each iteration.

Fixes

Build 15459: This build includes the following fixes (along with fixes from the previous builds):

A critical security fix for the issue related to Multi-Factor Authentication (MFA) when used with database authentication. This vulnerability is not applicable when using SAML or AD authentication. For more information on this security fix, see Unexpected behavior observed with Two Factor Authentication post A360.26 upgrade, where a valid authenticator code alone is sufficient to login to CR, in spite of an incorrect password.

Service Cloud case ID: 01941769, 01945068
Build 15450: This build includes the following fixes (along with fixes from the previous builds):
If you have large and complex bots with many dependencies and if the size of the deployment messages that were sent from the Control Room to the Bot Agent is up to 5 MB, then the bots will run without failure.

Previously, bots were failing to execute when the size of the deployment messages that were sent from the Control Room to the Bot Agent was more than 2 MB.

Service Cloud case ID: 01882630
When you import a bot or file that is a manual dependency of other bots using the overwrite option, the import process no longer removes the dependencies from the other bots.

Previously, manual dependencies were removed for the overwrite option from the other bots during bot import.

Service Cloud case ID: 01911410, 01920508

You can select a path containing a dollar sign ($) in a folder trigger for a file and folder, and the bot will execute successfully. Previously, the bot failed when you selected a path containing a $ in a folder trigger for a file and folder.

Service Cloud case ID: 01829534

Build 15443 (for US-East and US-West regions only): This build includes the following fixes (along with fixes from the previous builds):
When you import a bot or file that is a manual dependency of other bots using the overwrite option, the import process no longer removes the dependencies from the other bots.

Previously, manual dependencies were removed for the overwrite option from the other bots during bot import.

Service Cloud case ID: 01911410, 01920508

Build 15439 (Japan region only): This build includes the following fixes (along with fixes from the previous builds):
You can now successfully retrieve values assigned to Global values with Japanese characters after updating the Control Room to the Automation 360 v.26 release.

Service Cloud case ID: 01911093, 01911209, 01911190, 01911116, 01911259
Build 15436: This build includes the following fixes:
You can now successfully delete a device from the device pool without any error.

Previously, when you deleted a device from the device pool, it was deleted from the Control Room but remained in the DEPLOYMENT_ALLOCATION_QUEUE table. Hence, the device could not be deleted and an error was shown.

Service Cloud case ID: 01791502, 1840575
If you run a bot from the Bot editor workspace for debugging using the Run from here option and if the bot contains packages that use the session (Local or Global session), the following compiler error no longer occurs: Unable to find any open session

Service Cloud case ID: 01080318, 01759454, 01785168, 01790014, 01786670
In a multi-user environment, for simultaneous bot deployments, bot launcher logs are now generated for all the users.

Previously, in such cases, bot launcher logs were not generated for all the users.

Service Cloud case ID: 01759506
You can now successfully list a scheduled task, and the following error no longer occurs: Unknown timezone ID:US-Pacific-New

Previously, an unsupported time zone could be selected, which resulted in this error.

Service Cloud case ID: 01759074
If a device is shared between a Bot Creator and a Bot Runner, when you try to edit a schedule, the following updated message is now displayed: UNKNOWN: All runAsUser(s) should have default device as no pool is provided. RunAsUser(s): [dprunner] does not have a default device or that device is shared with a bot creator

Previously, if a device was shared between a Bot Creator and a Bot Runner, when you tried to edit a schedule, the following incorrect message was displayed: Automation failure due to deploy failure

When you update the Bot Agent from user level to system level, you can now capture objects using the Recorder actions or from a window list in a Google Chrome browser. You no longer have to manually delete the registry entry in Windows from the current user level (HKEY_CURRENT_ USER).

Service Cloud case ID: 00731155, 00778022
After connecting to a device, when you set the global cache location to an invalid path, an audit log entry is generated against the device, and the default global cache path is now used.
Note: Depending on the device used and the path you specified on your drive, validation of the default cache path might not be supported.
When you want to edit a DataTable variable in debug mode, you can now scroll horizontally to view all the columns in the DataTable variable.

Service Cloud case ID: 01818834
In the FTP / SFTP package, you can now create bots using actions such as Delete files, Put files, and Get files even if the file name contains characters such as the comma (,) and the colon (:).

Previously, characters such as the comma (,) and the colon (:) were not supported in file names.

Service Cloud case ID: 01772186
You can now run an Enterprise 11.3.3 bot from Automation 360 in the Enterprise 11 Control Room by using the Run action.

Previously, the Run action did not work for v.11.3.3 because the device V1 API was not working with an empty filter for release 11.3.3.

Service Cloud case ID: 00825696, 01747999
You can now successfully connect to the Excel or Access (Microsoft Office 2016 or later) engines with ODBC drivers.

Previously, if you tried to connect frequently to the Excel or Access (Microsoft Office 2016 or later) engines with ODBC drivers, bot execution failed intermittently.

Service Cloud case ID: 01762290, 01755335, 01778149, 01778899, 01793064, 01788154, 01810754, 01806851, 01811703, 1815437, 01807133, 01799364, 01755642, 01749480, 01767869, 01807133, 01818989, 01815300, 01826839, 01804882, 01842384, 01846477, 01762300, 01331003
When you send an email with multiple file attachments and if attachment size exceeds 24 MB, the bot now waits for 120 seconds before encountering a timeout error.

Previously, when you sent emails with a large file attachment, bot execution failed after 30 seconds if the attached file exceeded the file size.

Service Cloud case ID: 01763214
When you use the Connect action to connect with the EWS protocol, the Send email action and read email now print the email message body in a new line character in the following scenarios:
  • When you create a bot and connect with the EWS server, then use the Loop action to read email as a plain text messages, and then use the Log to file action to log text into a file.
  • When you use the Send email action and connect with the EWS server with OAuth authentication to send email.

Service Cloud case ID: 01770645, 01780628

In the Email package, when you use the Move all action and establish a connection with the EWS server, if the destination folder contains any of the following special characters in the folder name, then use a backslash (\) as escape character before the special character: , + , * , ? , ^ , $ , ( , ) , [ , ] , { , } , | , \

For example, if the destination folder name is "4) folder name", enter it as "4\) folder name".

Service Cloud case ID: 01803958

If your bot contains an error, Bot error now shows the correct line number of the error within the Finally block in the following scenario: When you add the Try/Finally block around the corresponding action, then insert more actions in the Finally block, and then save and run the bot.
You can now successfully upload files whose file names are in the Japanese language by using the Rest web service action with multipart form data.

Previously, file upload did not work for files whose file names were in the Japanese language.

Service Cloud case ID: 01801767

You can now use the Terminal Emulator package to perform tasks associated with the terminal without any issues. We now provide support for the Start PC Command (STRPCCMD), so when you run the bot, the terminal now successfully opens the application with the STRPCCMD command.

Previously, when you passed the appropriate key on the Terminal Emulator, the bot did not open the expected application because the STRPCCMD command was not supported in the Terminal Emulator.

Service Cloud case ID: 01816577

In the Terminal Emulator package, you can now use the Connect action to connect with a host machine on which you want to automate a task.

Previously, when you used the Connect action, a black screen was displayed for a few terminal hosts.

Service Cloud case ID: 01823081, 01841800
After migration, when you open a Load Add-ins-enabled Excel file using the Excel advanced > Open action and run a bot, the bot now runs successfully without any error.

Previously, the bot failed because some Excel files with the Load Add-ins option enabled stopped functioning and the workbook was closed unexpectedly.

Service Cloud case ID: 00950745, 01835066
When you use the PDF > Merge documents action and select All pages option in the Pages field to merge all pages of multiple PDF documents into a single PDF document, the output PDF now retains and merges all the attributes such as bookmarks, links, layers, attachments, and signatures from the individual source documents.

Service Cloud case ID: 01792105
When the Recorder fails on a computer where the operating system language is not English, the error message for the bot runtime failure is now shown in the same language as that of the operating system.

Previously, the error message was shown in English even on computers where the operating system language was not English.

Service Cloud case ID: 01813050
You can now successfully extract text from within the captured area of a window using the App Integration package even if the screen resolution is more than 100 percent.
Automate and capture window authentication dialog boxes in the Google Chrome browser using a specific technology with the Recorder.
Bots are no longer stuck when you work with Microsoft Access database queries.

Service Cloud case ID: 01756390
You can now open local files by using the New window option in the Browser > Open action even if Microsoft Edge is your default browser.

Service Cloud case ID: 01799784
At bot runtime, when you assign a new window title to a window variable, the window variable now detects the correct window.

Service Cloud case ID: 01788466, 01791773
You no longer encounter a compilation error in the UI in the following scenario:
  1. Use the Datetime package released with Automation 360 v.23 or earlier to create a bot that uses the Datetime > Assign action.
  2. Then, select the Variable option to add the variable value.
  3. Then run the bot with the package released with Automation 360 v.24 or later.
You can now successfully capture objects from applications that are launched from a Citrix machine.
Note: This fix is available only with the new Automation 360 remote agent, which you can use with the updated Recorder package (version 2.8.6-20220823-160834).

Service Cloud case ID: 00831939
When you assign a window title to a window variable, if the variable field has an empty regular expression value, the bot no longer passes it without scrutiny. Instead, the following error message is now displayed: Unable to find the window '<window_name>'. The provided regular expression ‘<regular_expression>' is invalid. Please provide a valid regular expression for the variable '<variable_value>’.
When you merge multiple PDF documents by using the PDF > Merge documents action, all the form field attributes in Adobe Acrobat are merged and the output PDF document is now rendered properly.

Service Cloud case ID: 01760279, 01792301
When you use the If > Folder does not exist condition to determine whether a folder does not exist, if the specified folder exists, the bot now successfully recognizes the folder and does not attempt to create it again.

Previously, because of the presence of leading and trailing spaces in the input folder path, the bot failed to recognize an existing folder and hence attempted to create the folder, leading to an error.

Service Cloud case ID: 01466067
If you migrate a bot and select the HTML Tag, HTML InnerText, and HTML type properties and then select HTML-type properties in Search Criteria, the bot now successfully locates and identifies the object and performs the selected action.

Service Cloud case ID: 00829817, 01757049, 01761452, 01822711
When you use the Recorder package for the Get property action, the correct values are now displayed for the top, left, height, and width properties.
Note: The Get property action does not display correct values for cross-domain iFrames elements.

Service Cloud case ID: 01251758
The AISense Recorder package now works as expected when you use the Windows 10 operating system in the Japanese language. Because UTF-8 is now enabled, you no longer need to use any workaround.

Service Cloud case ID: 01821267, 01822433
When you use 2.8.0-20220601-034227 and later versions of the Recorder package, the automated bot now returns the correct value for the HTML InnerText property in Google Chrome and Microsoft Edge browsers.

Service Cloud case ID: 01257098 , 01754795, 01791073, 01787461, 01813080, 01846403
For WLM queues, the date is now displayed in the correct format as YYYY-MM-DD.

Previously, this date was shown in the years ago format, which did not match the date format in the CSV file and was confusing.
In a multitenant environment, when you upload a work item file to a queue in one of the tenants, the In progress tab now displays the correct file upload status only in the corresponding tenant.

Previously, the In progress tab displayed the upload status for all the tenants.
When a WLM automation is in progress, an administrator can no longer delete the user who created that automation.

Previously, the user who created an automation could be deleted, after which that automation could not be paused or resumed by another user.
When you stop a WLM automation, work items are no longer stuck in the ready-to-run state and are now moved to the New state.

Previously, when you stopped a WLM automation, a few work items were stuck in the ready-to-run state and could not be deleted.
After you change any configuration field in the Administration > Settings > Devices > Advanced options settings in versions prior to v.25, if the Control Room is updated to v.25, the Global Cache Location is now set to the default C:/ProgramData/AutomationAnywhere/GlobalCache value.

Previously, in such cases, no value was shown for the Global Cache Location field, which was confusing.

Service Cloud case ID: 01869048
When you use the Run bot option to run a bot in the Activity > Historical > View page for any activity, the bot now runs successfully.

Previously, in such cases, bot execution failed with an error.
When you import a bot that contains manual dependencies, for the overwrite option, the import process now removes the manual dependencies.

Previously, during bot import, the manual dependencies were not removed for the overwrite option.

Service Cloud case ID: 01813452
When you import a bot into a folder, if a folder with the same name but different letter case already exists in the repository, bot import now fails with an error.

Previously, in such cases, bot import was successful, but the imported bot failed at the time of execution because of the wrong folder path.

Service Cloud case ID: 01270324, 01816507
You can now successfully access all the folders in the public workspace without any issues.

Previously, when you imported and cloned a bot under a folder in the public workspace and then tried to access that folder, sometimes an error occurred, and the folder could not be accessed. This occurred some times when there were more than 2100 folders under the bots directory.

Service Cloud case ID: 01852748
When you update from Enterprise 11 to Automation 360 or update from an earlier version of Automation 360 to a later version, the earlier defined group mappings are retained are retained, even when the Distinguished Name (DN) column of the mapping entries are empty in the database.

Previously, some of the earlier-defined group mappings were deleted due to the empty value for the DN column.
After you update to Automation 360 v.22 or later, the Repository Management (v2/repository/file/list) API now returns the correct file size as response output.

Previously, the Repository Management (v2/repository/file/list) API returned the file size as zero in the response output.

Service Cloud case ID: 01151460

The Azul Zulu JDK is now updated to version 11.0.15+10. The previous version, 11.0.14+9, contained some vulnerabilities.

Common Vulnerabilities and Exposures (CVEs) for this version are as follows: CVE-2022-34169, CVE-2022-21540, CVE-2022-21541, CVE-2022-21549, and CVE-2022-34169

Service Cloud case ID: 01854652, 01868897, 01857973, 01854652, 01887083
When you create a folder (through the create folder API option), you can no longer have an empty space as the first character for the folder name as it is now automatically removed.

For example, while creating a folder, if you enter the name as ' sales', the folder is created with the filename as 'sales'.

Note: Before updating to this release, if you had created any folder that had an empty space at the beginning of the folder name, you could export it without any issues. However, importing that folder was not supported. To resolve this issue after updating to this release, unzip the exported package, open the manifest.json, and remove all occurrences of the empty space in the manifest, and the folder name. You can then zip the package and import it again.

Limitations

When you connect to the Microsoft Access Database with JDBC and specify the database path, and if you use the following specific aggregation functions in the query, an error occurs when you run the bot.
ASC, ATN, SQR, CBOOL, CCUR, CDATE,
CDBL, CDEC, CDATE, CDBL, CINT, CLONG, CLNG,
CSIGN, CSTR, CVAR, DATEADD, DATEDIFF, DATEPART,
DATESERIAL, DATEVALUE, FORMAT, IIF, INSTR, INSTRREV,
ISDATE, IsNull, ISNUMERIC, LEFT, LEFTS, LEN, MID,
MONTHNAME, DATE, NOW, NZ, SIGN, SPACE, STR, TIME, VAL,
WEEKDAYNAME, WEEKDAY, STRING, TIMESERIAL, CONCAT
Workaround:
  1. Go to Administration > Settings > Devices > Advanced options > Bot launcher JVM options and set the value as follows: -Dhsqldb.method_class_names=net.ucanaccess.converters*
  2. Restart the Automation Anywhere Bot Agent service.
External key vault integrations are not supported on Oracle Database.
Not all missed recurring schedules are redeployed with the Redeploy the schedule again option. Also, only one entry is shown for the missed recurring schedules in the In progress tab.
As an IQ Bot user, you can check out only the latest version of a process. You cannot check out previous versions of a process because version check is performed based on the Automation Anywhere file version and not the Git version.

The OAuth2 configuration settings in the Control Room will not enable you to connect to the OAuth2 service at this time. Customers planning an OAuth2 integration with our partner application should expect the service to be available by November.

In the Oracle Database environment, you cannot view a checked-in bot in the Public folder because version check is performed based on the Automation Anywhere file version and not the Git version.

Workaround: To view a checked-in bot in the Public folder, you must refresh the Automation page manually by using the Refresh button.

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 using the Run bot with queue option, the queues are not deployed. Also, no errors are shown in the Audit log or Activity page.
For regular or scheduled automations using the unattended Bot Runners, bot deployments remain in the queued state and accumulate on the In progress page for these following scenarios:
  • If the devices are down or not available.
  • If a run-as user is busy executing the bot.
For devices not in the deployment state, if the number of queued bots reaches 500, it blocks the bot deployments for all devices or for all run-as users.
Workaround: To run the blocked deployments, perform one of the following actions:
  • Select the queued jobs on the In progress page and move it to the Historical page
  • Reconnect the Bot Runner devices.
When you set the default package version using the Update bots to default package version option for bots in the public workspace that are using the Excel Advanced > Open action, the Task Bots do not display the session name and file path values.
Workaround: Perform one of the following workarounds:

Service Cloud case ID: 01905290, 01882083, 00712719, 00728499, 00737694, 00803673, 01255722, 00838604, 00772147, 01760236, 01762679, 01771416, 01761859, 01782588, 01778220, 01784255, 01789551, 01809167, 01818690, 01831969, 01813413, 01287311, 01923711, 01927867

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 use 2.6.1-20220428-010714 or later versions of the Recorder package to automate a web page on Microsoft Edge browser, the Recorder might not be able to perform Click or Left click actions on the JavaScript alert, prompt, and confirmation pop-up windows.

Workaround: For performing the click actions successfully, downgrade the Recorder package to 2.5.4-20220309-151830 version or earlier.

When you use the Browser > Close action to close a tab or a window opened in the Microsoft Edge browser, if only one Microsoft Edge browser window is open, the bot encounters the following error: Error occurred while closing the tab

When you run a bot in the Google Chrome or Microsoft Edge browser, use the If, Loop, or Wait action, select the webpage from the list of active tabs in the Browser tab, close the browser window, and then run the bot, the bot might take two minutes to open the webpage in the browser irrespective of the timeout value mentioned.

Workaround: Move the If, Loop, or Wait action inside the If block and use the Application is running condition with same browser application to check whether the browser is running.
When you run a stored procedure in Oracle and it returns SYS_REFCURSOR, the Run stored procedure action is not closing the cursors. As a result, after the maximum cursor limit is reached, this action results in an error.

When you migrate a bot that contains XML command > Get single node, after migration, the bot 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.
While running a bot in debug mode, the bot 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 use the Browser > Open action to automate a browser window running on Google Chrome and Microsoft Edge browsers, then from the browser window, select More tools > Name window option to update the title of this window during bot run and then when you try to run the bot with the updated window title, the bot might fail.

When you use the actions in the App Integration package to extract text from a window, the bot might not be able to detect the new UI of the Windows 11 operating system and capture the text.

Workaround: Enable the old classical UI in Windows 11 operating system. See Restore Old Classic Notepad in Windows 11

When you use the /v2/repository/file/list, the response lists bots restricted by user role. If you use this API as an AAE_Admin, you can view bots from the private repository in the response. Whereas if you use this API as a bot creator, you can view system bots (recorder) in the response.

Workaround: Use the /v2/repository/workspaces/{workspaceType}/files/list.
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.
You will be unable to add locker managers and participants when creating a locker.

Workaround: After creating a locker, edit the locker and then add the locker managers and participants.

Service Cloud case ID: 02004160
While scheduling a Task Bot, API Task, or process, an error is not displayed when you select the EST, HST or MST time zones although these are no longer supported.

Service Cloud case ID: 02145509

Feature deprecations

Review features and capabilities (from Automation Anywhere or other third-party vendors) that are deprecated or nearing deprecation to understand how they impact your automation.
Automation Anywhere Mobile app deprecated

The Automation Anywhere Mobile app is deprecated as of July 2022 and will not be updated to subsequent versions of iOS and Android. The mobile app is no longer available and no further support will be offered. A replacement product is currently not available.
Tesseract OCR v3 deprecated

Tesseract OCR version 3 is deprecated as of September 2022. If you have created learning instances using Tesseract OCR version 3, we recommend that you plan to train your learning instances with alternative OCRs (including Tesseract4 OCR) before you update to Automation 360 v.26.

Deprecation of Tesseract OCR v3

Deprecation of IQ Bot Extraction package

The IQ Bot Extraction package has been deprecated as of September 2022. As part of Automation 360 v.26, IQ Bot will no longer support pretrained machine learning models for invoice data extraction.

To move your bots from the IQ Bot Extraction package to Document Automation, see IQ Bot Extraction package.
Automation Anywhere for Excel deprecated

Automation Anywhere for Excel has been deprecated as of January 2022. The plug-in is no longer available to download as a product. However, support will be offered to current customers already using the product.

A replacement product as a plug-in for Microsoft Excel is not available. In Automation Anywhere for Excel, this action was triggered from within the Excel application. However, as an alternative, new customers can develop bots for Excel within Automation 360 Automation Workspace and use input variables to allow specifying file names, worksheets, and ranges for bots to operate on. In Automation Anywhere for Excel, this action was triggered from within the Excel application, whereas now this action is taken from the Automation Anywhere Control Room.
G-Suite Apps package deprecated

The G-Suite Apps package has been deprecated as of September 2022 and it no longer supports using the Connect and Disconnect actions to establish a connection with the Google server and automate tasks.

Recommended: For specific G-Suite applications, the functionality of the G-Suite Apps package is available in the following G-Suite packages:
  • Google Drive
  • Google Calendar
  • Google Sheets
To automate tasks, in the appropriate G-suite package, use the corresponding Connect and Disconnect actions.