Known issues

1642467: It is impossible to use SAP because nodes for some elements are not available in the tree in the Recorder View.

Workaround: To make all nodes available in the tree, from the product installation files, download and save the RegSAPSurrogate.reg file on the computer running the Desktop Automation Service. Run it accepting any warnings and then restart the Desktop Automation Service agent. The file resides in the {path}\DesktopAutomationService\bin folder.

1641912: Kofax TotalAgility cannot reach Kofax RPA when a server configuration is set to Cluster. Applicable to Kofax TotalAgility versions 7.8.0 and 7.9.0.

Workaround: Configure KTA to use RoboServer instead of Cluster. Or, configure KTA to use the REST communication type instead of .NET.

1625531: Some exceptions and error messages related to kapowhub are not localized in this product version.

1618537: Starting with version 11.2.0, Management Console and RoboServer write logs to a database in UTC time format, which is different from previous versions when the time was logged in a time zone of the respective Management Console and RoboServer.

Workaround: Start legacy RoboServers with the java -Duser.timezone=GMT option.

1616761: The internal time zone format in Kofax Analytics for RPA has changed to UTC, which means that data from Kofax RPA versions prior to 11.2.0 is shown incorrectly in Kofax Analytics for RPA 2.5.0 and later.

1607788: Adding new users to the default RPA Administrators group in Management Console causes an "rpa administrators" group to be created in Kapplets.

1603045: The Desktop Automation Service may stop functioning on Windows 7 when a .NET application is started while it is running.

1602656: Some menus in Design Studio are placed incorrectly when running on Linux with Gnome and may become inaccessible.

1594223: The Call REST Web Service step cannot load a page with Digest authentication when using a proxy server.

1593366: Some email addresses of a reviewer or a signer that are invalid in Kofax SignDoc can be entered and validated in Kofax RPA.

Workaround: Consult the SignDoc documentation to ensure that the email addresses you are using are valid before entering them in RPA.

1584988: If the StackOverFlowError is reported, you need to manually increase the memory limit in the DesignStudio.conf file. To do so, add the wrapper.java.additional.1 setting to the file and specify the memory limit.

Example: wrapper.java.additional.1=-Xss4096K

1584454: If you use the Database provisioning default settings when filling out the Process Discovery Analyzer parameters in a Management Console, the Management Console cannot create the Analyzer database, and provisioning fails.

Workaround: Explicitly specify the username and password under Process Discovery Analyzer > Database provisioning in Management Console before creating a database.

1559704: If you deploy the offline documentation in Japanese on the Tomcat server using the Microsoft Edge browser, the help files may contain unreadable characters.

Workaround: Use Google Chrome or Mozilla Firefox browsers with the Japanese offline documentation.

1546570: Process Discovery Agent cannot collect events of the applications running with administrator rights.

Workaround: Run Process Discovery Agent with administrator rights to collect events from all applications.

1536508: When the user is trying to import a backup in Management Console, and the import fails, the existing schedules switch to their default values and can no longer be started.

Workaround: To start the schedules, they need to be recreated. Before importing a backup, we recommend that you create a backup of the current Management Console state.

1524460: When uninstalling the Document Transformation Service version 11.0.0 to prepare for a new installation, the license utility is not entirely removed.

Workaround:

1. Uninstall the old Document Transformation Service version.

2. Install a new Document Transformation Service version and then uninstall it.

3. Install the new version again.

1523086: Kofax RPA Kapplets that use MySQL database use the collation from the database properties variable "collation_database" instead of using the schema collation. It may cause Unicode characters to be shown incorrectly if the "collation_database" is not set to a Unicode collation.

Workaround: Make sure that you use the schema collation for the utf8mb4 character set in the database system variables "collation_connection," "collation_database," and "collation_server."

1517340: When a backup file containing a Kapplet user with the specific double-byte character set name is imported to a Management Console, the Kapplet user does not belong to the Management Console group that the user was initially assigned to.

1517076: The Process Discovery database user password is not encrypted when stored in the Management Console.

1512677: When running multiple robots simultaneously, the org_freedesktop_general file used by the D-Bus protocol to authenticate the server and client may get locked by one robot for a short period of time, preventing another robot from accessing this file to read cookies from it.

