Kofax RPA 11.4.0 Fix Pack 3

Build Date: August 1, 2023

© 2023 Kofax. All rights reserved.
Use is subject to license terms.

Introduction

Install Kofax RPA 11.4.0.3 to resolve the issues listed below.

Issues resolved in this fix pack

1971147: In Management Console, the request to run a robot list for a cluster no longer causes performance issues.

1971141: In Desktop Automation Service, configuration of the OPENSSL_MODULES environment variable no longer causes any issues.

1970459: In Kapplets, when creating a schedule and specifying a period for the "Hourly" interval, enter any integer value between 1 and 23.

1970423: In the Kofax RPA Administrator's Guide, the command to set Synchronizer as a service is no longer valid as it does not need parameters.

See How to install Synchronizer as a Windows service at the Kofax Knowledge Portal.

1967420: Kofax RPA silent uninstall is now available.

1967039: Information about adding a UI recognition language for Tesseract needs clarification in the Kofax RPA User's Guide and Help. This also relates to step 1 in the "Change Default OCR Language for Robot" topic. When downloading the .traineddata file for Tesseract, follow these instructions:

1. Download the .traineddata file for the required language from GitHub. For example, the file for the Japanese language is jpn.traineddata.

   If the files are not avaialable in the link above, search for version 3.04 from the main repository page.

   Tesseract version 3.05.00 is compatible with Kofax RPA 11.4. However, RPA uses Tesseract 3.04.00 training files.

   NOTE: Make sure the downloaded .traineddata file is compatible with your version of the teserract.dll file. For compatibility information, see the README file published at the bottom of the traineddata page. Using the wrong training data does not result in error messages, but may cause poor OCR results.

2. Copy downloaded trained data file to the appropriate folder:

   • On the Windows-based automated computer with installed Desktop Automation Service:

     DesktopAutomationService\lib\tessdata in the Desktop Automation Service installation directory. Example:

     C:\Program Files\Kofax RPA DesktopAutomation 11.4.0.0\DesktopAutomationService\lib\tessdata

   • On the local Windows-based computer to use with built-in browser:

     nativelib\hub\windows-x64\<build number>\lib\tessdata* in the Kofax RPA installation directory. Example:

     C:\Program Files\Kofax RPA 11.4.0.0\nativelib\hub\windows-x64\622\lib\tessdata

   • On the local Linux-based computer to use with built-in browser:

     nativelib/hub/linux-x64/<build number>/lib/tessdata in the Kofax RPA installation directory. Example:

     Kofax_RPA_11.4.0.0/nativelib/hub/linux-x64/533/lib/tessdata

   * The build number is different in different versions of the program.

3. Change the UI recognition language as described in the "Change or add UI recognition language" section above.

1965860: It is now possible to split a single KCU unit equally between multiple RoboServers.

1965328: A non-root user for Robot File System is now able to write data to the /data directory.

1964488: Information in Kofax RPA 11.4.0 Release Notes needs clarification. In the Changes in behavior section, instead of "Use same Scheduler database in fix packs" please read "Use the same Management Console platform database."

1958461: Synchronizer now runs successfully when updating and uploading types to Management Console.

1958412: On Linux, Kapowlock now connects successfully.

1958293: In Management Console, users are now prevented from adding databases with the same name to the same cluster.

1957737: Design Studio no longer fails if the connection to the Management Console becomes unstable.

1956063: When Management Console and proxy use HTTP and HTTPS accordingly, Management Console now generates the correct URL for testing the service when selecting the REST option for the required Robot.

1954178: Robots now start successfully, even if RoboServer was previously above the memory threshold.

1946223: In Desktop Automation Service, it is now possible to configure Screen Lock on startup.

1945812: Process Discovery Analyzer now works properly when analyzing Excel screens.

1922083: Snakeyaml has been upgraded in Kapplets to enhance security.

1863200: The base Linux image for Docker installation is updated to Ubuntu 22.04 LTS.

Issues resolved in previous fix packs

Issues resolved in Fix Pack 2

1943553: Reduced the size of Docker images.

1943490: Japanese characters could not be entered in Kapplet name and description.

1943488: OAuth access token was not refreshed when using email triggers.

1942678: Added the description of SAMLKEYSTORE_PUBLIC_KEY_FILE to the Docker readme file.

1942070: Updated the Docker readme file to include new variables.

1940951: Upgraded commons-fileupload to enhance security.

1939479: Management Console in high availability could crash due to non-serializable objects submitted to the Hazelcast scheduler.

1937972: The Add server option was removed from Cluster options in Management Console.

1935311: Process Discovery Analyzer could crash due to recursive JSON in recorded data.

1934905: XML Data Mapper generated attributes without record field types.

1934060: Process Discovery Analyzer failed to start in Docker when using the supplied Dockerfile.

1932598: RoboServer uptime displayed without formatting.

1932004: Cluster Settings Database View did not scroll correctly.

1931653: Kapowlock failed in environments where localhost and 127.0.0.1 are not interchangeable.
If the environment variable KOFAX_RPA_LOCKSCREEN_HOST is set, the 127.0.0.1 parameter passed by Lock Screen will be replaced by the value of the variable (presumably 'localhost').

1928101: The Complete SignDoc Request application action was missing.

1925731: SAML login failures were not logged in the audit log.

1925729: SAML logout no longer leads to automatic re-login.

1925724: SAML login failure no longer redirects to LDAP login.

1925722: SAML user name validation did not allow special characters.

1890539: PressKey in Chromium did not work after pressing the navigate button.

Features resolved in Fix Pack 2

1943554: Allow initial admin user and password to be configured using the Management Console configurator.

When deploying RPA in Docker, you can configure initial admin user name and password in the docker-compose file using environment variables.

LOGIN_INITIAL_ADMIN_USER: Sets the initial admin user name. Default is admin.

LOGIN_INITIAL_ADMIN_PASSWORD: Sets the initial admin password. Default is admin.

The admin user is created if the database is empty or no admin user exists, and the system is configured either to use local authentication or (for ldap, and so on) the createAdmin is set to true.

If the database already contains an admin user, the user is not created.

After RPA is deployed, you can view the applied values in the initialAdminUser and initialAdminPassword properties of the login.xml file.

1940892: Allow SAML settings to be configured using the Management Console configurator.

1940891: Allow SAML certificates to be configured using the Management Console configurator.

When deploying RPA in Docker, configure the following settings in the docker-compose file using environment variables.

SAML_IDP_NAME: Sets the identity provider name. The possible values are: OKTA, ONELOGIN, and AZURE.

SAML_ADMINGROUP_COUNT: Determines the number of admin groups.

SAML_ADMINGROUP_VALUE_<N>: A list of identity provider groups mapped to the admin superuser in Management Console. For each admin group, replace <N> with a number between one and the count of groups.

SAML_ADMINISTRATORGROUP_COUNT: Determines the number of RPA Administrators group.

SAML_ADMINISTRATORGROUP_VALUE_<N>: A list of identity provider groups mapped to the RPA Administrators group in Management Console. For each RPA Administrators group, replace <N> with a number between one and the count of groups.

TOMCAT_SERVER_CONNECTOR_SCHEME: Sets the scheme name for the HTTP connector in Tomcat.

TOMCAT_SERVER_SSL_CONNECTOR_SCHEME: Sets the scheme name for the HTTPS connector in Tomcat.

After RPA is deployed, you can view the applied changes in the saml.xml and server.xml files accordingly.




When deploying RPA in Docker, manage the SAML signing certificate with the following environment variable.

SAMLKEYSTORE_PUBLIC_KEY_FILE: If set, points to a file containing the certificate in DER or CER format. Then, the certificate is imported into the dedicated SAML keystore to establish trust with any identity provider.

1923388: Database steps now have a timeout setting.

The Basic Engine Robots and Robots Execute SQL and Query Database steps now have a Timeout property.

