Automation 360 v.34 Community Edition Release Notes
- Updated: 2024/11/12
Automation 360 v.34 Community Edition Release Notes
Release date: 27 September 2024
Review what's new in the Community Edition of the Automation 360 v.34 (Build 26372) release. Build 26372 replaces Build 26366.
For more information on updating to this release, see these resources:
Updated release builds
We have released an updated Build 26372 which contains the following:
- Fix for an issue where Task Bots were not visible when they were added using the Run action in the Task Bot package from a parent bot (Service Cloud Case ID: 02163129).
- Fix for an issue where the Watched variable in the debug mode displayed incorrect value (Service Cloud Case ID: 02165726).
- Fix for an issue where actions in the Dictionary package were missing variables of type Any (Service Cloud Case ID: 02165977).
- Fix for an issue where the Extract field action in the PDF package failed to save the extracted value in dictionary and string variables.
We have released an updated Build 26366 that includes a fix for an issue where run-time compilation error occurred in automations with variable mapping of type Any when there was a reference to another automation (Service Cloud Case ID: 02161012).
Automation Workspace
| What's new |
|---|
Debug
enhancements
|
| New enhanced expression
builder
We have made the process of creating expressions more intuitive to enhance the experience of developing automations. In the editor, the process to insert a variable or build an expression manually in the action properties is now simplified and easy to use, without requiring a deep understanding of expression patterns. You can now quickly create simple to complex expressions, saving you valuable time. |
| Option
to ignore pop-ups in the Bot editor When you create or open an existing bot, you can now test the resiliency settings by enabling the pop-up handler feature before running the bot . This ensures a successful execution without any runtime issues. |
| What's changed |
|---|
| Set
a limit on the size of the upload file (Service Cloud
case ID: 02085500) The File size upload limit option is now updated to enable Control Room administrators to set the limit on the size of a file that is being uploaded by other users. |
| Bot Agent version change
notification After you update to this release, an update notification alert is displayed in the Notifications section of the Control Room when there is a change in the major, minor, or a patch version of the latest Bot Agent. |
| Generative Recorder configuration
settings In the Recorder package (version 3.1.5 and later), the Generative Recorder configuration settings are now visible regardless of whether a Recorder action is added in the Bot editor, ensuring there is no confusion about enabling the fallback option. Note: To save the configuration settings,
the automation must include a Recorder
action. |
Automation Co-Pilot for Business Users
| What's new |
|---|
| To provide an improved
user experience, when you add or resize a new element in a row
of a form created in Process Composer, the form
renders the row and its elements consistently regardless of how
the form was created via the desktop, web, embedded, or mobile
platform. Additionally, each row on a form can contain up to
10 elements with a total combined cell width limited to
100%. When adding or editing elements to a row, if you
exceed either the number of elements in a row, or the
combined cell width is greater than 100%, two new messages
are displayed:
You must adjust the number of elements and/or cell width of an element in the row to proceed. |
When
you add rules to forms in Process Composer, hidden
variables now support all the same
If/Else conditions that are available
for their respective visible form elements, except for the
Has errors condition. This applies to
these specific hidden variable types:
The Has errors condition remains exclusive to visible form elements only. |
| What's changed |
|---|
| When elements in a form have any errors in their property values (such as minimum/maximum, height, and so on), the form Save option will be disabled. In previous Automation 360 versions, the Save option was enabled. If you open an older form that contained errors in their properties, you must resolve the errors before you can save and proceed; otherwise, you can close the form. |
| To better assist users with troubleshooting errors, when they edit a process task in Process Composer, validation error messages now display specific information as to which field needs to be corrected, and any required fields that are missing information are highlighted with a red box. |
Document Automation
| What's new | ||||
|---|---|---|---|---|
| New
navigation to access learning instances We have created a new AI section in the navigation menu, which includes Document Automation and other AI-powered products. This streamlined navigation makes it easy to find and access all our AI-enabled offerings. You can access your learning instances using the new navigation: .
|
||||
| Field-level
validation feedback You now have the option to disable or enable validation feedback for each form and table fields so that users have control over which fields require validation feedback. This option is particularly useful when you need to disable validation feedback for fields that provide desired results without the need for validation feedback or when you need to use alternate solutions such as pre-trained model or generative AI providers to improve data extraction. |
||||
| Support for
new languages in Automation Anywhere user-defined
provider You can now process documents in the following languages when using the user-defined document type and Automation Anywhere (user-defined) provider:
|
