1641662: When Management Console contained a large number of robots, updating the Robots section took too much time and led to an increase in the memory consumption.

1635710: A Basic Engine Robot did not show loaded data when Replace Pattern was set on the Page Loading tab in the Robot Configuration dialog box.

1626903: If the device name in a Robot was different than the device mapping name in the Call Robot step, adding a Windows step caused an error: "Device information has changed."

1621518: A deadlock occurred while activating two RoboServers in Management Console from two different clusters.

1621061: WebKit incorrectly encoded URL parameters and sent requests with a query string that the server could not interpret.

1620569: For some Basic Engine Robots, it took several minutes to open the robots in Design Studio.

1619336: WebKit incorrectly encoded URLs when receiving 302 HTTP redirect and redirect requests with an incorrect URL.

1618585: The robots summary log view did not filter by the start and end time.

1618413: Time stamps sent by the Desktop Automation Service systray application to the Management Console were not formatted with InvariantCulture.

1617869: RoboServer could receive an authentication error during hub reservation when several robots were trying to reserve a hub from a RoboServer in parallel, which could cause a robot to wait in the Management Console queue indefinitely.

1616317: Management Console failed with NullPointerException when SlimRepository was requested by Design Studio and the Oracle database was used for Management Console.

1608829: Kapowbrowser became unresponsive when running the Execute Javascript step with large data.

1608289: In Kapplets, after restoring a Kapplets backup containing a robotBlock reference, some Kapplets were missing.

1604457: Resolution of overlapping text runs in PDF files could result in an incorrect or empty content in the application tree.

1603255: The systray application icon was not using the error icon when the command port of the Desktop Automation Service was busy.

1601510: A deadlock occurred in Design Studio, which was caused by the synchronization in Kiama. It happened if a Robot instance was accessed by two threads concurrently, such as from the execution thread and the AWT thread.

1601362: Some Press Key step limitations for the built-in Excel were not mentioned in the documentation.

1601082: When clicking the address bar in the Chromium browser, it did not replace text but instead added it at the end.

1599348: When checking the robot run in Log view, the columns were too small. When trying to extend these columns, the filter disappeared and other log lines were shown.

1597940: Design Studio became unresponsive when trying to calculate the history hash for ExcelSpreadsheetDocument that was not serializable. It could happen if Excel was used as input to external operations such as a database interaction.

1597733: The Extract Data converter did not match some characters with different cases even when the Ignore Case option was enabled. The issue was reported for Cyrillic characters.

1597732: When running text recognition on a Document Transformation Service project that used Clarity from RPA, the call failed with an error from Google Vision stating that the API key was missing.

1596030: When assigning a permission for a project in Management Console, it was impossible to enter the name in the group security drop-down list to search for a specific group.

1594833: If the Log view or schedule runs had more than 2100 rows, the request "Delete all runs (X) and their messages matching the current filter" did not work in Management Console.

1589440: After the device specification was added to Robots, it was no longer possible to reuse a Robot among Basic Engine Robots that used different mapping types.

1586876: The Find in Database step returned outdated cached values.

1586835: In LDAP mode, user groups were not sent to Kapplets.

1585535: Text input variables for Robots that contained only white spaces were trimmed while transferring them to a Robot. In that Robot, the variable was empty instead of containing the white spaces.

1584298: A duplicate group was created after restoring a backup file in Kapplets.

1581582: After executing a trigger for a robot deployed on a Management Console, subsequent robots were not executed properly. This situation occurred if the trigger device and trigger mapping for the robot with the trigger had different names.

1579983: Trigger mappings did not work when the mapping name was different on the Call Robot step compared to the name inside the Robot.

1579320: It was possible to have a step with a previous application reference after a converter step containing a device finder only, if the step before the converter step had an application finder.

1576444: Deleting more than four email accounts from Management Console caused an error.

1570772: The Outlook calender had a faulty tree and could not be automated with mouse operations.

1570478: When the Number type was used and a table with "Float" in SQL Server was created, the sorting was not correct in the Data view in Management Console when sorting was performed by that column.

