Automation Workspace v.32 release
- Updated: 2024/11/13
Automation Workspace v.32 release
Review what's new and changed, and the fixes and limitations in Automation Workspace for the v.32 release.
What's new
| Control Room, devices, and Bot Agent |
|---|
| Pre-built templates
We now provides a faster and more efficient process of developing automations through pre-built templates. You can use these templates to build new automations quickly, adhering to best coding practices. These pre-built templates are tailored to specific use cases that streamline the automation creation process and accelerate and scale automation across the organization. |
| Efficiently manage IdP user
accounts When you integrate the Control Room with your Identity Provider (IdP), your IdP user accounts are automatically provisioned in the Control Room. User account management in the Control Room is simplified in such a way that provisioning and updating of the Control Room user accounts, managing of the Control Room roles, and assigning of the Control Room licenses are managed automatically based on the IdP group mapping that is configured in the Control Room. Note: This feature requires the Enterprise Platform license and is
available only on Cloud. Contact your
Automation Anywhere account representative for more
information about this license. IdP group mapping | Enable SAML automatic user account provisioning |
| Updates to ACC homepage widgets The ACC homepage is now
updated to include the following widgets:
|
| Record bot execution As part of Resiliency settings, the functionality to record automation execution is now available that enables you to review and resolve any errors that might have caused a runtime failure. |
| Export
Automation data to PDF You can now export ACC dashboard as a PDF document to gather the statuses of various automations. |
| Additional
language support for the Secondary email language The
Secondary email language option
in the Notification channels now
supports the following additional languages:
Note: This feature requires the Enterprise Platform license. Contact your
Automation Anywhere account representative for more
information about this license. |
| Transfer ownership of WLM
automation The user who has created an automation or a
user who has the required role permissions can transfer the
ownership of a WLM automation from screen. Note: A user must have the following four
permissions to own the WLM Automation:
|
| Run API tasks in Automation 360 You can run API tasks using the Run now wizard in Automation 360. Note: Running API Tasks in
Control Room requires Enterprise Platform license. See Enterprise Platform. |
| Support for ESXi 7.x and 8.x versions
(Service Cloud Case ID: 02096068, 02098971, 02108215, 02110030,
02112682) You can now install Control Room instances on Microsoft Windows Server 2016 and Microsoft Windows Server 2019 that are installed on VMware VMs that are running on ESXi 7.x or 8.x versions. Operating system, environment, and platform supported for Control Room |
| Packages, actions, and Bot editor |
|---|
|
Generative AI
package
You can use the new Vertex AI: Multimodal Prompt AI (Google Gemini), OpenAI: Run Assistant, and OpenAI: Run Assistant Function actions in the Generative AI package. Vertex AI: Multimodal Prompt AI action is capable of processing information from multiple modalities, including images, videos, and text. OpenAI Assistant actions enables easy integration of Assistants with Automation 360 automations, enhancing productivity and unlocking new possibilities in automation. Vertex AI: Multimodal Prompt AI action | OpenAI: Run Assistant action | OpenAI: Run Assistant Function action |
|
New option in REST Web Service
(Service Cloud case ID: 00746832,00771280, 01803290,
01871977, 01922168, 01922296, 01978860, 02003344) In the REST Web Service package, you can now use the Accept Cookies option to automatically capture session cookies from server responses and include it in subsequent REST calls. |
| Certification
of SAP GUI 800 (Service Cloud Case ID: 02098553) The SAP GUI 800 with patch 4 for Windows is now certified to automate SAP-related tasks. |
| Hide
automation progress window (Service Cloud Case ID:
00516630, 00576840, 00612585, 00764407, 00859343, 01774749,
01973826) After updating to this release, the Hide bot run window is enabled by default and the automation execution progress window is hidden from view. However, you can choose to disable this feature in order to view the progress window. For information on how to disable this feature, see Hide the Automation Runtime Window Enabled with new Run Now/Schedule Wizard (A-People login required). |
| APIs and integrations |
|---|
| Connector Builder Integrate any SaaS app or service effortlessly with our Connector Builder tool, enabling you to create custom connectors in minutes without Java dependencies. Run API Tasks directly from the Control Room for quick and efficient testing and execution, freeing developers from constructing comprehensive process workflows. Note:
Connector Builder is only available for Cloud customers on AWS. This feature
requires an additional license. Contact your Automation Anywhere account representative for more
information. |
| API Task real-time endpoint You can now invoke API Tasks instantly with a real-time endpoint. Generate Task execution URL and Token to execute API Tasks. |
| API for
PROD labelling You can now label an automation for
production. The new endpoint POST
|
What's changed
| Control Room, devices, and Bot Agent |
|---|
|
Support for multiple active user sessions You now have the option to open a maximum of 5 (five) concurrent active sessions from a Control Room. If you already have five concurrent active sessions open and want to log in to a sixth session, the first inactive session is automatically disconnected. |
| Automatically delete
unknown devices (Service Cloud Case ID: 01765115) The Automatically release any automations in unknown state is enabled by default and the unknown automations are automatically moved to Historical activity by default. |
| Add queue running
times When you edit a workload management (WLM) automation (in use queue), you can now use the Add running time option to add multiple automation execution times. |
| Recommendations license
consumption As a license administrator, you can view detailed information about recommendations that are available for Co-Pilot for Automators. You can view details about purchased licenses, consumed licenses, and available licenses on the License details page. |
| Improved
performance in folder operations in the public
workspace Performance is enhanced for folder operations in the public workspace. Expanding folders or sub-folders is now faster, even when you have many files and sub-folders within them. |
Fixes
| You will no longer see duplicate audit entries for the
Run bot deployed event type when you
run bots. Previously, such duplicate audit entries were logged when you ran bots. Service Cloud Case ID: 02097082, 02107966 |
| Domain names are no longer
case-sensitive, and you can manage role mappings between the Active Directory and Control Room.
Previously, the domain names configured in the Active Directory server had mixed cases (Upper/lower cases). As a result, domain names could not be found, and due to this issue, synchronization (sync) of role mappings between the Active Directory and Control Room was not working. Service Cloud Case ID: 01992320 |
| When you log in to the Control Room, you
no longer experience performance issues while performing
operations such as navigating from one page to another, loading
pages, saving the changes, and Check in or Check
out. Previously, when a Control Room administrator added an email address with a trailing comma to subscribe to email notifications, the alert notification job update process failed because the trailing comma initiated a loop and published the same alerts. This loop caused a significant increase in database load, which elevated CPU usage, active connections, and other resource utilization on the database server. |
| A Request ID is now generated for
a successful callback request in the audit logs. Previously, the Request ID response was not always generated. Service Cloud Case ID: 02098704 |
| You can now save the SIEM
integration configuration after you delete request body
attributes from the Control Room, and an error is
not displayed. Previously, the configuration sometimes could not be saved after request body attributes were deleted. Service Cloud Case ID: 02005053 |
| When adjusting the screen resolution of a device, users
can now access the audit entry for the Update device
resolution settings event on the
Audit Logs page. Previously, the event entries were missing from the user interface for this event type, despite a positive result count. Service Cloud Case ID: 02007028 |
|
Fix for an issue where the drop-down menu was grayed out when you edit a selected variable. Service Cloud Case ID: 02120450, 02125663, 02125715, 02125730, 02126149, 02125682, 02126260, 02125734, 02126599, 02126230, 02127111, 02126863, 02127452, 02125289, 02127807, 02127848, 02126068, 02128239, 02127016, 02129361, 02129349, 02129271, 02129290, 02129604 |
|
Fixed some security vulnerability issues. For more information, use the release download link and view the Security & Compliance reports at A-People Downloads page (Login required). Service Cloud Case ID: 01955093 |
| If you are using multi-factor
authentication (MFA) to authenticate your account, you can now
use the Enter key after entering the code on the login
page. Previously, a user had to click the Confirm option to authenticate their account. Service Cloud Case ID: 01989034 |
| You can now create, check-in, checkout, or
export a bot with the same name as the parent
folder even when that bot contains the
Capture
action from Recorder
package. Service Cloud Case ID: 02086676 |
| In the
Audit log screen, the
Status for some of the events is no
longer displayed as both Successful and
Unsuccessful. Service Cloud Case ID: 01996523 |
|
On a multi-user system, the Automation.bot.BrowserAgent.exe process now executes faster when you deploy your bot from the Google Chrome or Microsoft Edge browser. |
| When you check out bots with a
large number of dependencies or metadata, the process no longer
times out and completes successfully. Service Cloud Case ID: 01994310, 01992456, 01975543, 02050574 |
| When you use the option to move a bot from one Control Room instance to another, the activity is
no longer displayed in the Historical
activity page and an automated email is not
sent. Service Cloud Case ID: 01982943 |
When you use the Export filtered
items option to export a larger number (more
than 30,000) of work items, duplicate entries are no longer
added and only the correct number of records as per the applied
filter are captured in the .csv
file.Service Cloud Case ID: 02087833, 02091925, 02110291 |
Workitems are now
added successfully when you upload the .csv
files that conform to the RFC 4180 standard and have values that
contain double quotes in the middle or at the end. However,
ensure that none of these values have the double quotes at the
beginning.Service Cloud Case ID: 01963694 Note: This fix is not
available as part of the standard installation. Contact your
Automation Anywhere Customer Support for assistance on
enabling this feature. |
| After you update to this
release, the Service Account credentials are masked
correctly. Service Cloud Case ID: 02005468 |
| On the
Scheduled activity page, the results
are now displayed correctly when you use Automation
priority column to filter the
activities. Service Cloud Case ID: 02004825, 02081823 |
| When code analysis is enabled
and a policy including variable name pattern API Task rule is applied to a folder, the default
variables generated during the creation of new API Tasks now adhere to this rule. Previously, the default variables created in new API Tasks failed to comply with this rule. |
| An unattended Bot Runner user with a
default device can now use the Run as
self option to deploy the bot
without any issues as the Device pool is
now optional. Earlier, user was unable to deploy the bot if the Device pool
option was not selected. Service Cloud Case ID: 02126192 |
| Conversion output used in a bot
no longer causes runtime errors and the bot
execution completes successfully whether the inline typecast
conversion values are in upper or lower case (such as
$SampleNumber.number:toString$). Service Cloud Case ID: 02127968, 02128187, 02127022 |
| You can now select and edit a
variable or credential from the Simulate
keystroke > Select a
credential drop-down menu. Previously, for some
lockers, users were unable to select or edit these values.
Service Cloud Case ID: 02120450, 02125663, 02125715, 02125730, 02126149, 02125682, 02126260, 02125734, 02126599, 02126230, 02127111, 02126863, 02127452, 02125289, 02127807, 2127848, 2126068, 02128239, 02127016, 02129361, 02129349, 02129271, 02129290, 02129604 , 02130086 |
| You can now rerun bots from the
Activity > Historical
activity page. Previously, a user could not run
bots from this page when the activity
run now feature was enabled. Service Cloud Case ID: 02125969, 02125049, 02125871, 02126187, 02125726, 02129441, 02127257 |
| After updating to this release, the bots no longer appear in the queued state
on the In-progress page. In previous
releases, there might have been some intermittent cases where
the bots would remain in the queued state.
Ensure that you fix these bots manually
before or after updating Automation 360 to
v.32. Service Cloud Case ID: 02109884, 02129759 |
Limitations
| When you try to install Control Room in Google Cloud Platform 2022 Server, Bad Gateway error message is displayed. |
| When the associated Run as user for the WLM automation is deleted from Automation 360, the workitem is still displayed in the Active state |
| Automations created through WLM queue are not recorded in Automation 360, irrespective of the option you have selected in . |
When deploying or scheduling an automation on a device,
the Bot execution recording might fail
intermittently under various conditions such as:
|
| If the functionality to record
automation execution is available and the automation recording
fails due to any of the reasons such as the recording option was
not selected, recording option was selected only for failures
but the execution completed , was unable to record due to system
issues or failed to upload the recording, a generic error
message is displayed. Service Cloud Case ID: 02130216 |
| While transferring the ownership of a WLM automation, all the available users are displayed instead of only the list of users who have the required permissions to own that WLM automation. |
| If the
Assistant window is open and shows a
violation of the code analysis policy, and you delete one or
more actions causing this violation, an error occurs, and the
action cannot be deleted. Workaround: Close the Assistant window and delete the actions from the automation that violate any code analysis policy. |