Database package updates

Review the updates in released versions of the Database package such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.

Versions summary

The following table lists the versions of Database package released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that package version.

Version Release date Release type Bot Agent version Control Room build
5.4.0 17 June 2024 With Automation 360 v.33 (Sandbox) release 21.88 or later 10204 or later
5.3.0 22 March 2024 Package-only; post Automation 360 v.32 (Sandbox) release 21.88 or later 10204 or later
5.2.1 6 December 2023 With Automation 360 v.31 (Sandbox) release 21.88 or later 10204 or later
5.1.0 16 August 2023 Package-only; post Automation 360 v.29 release 21.88 or later 10204 or later
4.12.2 6 June 2023 With Automation 360 v.29 (Sandbox) release 21.88 or later 10204 or later
Note:
  • To download an individual package (updated in an Automation 360 release where you want only the package), use this URL:

    https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar

  • For Database package, the naming convention is: bot-command-database-<version.number>.jar

    For example, bot-command-database-5.2.1.jar

For detailed steps on downloading a package and manually adding it to the Control Room, see Add packages to the Control Room.

5.4.0

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10204 or later
Fix

You create a bot using the Database Connect action with the ODBC connection string, use Excel as a database, then use the Read from action, using Select * into [sheet2] from [sheet1] statement, the bot no longer stuck and now displays an appropriate error message.

(Service Cloud case ID): 02113073

5.3.0

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10204 or later
Fix
The Database package jar file is installed successfully through Cloud updates.

Previously, the scheduled cloud update of packages failed to install the Database package jar file due to an error.

5.2.1

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10204 or later
What's changed

Internal update in packages

Minor update to support API tasks.

5.1.0

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10204 or later
Note: This package version is also available in the Automation 360 v.30 release.
What's new
Database package enhancements (Service Cloud case ID: 01881930, 01981681, 00743352, 01938224, 01946530, 01938224)
The following enhancements have been added to the Database package for Pro and Citizen Developers.
  • Ability to share the Database session across parent and child bots.
    • You can now create a new global session using the Database > Connect action and pass this session from a parent to child bots or reuse this session in other actions of the Database package. This feature ensures data consistency in each bot because you perform the database operations on a standard set of data.
    • You can create a new session variable of the type database session to store the database sessions.
    • The existing session name field has been renamed to Create Database session.
  • In default mode, you can now define connection strings with variables to substitute credentials such as username and password or any other security-related data in the Connect action. You can map these variables with credential vault values to ensure that sensitive information is not exposed in the connection string.
  • You can now connect to any database with the JDBC connection string for the user-defined database option. This helps to significantly reduce development time and maintenance overhead because you are no longer required to automate processes that involve other databases.

Using Connect action for database
What's changed
Changes to storing the database schema in Disconnect action(Service Cloud case ID: 00743352, 01938224, 01946530, 01938224)

In the Disconnect action, if you select the Keep database schema in cache until bot finishes running option and then try to create a new database session after the Disconnect action, while keeping the same session name as the previous one, an error occurs, and the new database session is not created. To avoid this, leave the Keep database schema in cache until bot finishes running option unchecked.

Disconnect action
Fixes
For the Insert/Update/Delete action in the Database package, the 'Stream Closed' error is no longer displayed when you run a large SQL query (up to 65K ASCII text) over an ODBC connection.

Service Cloud case ID: 01991720
Fixed the vulnerabilities reported in the security scan.

Service Cloud case ID: 01967285

4.12.2

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10204 or later
Fix
Fixed the vulnerabilities reported in the security scan.

Service Cloud case ID: 01967285