Automation 360 v.26 Release Notes
- Updated: 2024/04/24
Automation 360 v.26 Release Notes
Release date: 6 October 2022
Review the top 5 features as well as other new features, enhancements, fixes, and limitations in the Automation 360 v.26 release. Automation 360 and IQ Bot are on Build 15459 (for On-Premises and Cloud).
We have released updated builds for fixes after the Automation 360 v.26 GA build, which was Build 15436. For information about the fixes in these updated builds, see Updated release builds.
Highlights of this release
Here are the top 5 features in the v.26 release:
- Embedded automation with OAuth 2.0
- Business users can directly access authorized automation from within
their favorite business applications, without having to open a new
interface or learn a new app. OAuth 2.0 enables seamless authentication
across systems, reducing complexities of system-specific sign-ins.
Learn more: Embed automations in your application using Automation Co-Pilot.
- Coding standards through code analysis
- Administrators can establish coding best practices by setting a code
analysis policy and improve their team's code to quickly find and
correct rule violations. They can select which rules to check for and
enable summary reports for a snapshot of all bots within
a project.
Bot builders can quickly check the status of their bots and receive feedback on what to fix, speeding up bot development and deployment and promoting coding best practices.
Learn more: Code analysis.
- Package role-based access (RBAC)
- Administrators can tailor package access to the business
needs and expertise of bot developers and enforce access
policies for custom groups. They can maintain policy control and ensure
confidence and ease-of-use for developers by providing group-based package access with clear policies.
Citizen developers can access simpler packages and build easy-to-complete automation, and professional developers can access a broader set of complex packages.
Learn more: RBAC on packages.
- Salesforce integration with command package
- RPA developers can build robust integrations with Salesforce through
direct API interaction. They can automate repetitive processes involving
access and updates to Salesforce data, enabling business users to focus
on high-value business tasks such as strategic planning and
optimization. Commands available include authentication, database
querying, record updates, and file processing.
Learn more: Salesforce package.
- Automation 360 integration with Google Cloud Apigee
- RPA developers can fast-track end-to-end automation development by
combining API components from Apigee and RPA bots from
Automation 360 to access any data in the enterprise.
Our prebuilt integration packages make the integration
seamless, enabling you to drive more value from reusing existing assets
created by your organization's automation teams.
Learn more: Apigee integration.
Updated release builds
We have released the following updated builds:
-
Build 15459 Service Cloud case ID: 01941769, 01945068This build is updated to include 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.Note: This issue exists only in Automation 360 v.26 release. For v.26 On-Premises customers using or planning to use MFA with database authentication, we recommend that you install this update at your earliest convenience. No action is required from customers on other Automation 360 releases.
-
Build 15450 with fixes for the following issues:
- 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 (Service Cloud case ID: 01911410, 01920508).
- When you have large and complex bots with many dependencies and if the size of the deployment messages that are sent from the Control Room to the Bot Agent is more than 2 MB, the bots run successfully. (Service Cloud case ID: 01882630).
- The following IQ Bot issues were fixed:
-
IQ Bot can now perform post-processing on a field
if the custom logic uses Python script containing single quotes,
such as
print('Test')
. - If your IQ Bot custom logic uses the
Pandas
library, the script no longer needs to have theimport Pandas
statement. -
IQ Bot can now perform post-processing on a field
if the custom logic uses Python script containing characters
from non-Latin languages (Unicode characters), such as
äöüñй
.
-
IQ Bot can now perform post-processing on a field
if the custom logic uses Python script containing single quotes,
such as
- Security fixes for Cross-Site Scripting (XSS) vulnerabilities (Service Cloud case ID: 01843148).
-
Build 15443 (for US-East and US-West regions only) Service Cloud case ID:
01911410, 01920508
This build is updated to include a fix for the issue related to the manual dependency file that is shared between multiple parent bots upon export and import. If one of the child bot files is exported and imported into the Control Room with overwrite options in the import process, then links to the manual dependency are unlinked from other parent bots. Use Bot Agent version 21.222 for this issue.
-
Build 15439 (Japan region only) Service Cloud case ID: 01911093,
01911209, 01911190, 01911116, 01911259
This build is updated to include a fix for the following issue: Cannot retrieve values assigned to global values having Japanese characters after upgrading Automation 360. Build 15439 is available for download for On-Premises customers who need this fix.
What's new and changed in each product
Go to the following pages for details on all the updates (what's new, changed, fixed, and limitations) in each product: