Automation Workspace v.35 release

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

What's new

Control Room, devices, and Bot Agent
Include global values while importing or exporting bots (Service Cloud Case ID: 00505782, 00747034, 01760643, 01890218, 01940806,01997839, 02004538)

Users or roles associated with the View and manage global values permission can now include global values while importing or exporting bots.

Import bots | Export bots
Manage automation deployment queue
The configuration settings now include the Deployment functionality that enables you to efficiently manage the automation deployment queue by leveraging the following enhancements:
  • The deployment is now automatically added to a queue if the default device is down (Disconnected state) when you run an automation. This prevents automation failures due to device downtime.
  • Queued items that remain unprocessed are automatically archived, which limits deployment delays and enhances the deployment efficiency.

Deployment
New capability to submit templates to Bot Store

You can now build and upload templates to the Bot Store directly from the Control Room. This streamlined process allows different users such as business users, partners, and the developer community to easily create and share templates for various use cases. By contributing these templates to the Bot Store library, you can increase the availability of ready-to-use solutions for everyone.
GitLab support for Control Room (Service Cloud Case ID: 00667771, 00748148, 01768805, 01965209, 01845855, 2082599, 02082464,02087718, 02082464, 02162592)

GitLab is now certified for Git integration with the Control Room.

Integrating Control Room with Git repositories
APIs and integrations
AI Agent Studio APIs

This release introduces new API endpoints that enable you to connect to custom generative AI models. These APIs allow you to define models that are not natively provided by AI Agent Studio. After a model is created using the API, you can then create Model connections and use the model within AI Skills in AI Agent Studio.

  • POST /gai/prompttools/v1/custommodel - Creates a new custom model definition.
  • GET /gai/prompttools/v1/custommodel/vendors/{vendorName}/models/{modelName} - Retrieves the definition of an existing custom models..
  • DELETE /gai/prompttools/v1/custommodel/vendors/{vendorName}/models/{modelName} - Deletes an existing custom models..
  • POST /gai/prompttools/v1/custommodel/list - Retrieves a list of all custom models defined for all vendors within the Control Room.

Custom model definitions | AI Agent Studio API
Policy Management APIs

This release introduces new API endpoints to enable administrators with more granular control and detailed insights into code quality.

  • GET /v1/policy/bot/analysis/download/{filename} - Downloads a detailed CSV report containing the results of a previous code analysis scan.
  • POST /v2/policy/bot/analysis/details - Initiates a detailed code analysis scan for a specific bot automation and returns a comprehensive report of violations.
  • POST /v2/policy/bot/analysis - Initiates a summary code analysis scan for a specific bot automation and returns a concise report of key violations.

v1 - Policy Management API | v2 - Policy Management API

What's changed

Packages, actions, and Bot editor
Enhanced management of automation recordings
Record automation execution feature is now enhanced to effectively and efficiently manage execution recordings with the following capabilities:
  • Recordings that were not successfully uploaded are automatically retried.
  • Recordings that fail to be uploaded within three days are automatically deleted as part of storage management.

Record automation execution
Real time proactive view across all your production automations
The ACC home page is now updated to contain the Monitoring tab that provides the following benefits:
  • Execution status (in-progress, waiting, completed and failed) of all the available automations (such as Task Bots, API Tasks, and Processes) are displayed.
  • Review the status to immediately find any stuck and failed automations.
  • Provides toggle type filter to get all automations that have similar sub-types such as paused, pending executon, deploy failed, and stopped.
  • Export all or specific automation execution details into a .csv file for audit and review.
Note: The feature to view the Monitoring tab requires the Enterprise Platform license. For more information about the supported version for this feature, see Enterprise Platform.

Monitoring
Updated bot check in status (Service Cloud Case ID: 02067111)

An alert is now displayed if you try to check in a bot while the previous check in is in progress.

Check in a bot
Additional columns in the automation data CSV file
When you export automation data as a .csv file, the table is now updated to contain the following additional columns:
  • User Name
  • Licenses
  • Execution Type

Export Automation dashboard
License grouping for Enterprise Platform, Automator AI, and APIaaS licenses

License grouping now includes support for new license types, such as feature licenses, recommendations and API calls, and APIaaS concurrency. With the appropriate license management permissions and Enterprise Platform license, authorized users can view, create, edit, and delete license groups in Control Room. Licenses can be managed by the license administrator. Additionally, to manage license data across groups, tabs named Main Group, Account utilization, and Group Distribution have been added in the user interface when you navigate to Administration > Licenses.

License group management
Audit entry name change to Move activity to history (user)

In the list of audit events, the audit entry name that was previously called Move automation to history is now updated to Move activity to history (user), which is used for logging the action details when a user moves a selected activity to the Historical page.

Audit events list
Support for entering masked input for Client Secret in OAuth connections (Service Cloud Case ID: 02126295)

The Client Secret field in the Manage > OAuth connections page is now masked, similar to a password field. This change enhances security by preventing the secret from being visible in clear text.

Create OAuth connection
External key vault custom secret name for service account (Service Cloud Case ID: 01961519)

While integrating external key vaults with Automation Anywhere Control Room, users can now configure object names without any Automation 360 encoding conventions. This enables users to align to their own organization’s object naming policies.

Custom secrets mapping

Fixes

You will no longer see .png files in audit logs when performing bulk package update of packages that contain PNG metadata.

Previously, .png files were displayed in audit logs in such scenarios.

Service Cloud Case ID: 02139798
You can now use the Bot Scanner to scan automations using EOL features such as EWS API, basic authentication, and Internet Explorer.

Previously, the Bot Scanner utility failed to authenticate with an error: Authentication failed as Username or Password.

Service Cloud Case ID: 02146267
The issue of duplicate Run bot deployed entries in the Control Room audit log for specific schedules has been resolved.

Service Cloud Case ID: 02148949

To pause, resume, or stop WLM automation, you now require only the Manage activity from user’s folder permission. Previously, it was necessary to have the View everyone’s activity permission to perform actions in a queue.

Service Cloud Case ID: 01945392

You can now test endpoints with a string input in the query parameter in the Connector Builder.

Previously, this caused tests to fail with a 500 error, even though the connector would function correctly in automations.
Audit log captures the Bot promotion Setting changes correctly.

Previously, when you add and delete Control Room URLs from Administration > Settings > Security Settings > Bot promotion Setting , the changes were not logged in the Audit log entry.

Service Cloud Case ID: 02137549

Limitations

In the Monitoring tab of the ACC home page, the details for the number of automation runs that are displayed in the In-Progress widget do not appear in the table at the bottom if the automations were queued beyond the selected time range.
When you click the Import bots option to import automations to Control Room, the functionality might fail intermittently with an error message.