Resolved issues

1763166: Some database update requirements were not documented.

1762166: The granularity of the aging increase was too big for queued tasks.

1751114: The word "second" in the documentation on schedules was translated as 秒, meaning "a second," while it needed to be translated as 2番目, meaning "the 2^nd."

1750595: When the Kapplets interface language was changed to Japanese, the error messages on the "Kapplet Schedule" creation page still appeared in English.

1735719: If you uploaded a Robot from Management Console that already existed in the target location, an error appeared even if the Override option was selected.

1735667: When a Kapplet health check request was invoked, it made Kapplets log in to Management Console, which created network congestion and LDAP overload.

1734829: After copying a schedule in Management Console, the value of the Password variable was changed to asterisks instead of the actual password characters.

1734550: Email triggers did not work correctly if two identical emails were present.

1733160: The Management Console "Data view" page showed some columns from another table.

1731983: Design Studio did not correctly read connectors containing Japanese characters.

1730798: The robot summary, which included comment, tags, types and robots used, could not handle invalid XML characters, and the robot XML file became invalid.

1717368: When building an Excel tree, the Windows Automation API could return a NULL result value while reporting a successful operation, which caused the application to become inoperable.

1711040: Deleting a column in an Excel variable that contained formulas resulted in a corrupted Excel file.

1706587: Sorting items by a user name in the "Password store" table produced the "Unable to process request" error.

1706009: The Press Key step did not work after clicking the navigation button on the toolbar in the built-in browser.

1705503: Emails were not moved from the Processing folder after the robot executed by the email trigger had finished.

1695048: The Custom Action step Connector could fail while accessing local disks if the path contained non-ASCII characters and long names.

1690660: In Management Console, the filter did not update the list of robots on the Robots page after logging out as a limited access user and logging in as the admin user.

1686107: Kapplets with an empty input date variable became unresponsive when they were executed.

1685422: The Press Key step in Robots older than 10.7.0 could have a press key count of zero (0), which produced errors when executing on a newer version of RoboServer.

1685400: Non-admin users were unable to delete an OAuth user even if they had the privilege to delete the user.

1684818: When a certificate storage contained several "trustedcert" entries with unique aliases, Design Studio could not pick the correct client certificate storage.

1683399: The VCS Repository Client did not release the connection when required and the Repository Client produced some errors.

1683379: SOAP views were erroneously removed from Management Console.

1682714: Entering a number followed by the letter D in an Excel cell caused the D to disappear. To avoid the issue, a single quotation mark has to be added in front of the number, as documented in the Kofax RPA Help.

1682221: It was not possible to use previous references to device finders when the previous finders were of the application or component type.

1679583: Design Studio became unresponsive when setting up a client certificate without a private key.

1679488: Importing a project led to an error if a backup contained more than one password store with one password access.

1674560: The Tree Stops Changing guard did not work for some websites in the built-in browser.

1672809: When the index of a message that the Robot finder was supposed to use was changed on the server, a component action, such as "Get message content" or "Delete message," could be executed on a wrong message.

1672785: Failed Management Console login attempts were not recorded in the audit log.

1671331: Design Studio became unresponsive when an unreachable finder was edited in a Basic Engine Robot.

1669401: Design Studio became unresponsive when the Select Next Matching Node button was clicked. The issue occurred when the user clicked the button after adding a tree mode configuration.

1661255: Fonts in the Thai language were displayed incorrectly after switching to OpenJDK.

1658182: When loading a large non-HTML file, pageChangeFilter issued a DBus error on Windows computers.

1654150: No option was available to create a pre-defined role that allowed configuring Kapplets with a user that had privileges required to run Kapplets.

1653556: When starting Outlook and Microsoft Word 2013 on a Windows 7 computer with Kapowlock enabled, the Desktop Automation Service could not obtain screen shots.

1648587: Loading the cef.cfg file failed if Kofax RPA was installed into a directory where the path contained double-byte characters.

1647260: A schedule that used a pattern to execute robots sequentially ran them simultaneously, even when the "Run jobs sequentially" option was selected.

1646137: The log could show "ERROR [RobotExecutor] Selector null - nodeNameStats: node deleted by compute(); Name = javaw.exe ; Value = null," which in fact was not an error.

1639788: The Kapplets service could not restore Kapplets with a RobotBlock reference in a backup file. As a result, some Kapplets were missing.

1635512: Design Studio was unable to send a response back for an unsupported key at the Press Key step, causing the step to time out.

1634857: On the "Robot summary" tab in Management Console, it was impossible to apply filters based on the start and end time.

1629289: If Kapowlock was activated and a Restart Device step was executed, it was impossible to reconnect to the Desktop Automation Service as it stopped responding to the command port.

1628690: The Extract Email step did not support multipart/related and multipart/mixed MIME types.

1619127: In Management Console, when the user opened the "Trigger mappings" page and filtered the Robots, the filter was also applied to the list on the Robots tab.

1608628: When the HTTP connection to Management Console failed, during the Robot execution, the log entry could state "Could not establish repository access for device reservations."

1577748: The users could not use Email subfolders as a trigger unless they provided a specific path.

1558181: In Design Studio, an issue occurred with the Click step, which caused a StringIndexOutOfBoundsException error.

1550956: The Page Down key did not scroll a page with a table element in a scrollable area.

1547456: Design Studio became unresponsive when loading a favicon.

1540561: An issue occurred when running Robots with Kapplets when the Robots were run directly over RQL.

1528530: It was not possible to interact with application elements that disappeared once you removed the pointer.

1501561: Design Studio became unresponsive when the user tried dragging a Try Step.

1460612: In a Basic Engine Robot, when a key contained a period, the generated finder did not work.

1403419: If the user edited a name and a description for a Kapplet and then selected a template, the name of the template was overwritten.

1182993: Design Studio became unresponsive when the user was opening the Robot editor. This issue occurred if the user did not have the required execution privileges.

1122983: If LogDB was stopped, schedules became inactive, while Management Console and RoboServer kept running.

922702: When the user running a schedule in Management Console did not have privileges to write to the log database, the error message that appeared was ambiguous.