What's new in IBM Robotic Process Automation on Red Hat® OpenShift® Container Platform 21.0.7 Fix Packs

This release notes groups all the fix packs from the 21.0.7 release.

IBM Robotic Process Automation 21.0.7 is designated as a Long Term Support Release (LTSR). Active LTSRs will continue to receive maintenance and security updates throughout their lifecycle, but do not receive new functional updates. You can find fix packs or interim fixes (iFixes) for this release on Fix Central. Read IBM Robotic Process Automation Software Support Lifecycle Addendum for details about the Continuous Delivery Lifecycle Policy.

New releases also include cumulative fixes from previous iFixes. If you want to see a list of all the iFixes released so far, see Fix list for IBM Robotic Process Automation.

For previous release notes on the 21.0.x mainstream, see Previous releases.

21.0.7-FP016

Release date: 24 June 2024

  • [APAR DT389356] Fixed an issue where the server was unable to download newer versions of the Microsoft Edge drivers.
  • [APAR DT380968] Close Browser (webClose): Fixed an issue where the command would fail to close all the Chrome browser processes in Chrome v124.
  • Several security fixes. For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP015

Release date: 16 April 2024

  • Fixed an issue that would cause the email connection commands to not work under Red Hat OpenShift Container Platform.
  • Several security fixes. For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP014

Release date: 20 February 2024

21.0.7-FP013

Release date: 19 December 2023

Support for Red Hat OpenShift Container Platform 4.14

IBM RPA now supports Red Hat OpenShift Container Platform 4.14. To upgrade your Red Hat OpenShift Container Platform version, see Preparing to update to OpenShift Container Platform 4.14 🡥.

See the supported versions for each version of the operator in Supported OpenShift versions.

Fixes

  • [APAR DT196344] Fixed an issue where the IBM RPA Studio was unable to read scripts that were downloaded from the IBM RPA Control Center.
  • [APAR DT255296] Close Browser (webClose): The command now properly closes all open instances of the Google Chrome browser.
  • [APAR DT256701] Close Browser (webClose): Fixed an issue where the command would fail to close headless Google Chrome browser instances.
  • [APAR DT257075] Close Browser (webClose): Fixed an issue where the command would fail to close a Microsoft Edge browser instance.
  • Several security fixes. For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP012

Release date: 27 November 2023

New feature: New Redis operator

The new ibm-redis-cp-operator replaces the IBM Operator for Redis. This change does not affect current deployments, and the Redis operator is still installed automatically with the IBM RPA operator. However, you can now change the Redis password after you deploy IBM RPA.

For more information, see the following documentation:

Automatic antivirus update

The IBM RPA server can now automatically download antivirus definitions. To enable it, see the autoUpdateEnabled field in the Optional configurations documentation.

To manually enable automatic updates, see Enabling automatic antivirus updates.

Fixes

21.0.7-FP011

Release date: 31 October 2023

  • Improvements to Vault encryption methods.

For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP010

Release date: 3 October 2023

  • [APAR DT238692] Fixed an issue where the user was unable to uninstall IBM RPA.

For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP009

Release date: 5 September 2023

  • You can define the IBM MQ version that you want to use in the Custom Resource. See the queueManagerVersion, queueManagerLicense and queueManagerLicenseUsage options in Optional configurations. With that, you can now install IBM RPA in the same namespace of other IBM Cloud Paks that run different IBM MQ versions.
  • Fixed an issue where the certificate was not validated to see if the computer might run the script.

For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP008

Release date: 8 August 2023

  • [APAR DT224697] Fixed an issue where some keys did not work on the TN3270 terminal.

For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP007

Release date: 11 July 2023

  • Fixed an issue where v1.7 operator installations were causing failures when creating the QueueManager.
  • [APAR DT215184] Fixed an issue where the error ICurrentWindowBahavior not applied in the view would sometimes be displayed when trying to open IBM RPA Studio.
  • [APAR DT222744] Fixed an issue where the environment variable (${rpa:scriptVersion}) which has the version of the script, was not being returned when the script was called by the Execute Script (executeScript) command.

For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP006

Release date: 13 June 2023

For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP005

Release date: 16 May 2023

For security bulletin information, see Subscribing to security bulletins.

21.0.7-FP004

Release date: 18 April 2023

  • [APAR DT203300] Fixed an issue that would cause schedule runs to fail if the IBM RPA Agent was not restarted regularly.
  • The Extract Address (extractAddress) command now requires an API key to work. See Deprecated and removed functions for more details.

21.0.7-FP003

Release date: 24 March 2023

  • [APAR DT173615] Fixed an issue where the Execute Script (executeScript) command would cause an error if the script automated a Java application window.
  • [APAR DT178837] Fixed an issue where users imported from the LDAP server would receive the IBM RPA SaaS welcome email.
  • [APAR DT180516] Fixed an issue where the Java recorder was unable to map elements in a sequence.
  • [APAR DT196016] The proxy configuration is no longer lost after updating the IBM RPA Client.

21.0.7-FP002

Release date: 21 February 2023

  • [APAR DT188913] Fixed a regression issue that added unnecessary parameters to the Connect to IMAP Email Server (imapConnect) command.
  • [APAR DT189270] [APAR DT189306] Fixed an issue where it was not possible to set a fully-qualified domain name as hostname during the server installation.
  • [APAR DT192037] Fixed an issue that would cause an orchestration process to fail after losing connection with the MSMQ system queue provider.

21.0.7-FP001

Release date: 24 January 2023

  • [APAR DT168669] The Start Screen Recording (startRecording) command no longer crashes on Windows™ Server 2012 R2.
  • [APAR DT169390] The terminal emulator built into IBM RPA Studio now properly hides password characters.
  • [APAR DT172280] The IBM RPA recorder now properly recognizes Java selectors in a remote session.
  • [APAR DT172503] Fixed an issue where the email commands were unable to connect with the IMAP server if the computer had a proxy server configured.
  • [APAR DT173173] You no longer get an error after synchronizing user and groups from LDAP.
  • [APAR DT174653] Fixed an issue where the Connect to Chatbot or IVR (botConnect) command would occasionally time out in valid connections.
  • [APAR DT174689] Fixed an issue where the Open Excel File (excelOpen) command would fail to open a file if the spreadsheet contained cells with special characters.
  • [APAR DT178762] Changing the Antivirus port in the IBM RPA Control Center now updates it in the configuration file.
  • [APAR DT178769] Fixed an issue where API-related commands and browser web client requests were presenting slowness or timing out.
  • [APAR DT179592] The Wait Control (waitControl) command now tries to identify visible windows if there is more than one control with the same name.
  • [APAR DT179644] Fixed an issue where the Close Excel File (excelClose) command would be unable to save the file if it had macros or if it was protected by a password.
  • [APAR DT180390] [APAR DT180585] Processes started with an API call can now be restarted in the IBM RPA Control Center.
  • [APAR DT187748] Running bots from the IBM RPA Launcher no longer throws an internal server error.