Resolved issues

1796217: For one customer, the "application" step under load in Batch & Output Management could fail to process some requests.

1794013: DesignerListTemplates did not return the description of the listed Document Templates because the description was not properly saved after editing. This issue was fixed, but if DesignerListTemplates still does not return the description, you need to resave the Document Template.

1787988: If the name of the folder at the top level coincided with the project name, this folder was not displayed in the nested selection control.

1787966: The Form Editor in KCM Designer could not open the Forms that had been saved with older KCM versions.

1787960: If there were many items under a folder in the Designer menu tree, the nested selection control took a significant amount of time to open the folder.

1785293: Batch & Output Management did not function if TLS 1.0/1.1 was disabled in favor of a higher TLS version.

1782959: In rare cases, DocToPDF with the Rendition processor created images that were only partially visible or not visible at all.

1776623: When the Contract Manager was heavily loaded, in some cases it could return data from a different session.

1775602: It will not be possible to import KCM exports made by KCM 5.6 into KCM 5.5 or earlier versions. For KCM 5.5 and earlier versions, it was potentially possible to import exports made with newer versions of KCM into previous versions. It could lead to undefined behavior and loss of information.

1667921: In rare cases with a customer, concurrent bundling process led to undefined results if they specified an overlapping record selection.

1663472: The scrollbar was not displayed in the Letterbook Editor if a Letterbook contained many elements.

1661528: KCM could not process Unicode characters in the Data Backbone if they were outside the Basic Multilingual Plane. For example, Emoji characters could not be processed.

1659536: PDF documents generated by DocToPDF with the Rendition processor, could lack characters if they used a font that existed in the system but lacked a definition for those characters. The issue was fixed so that those characters are rendered with the specified substitution font instead. If the substitution font also lacks a definition, an error is thrown.

1647877: In rare cases, Rich Text Blocks saved in Microsoft Word 2013 or earlier versions, could lead to an error when used in composition. The issue was limited only to the .doc format and did not affect the .docx format.

1641737: Selection items located in the left margin of the ComposerUI were barely clickable for Content Wizards with a nested structure of options.

1560432: CheckDatabase did not detect privileges on roles for Oracle 11g or 12c during the installation.

1548761: The bookmark structure created by ConcatPDF by the PdfLib processor was different from the bookmark structure created by the Amyuni processor.

1353866: Batch & Output Management did not retry the queries failed due to harmless database exceptions. As a result, the process was terminated and required a manual recovery.

887392: KCM Designer allowed Quick Documents and Static Documents to be specified as Data Preparation Templates. However, they could not affect the Data Backbone; therefore, they were invalid as Data Preparation Templates.

727659: The names of the KCM Windows Services were changed. The names now start with KCM5.6 so that they are listed together in the Windows Services control panel.

727505: When the Amyuni processor was used in the DocTopPDF core scripting command, the specified watermark was placed in the wrong position and at the wrong angle. Often, the watermark was placed outside the page boundaries and was invisible.