Specify the timeout for submitting SQL statements in seconds. The value must be greater than zero.

In Basic Engine Robots, use a variable or a value option to define the preferred timeout. The timeout is enforced through DBMS and if it is reached, the Execute SQL or Query Database actions stop executing with an error message specific to the database.

In Robots, if the timeout is reached, the DeviceIssue exception is thrown with an error message specific to the database.

Note that various DBMS types and JDBC drivers may handle timeouts differently. For example, not every system allows a timeout to trip in the middle of certain statements.

Issues resolved in Fix Pack 1

1926113: Could not run Kapplets in a different Tomcat context.

To install Kapplets with a different name other than the default ("kapplets"), customize the file names of the kapplets.xml and kapplets.war to match, for example kapplets11.xml and kapplets11.war.

1926105: Upgraded Jackson to enhance security.

1923859: Upgraded Spring Security to enhance security.

1923854: Upgraded Tomcat to enhance security.

1923851: Upgraded Hazelcast to enhance security.

1922974: Fixed race condition when releasing Desktop Automation Service.

1922972: In Docker, Roboserver could not run with a non-root user.

1922089: Upgraded ivy to enhance security.

1908910: Robot execution sometimes resulted in the "last of empty list" runtime exception.

1900210: Updated SnakeYAML to enhance security.

1900025: Upgraded LibTIFF to enhance security.

1897258: Patched Leptonica to enhance security.

1894332: Upgraded jsoup to enhance security.

1894329: Upgraded Jackson to enhance security.

1894326: Upgraded JNA to enhance security.

1894325: Upgraded SSHD to enhance security.

1894248: Removed the msvcp100 and msvcr100 libraries as they are no longer used.

1867058: Upgraded protobuf to enhance security.

Note that documentation specifies Python version 2.7 which is not supported anymore. Python 3 versions 3.5 or higher are supported.

1867051: Upgraded woodstox to enhance security.

1825857: It was not possible to edit consumer key and consumer secret in OAuth application.

Applies to

This fix pack is a full installation. It is accumulative and includes the resolved issues released in previous Kofax RPA 11.4.0 fixes and fix packs.

Apply this fix pack to replace any of the following versions:

• Kofax RPA 11.4.0
• Kofax RPA 11.4.0.1
• Kofax RPA 11.4.0.2

Files included

This fix pack includes the following files:

File name	Version
KofaxAnalyticsforRPA-2.7.0.zip	2.7.0
KofaxRPA-11.4.0.3.msi	11.4.0.3
KofaxRPA-11.4.0.3.tar.gz	11.4.0.3
KofaxRPA-11.4.0.3_Trial.zip	11.4.0.3
KofaxRPADesignStudio-11.4.0.3.msi	11.4.0.3
KofaxRPADesktopAutomationService-11.4.0.3.msi	11.4.0.3
KofaxRPADocumentation-11.4.0.3_EN.zip	11.4.0.3
KofaxRPADocumentation-11.4.0.3_FR.zip	11.4.0.3
KofaxRPADocumentation-11.4.0.3_JA.zip	11.4.0.3
KofaxRPADocumentTransformationService-11.4.0.3.msi	11.4.0.3
KofaxRPAProcessDiscoveryAgent-11.4.0.3.msi	11.4.0.3
KofaxRPAProcessDiscoveryAnalyzer-11.4.0.3.zip	11.4.0.3
KofaxRPARoboServer-11.4.0.3.msi	11.4.0.3
ReadMe-KofaxRPA-11.4.0.3.htm	N/A

Install this fix pack

You can install this fix pack on top of the existing Kofax RPA 11.4.0, 11.4.0.1 or 11.4.0.2 Management Console database schema. To do so, use the following procedure.

1. Back up your existing installation by creating a Management Console backup.
2. Install the required components. For details, see the Kofax RPA 11.4.0 Installation Guide.
3. Use the existing database schema when installing the Management Console in Tomcat.

Remove this fix pack

This fix pack is a full installation. Follow the standard uninstallation procedure for Windows or Linux applications.