10.1.6.2

Edit

Upgrade RPA installer to version 10.1.6.1603

prerequisites

The patch must be applied to the IA Cloud installation version 10.1.6.3.

RPA patch v10.1.6.3.1

The RPA patch version 10.1.6.3.1 resolves the following issues:

  • RDPs Units do not launch:
    • A Session Disconnect event is not always detected. The Master session is signed off by policy after an inactivity period.
    • An access violation error occurs in the logging function implemented through JNI. The Master agent process crashes as a result.
  • Enabling the DEBUG mode for a Worker causes an exception when a Business Process (BP) fails with "java.util.MissingFormatArgumentException: Format specifier '%s'" under the following conditions:
    • Turning on Worker debug logs
    • Running a BP that uses JvmUiAgent class methods, for example, .getText() on an applet element
  • Retrieving Windows session information fails with the following error: "WinApi error: The system cannot find the file specified."

Installation procedure

  1. Uninstall the old version of RPA on a Windows machine.
  2. Install a new RPA patch on the Windows machine.

Configuration updates

note

For UI-rich Swing-based applications containing up to 1 M+ cells in a table, apply specific configuration settings.

To set Object selectors to use the legacy logic, follow the instruction below:

  1. Go to bot-agent-unit.yml.

  2. Using the standard -D switch, insert the rpa.objectselector.legacy variable and set it to true.

    For instance, you can insert the variable after the line as shown below:

    -Djvm.connector.path=../rpa-grid/dependency/jvm-connector.jar
-Drpa.objectselector.legacy=true

For more details, refer to Switch to legacy logic of searching for UI elements.

Log4J vulnerability mitigation

important

The following instruction may frequently change in response to newly discovered issues. Thus, check it each time before applying the patch to get actual information.

For the log4shell mitigation process, refer to Security advisories to eliminate the JNDI lookup class from all log4j instances used throughout the Product.

← PreviousRestore previous version →