1564826: Using the Extract Tree as XML step resulted in an invalid XML for some pages. For more information, see XML validation with Extract Tree as XML step.

1562022: The admin user rights were not updated from LDAP.

1551249: In Robot File System, writing to an SFTP share caused the NullPointerException on Tomcat 8.5.34 and Tomcat 9.0.34.

1544472: When the Docker configurator generated a properties file with entrylogin.ldap.check.timeout.<n> set to an empty string, it became unresponsive when reading the properties file back.

1544347: The Desktop Automation Service could not extract data from the second column of the SAP_AdvancedTreeList.

1540505: When using product version 10.7.0, it was impossible to upload a folder through the Chromium browser.

1538815: The Lookup Password step had no timeout, which caused robots to become unresponsive.

1538549: The vc_redist files were missing from the Windows RoboServer Docker Image.

1537691: Credentials specified in the Desktop Automation Service configurator were not encoded in UTF-8 before being Base64 encoded and sent to the Management Console.

1536884: Settings on the following tabs in Management Console > Settings > General were reset to their initial value after being changed, saved, and then refreshed: Login, RoboServer purge, and Base URL. This was also relevant for the From address field on the SMTP tab.

1532528: Design Studio version 10.7.0 could not connect to Management Console version 11.2.0 if connectors or Robots were uploaded.

1532524, 1530720: A malicious robot developer with elevated project rights theoretically had an ability to retrieve the password that had been previously set as input to a robot job in a schedule. The attacker needed to have malicious intent and sufficient knowledge about the internals of the scheduler.

1530042, 1528241: Password store entries were not restored when the Import project option was used.

1528659: When the Desktop Automation Service was configured over port 443, it was impossible to create an SSL/TLS secure channel.

1524075: After Synchronizer.exe was started, logging appeared only in the Synchronizer.exe console. The logs should have been written to the synchronizer.log file instead.

1518036: Parameter validation on signature-based steps rejected optional string parameters with an expression that evaluated to an empty string.

1517909: A "No node with name" exception occurred when using the Set Content step.

1516885: The new Management Console did not work on WebSphere.

1498832: The dialog box that enables you to automatically upload any missing dependencies during schedule creation in Management Console was not available.

1498773: An empty tree was returned when a page was opened using javascript: protocol.

1466282: If a robot had a hash sign in the name and/or path and required an input, it failed when it was run in a schedule.

1457810: When upgrading from product version 10.7.0.x, it was impossible run robots after a backup was restored.

1452320: When you tried to create an Insight Viewer bookmark in Kofax Analytics for RPA 2.2.0, an error occurred, and the bookmark was not saved.

1407189: Making a Group step that contained a Load Page step in a Minimal Execution robot led to errors after you entered a name for the group and clicked Enter.

1403260: This issue is resolved with Kofax TotalAgility 7.8.0 and later. For earlier versions, the issue still occurs. Using the following variable types in the Raise Job Event action in the KTA step led to errors: date, byte, document, float, double, nullable date, nullable string, and currency.

1318955: InsertSheetStepAction used on global variables did not commit on errors.

1308361: DOMParse worked differently on Linux, which required libxml2 to be updated.

1264566: When Management Console was added to Design Studio by using credentials for a user who did not have respective privileges, the Design Studio became unresponsive after the shared project was refreshed for the second time.

1255576: Kapowbrowser became unresponsive during snapshot creation when CSSRule had no parent StyleSheet.

1250640: The second iteration of a looped Test Value step executed after a Try step caused Design Studio to become unresponsive.

1248278: In Basic Engine Robots, the NullPointerException occurred when prematurely exiting a branch after a Try step.

1075498: In Basic Engine Robots, the Click step worked incorrectly on a <div> selection when the Restore Session step action was used in previous steps.

879944: WebKit became unresponsive on the String.split() call containing non-ASCII characters.

747918: In the Desktop Automation Editor, applications opened with "Run as Administrator" could be seen but they did not have an application title.