1502164: During schedule creation, the "Jobs timeout" and "Execution time limit" property values are converted from seconds to minutes. This situation occurs only when the value in seconds can be converted to whole minutes.

For information on these properties, see "Schedules" in Kofax RPA Help.

1498551: A Basic Engine Robot may fail to open website pages that contain Japanese characters. This issue was reported while using the built-in browser on a Windows system set to a Japanese regional format.

Workaround: For the loaded page, in the Robot Configuration > Page Loading > Page Change settings, specify a text replacement for the URL of the loaded page:

<body class="no-navi">

to

<body class="no-navi" style="text-align: start;">

1478872: A Robot with steps that use the Robot File System does not work if a copy of this Robot is uploaded to another project in Management Console.

1445050: Using the following symbols in workspace names in Kapplets leads to errors:

/ \ % ? . {

Workaround: Do not use these symbols in workspace names in Kapplets.

1398421: Management Console backup files created in versions 10.3.0.0 - 10.3.0.9 do not include trigger mapping data. Use the following workaround to create a backup that will contain all correct data. This workaround was introduced in version 10.3.0.10.

Workaround

For the enterprise Management Console

This procedure restores trigger mappings and applies to the Management Console deployed on Tomcat that contains attended robots with trigger mappings.

1. Stop Tomcat and back up your database before continuing.

2. Before installing the 11.3.0 .war file, open it and modify the version.properties file, which resides in WEB-INF\classes, to match the version you are upgrading from.

   For example, if you are upgrading from 10.3.0.5, the text in the file must be: fullVersion=10.3.0.5 266

3. Install the updated 11.3.0 ManagementConsole.war file on Tomcat. It will start a 11.3.0 Management Console with the old database.

4. Create a backup to contain all data including the trigger mappings.

5. Install a new 11.3.0 Management Console with an empty database (without changes to the .war file).

6. Restore the backup created in Step 4.

For the development Management Console

This procedure restores trigger mappings and applies to the embedded Management Console that contains attended robots with trigger mappings.

1. Stop the original Management Console and back up the folder:

   C:\<username>\AppData\Local\Kapow\10.3.0.x_<build number>

   to

   C:\<username>\AppData\Local\Kapow\10.3.0.x_<build number>_original

2. Install Kofax RPA 11.3.0 and do not start the Management Console.

3. Open the ManagementConsole.war file, which resides in <program folder>\RPA 11.3.0 <build number>\WebApps, and modify the version.properties file, which resides in WEB-INF\classes, to match the version you are upgrading from.

   For example, if you are upgrading from 10.3.0.5, the text in the version.properties file must be: fullVersion=10.3.0.5 266

4. Delete all files from:

   C:\<username>\AppData\Local\Kapow\10.3.0.x_<build number>\Temp

5. Add the updated ManagementConsole.war file to the original version to:

   <program folder>\Kapow 10.3.0.x <build number>\WebApps\

6. Start the Management Console original version. It will start a 11.3.0 Management Console with the old database.

7. Create a backup to contain all data including the trigger mappings.

8. Install a new 11.3.0 Management Console with an empty database (without changes to the .war file).

9. Restore the backup created in Step 7.

1384485: A Robot cannot select icons on the desktop after the Win+D key combination is pressed. The Win+D key combination is a shortcut to hide and show the desktop. Before the keys are pressed, the icons on the desktop are listed under the Program Manager pane. After Win+D is pressed, the icons are hidden, which prevents the Robot from identifying the icon elements to display in the automation tree.

Workaround: If the goal of using Win+D is to minimize all windows and show the desktop, use Win+M instead. This key combination does not hide icons, so they remain available in the automation tree.

1371327: If a database mapping is created in Management Console > Repository > Databases, a robot cannot be started with the remote API.

Workaround: Create a database mapping in the My Projects view (Shared Databases section) in Design Studio and use it with robots you want to start with the remote API.

1362162: In Password Vault in CyberArk, it is not possible to create a safe or account name in Unicode.

1359670: When a Robot with the KTA step is opened for editing, the KTA step is marked with an icon to warn that the configuration is unavailable. After an attempt to change any configuration parameter for the process, the step configuration collapses to the KTA Server level. After expanding the step, the previous configuration is discarded and the user needs to reconfigure the step.

1356285: The following parameter types have mismatching boundaries in RPA and TotalAgility: Currency, Decimal, Double, Float, Long, Short.

1354870: The virtual keyboard driver required by the Desktop Automation Service is built with User-Mode Driver Framework 2.0 and is only supported on Windows 10, Windows Server 2016, and Windows Server 2019.

1343762: Some built-in 32-bit Windows applications cannot be run by using their process name.

Workaround: Use the full path to the application to run it. For example, use c:/windows/sysnative/dfrgui.exe instead of dfrgui.exe.

1337449: A Kapplet with a large PDF file used as a binary input value generates an "Out of memory" error message.

Workaround: Change the "Maximum memory pool" value on the Tomcat server or the max_allowed_packet value in the MySQL my.ini file.

1314402: The kapowlock process used by the Lock Screen and RDP Login steps may freeze if the target computer is a virtual machine and it has an active session.

Workaround: Verify that no active sessions exist on the target computer or disable the "Use WDDM graphics display driver for Remote Desktop Connections" group policy setting.

1312329: When the Robot File System file share is mapped to a Windows drive (as configured in the Desktop Automation Service), the Windows WebDAV client used for the mapping caches information from the file share. On rare occasions, it may cause the mapped Windows drive to have an outdated view of the file share.

Workaround: Turn off the caching in the Windows Registry on the computer where the Desktop Automation Service is running.

1. In the registry, locate the following key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MRxDAV\Parameters

2. Change the value of the following parameters to 0.

   • FileNotFoundCacheLifeTimeInSec

   • FileInformationCacheLifeTimeInSec

3. Restart the computer.

1306204: Authentication with SAML is not supported for Kofax RPA Kapplets.

1289988: Users belonging to the RPA Administrators group cannot assign the Project Administrator, Developer, or Process Discovery Client roles to user groups in a project.

1281128: Characters in the localized version of Kofax Analytics for RPA may not display correctly if you use MySQL 5.7 or earlier with Insight for data and meta databases.

Workaround: Either upgrade your MySQL server to version 8.0 or later, or make sure the default character set for the server and all its components in MySQL 5.7 is set to UTF-8.

1263908: If you have a large number of types (180 or more) in a single project in Design Studio, it may cause the StackOverflowError and prevent you from opening and editing your Robot.

Workaround: Do not store too many types in one project.

1218466: The Windows 10 Start menu hides duplicate URL links, so if you have several Management Console installations, only the link to the first installed version is present on the Start menu.

1168320: When restoring a backup containing a file with a backslash in the name, an error about a corrupted file is shown. As the backslash character is not allowed for file names in a file system, the backup fails to be restored. The file with a backslash can be uploaded to the Kofax RPA project using the Repository API that does not prevent such files from uploading.

Workaround: When naming your work objects, such as robots, types, or snippets, do not use a backslash or other characters that may be reserved or have a special meaning in a file system. If you already have a backup containing file names with a backslash, unarchive the backup and then archive it again to work around the issue. For more information, see "Naming policy" in Kofax RPA Help.

739186: The maximum length of tab titles in the Robot editor is 32 characters, including spaces and dashes. Titles that exceed the maximum length are truncated automatically.

Workaround: Do not use title names longer than 32 characters.

695039: Expression editors become unresponsive if zeroes are added after the following characters: dollar sign ($) and the number one (1).

The lock screen and RDP connection features are only supported if the Desktop Automation Service runs on the Pro or Enterprise editions of Windows 7 or Windows 10. The Home edition of Windows does not have the remote desktop host and cannot be connected using RDP.

Running the Document Transformation Service on Windows Server 2016 requires the following change to the Windows security settings:

1. In the IIS AppPool\Kofax RPA Document Transformation Client script, add an entry for the Thin Client IIS application pool user.

2. Open security settings for C:\Document Transformation\Batch.

3. Allow all missing permissions for the user, save the changes, and apply the settings.

If VMware is used for hosting remote devices, text and icon scaling can displace selections in some applications, leading to unexpected behavior in Robots.

Workaround: Change display scaling to 100% on automation devices.