LIQUENT InSight Rendering 4.4 Release Notes

Resolved Issues: Liquent InSight Rendering 4.4

The following issues that were reported to Technical Support have been resolved. Issues are listed in descending order by their tracking numbers. Customer incident numbers that were recorded when the issues were reported are included in brackets [#####] following the tracking number.


Issue	Build	Description
4898		The CDCXref tool is not supported. Links created by the CDCXref tool will be stripped out of the rendition. In order to continue to use the links, the affected PDF renditions must be edited with Liquent SmartLink for PDF to recreate the links in a PDF to be used as a source document.
4897; [00056710]		Using the estext plugin, a very large document failed to render and an "`unable to transform to PDF`" error was displayed. This issue is resolved by modifying the plugin to use less memory.
4891; [00054164]		When using the DMS Browse window in Liquent InSight to browse SharePoint documents, the DMS Search Results frame displayed the Creation Time and Last Modified dates of the documents as 01-Jan-1970 when the locale/region on the SharePoint server was not set to US. Attempting to assign one of the SharePoint documents resulted in an error. This issue is resolved by reinstalling the LIQUENT SharePointServices installer on your SharePoint server.
4887; [00055257]		Due to an issue with Microsoft Word 2016, link boxes in the rendered PDF for page number links in TOCs were only one digit wide, regardless of the number of digits in the page number. This resulted in a portion of page number links with multiple digits being outside of the link box. This issue was resolved by updating the code to avoid the issue.
4870		The CDCXref tool is not supported. Links created with the CDCXref tool will no longer appear in the PDF rendition. In order to continue to use the links, the affected Word source document must be edited with Liquent SmartLink for Word to recreate the links in the source document. If the links are not to be preserved, re-render the affected Word source document to remove these links from the PDF rendition.
4859; [00053717, 00052994]		Due to an issue caused by Microsoft updates, attempting to publish to PostScript resulted in an error. This issue was resolved by modifying the code to workaround the issue with the Windows SDK.
4852		Liquent InSight Rendering Online Help was migrated to a new server. As a result, any previous manually entered help URLs will not need to be updated. The new server uses the https protocol.
4843; [00052540]		Very large Microsoft Word documents with tens of thousands of tables and no links were taking several hours to render. The algorithm to iterate through the tables in a document was refactored to reduce the time required to render the documents.
4835; [00052177]		The occurrence of a "next line" character (`0x0D` or `0x0A`) together with the "feed form" character (`0x0C`) on the last line of a page caused the ESText plugin to render blank pages in the PDF rendition. This issue is resolved.
4802; [00050141, 00051465]		The password character length for the Liquent InSight Rendering installer was limited to the size of the dialog window. This issue has been resolved. The password can now be set up to 32,767 characters in length.
4783; [00048853]		It can take over an hour to render a document when the Microsoft Word option Show Only Comments and formatting in Balloons is selected. This issue has been resolved. The document now renders in a reasonable time.
4759, 4325; [00045108]	4.3.0.34	When rendering via InSight Publisher, the Title of a PDF rendition was being set to the original filename plus extension and not to the Title of the source document. This issue has been resolved. Now, if the document is in Documentum, the Title in the rendition will be Documentum's Title property. If the document is not in Documentum, the Title in the rendition will be the Title property of the document. You will have to re-render all documents that need the Title updated.
4750, 4801; [00047063], [00049812]		Links and TOC entries in Microsoft Word 2013 source documents targeted the wrong page in the PDF rendition when the "All Markup" option was selected. This issue is resolved. Note: The issue will still be present if the "Simple Markup" option is selected. The "All Markup" option must be used.
4748; [ 00046492]		Bookmarks below the selected level were being expanded after publishing. This issue is resolved.
4747; [00046851]		Single-character reference field links in a Microsoft Word document did not target the correct destination page in the PDF rendition. This issue is resolved.
4715		Liquent InSight Rendering sometimes sent multiple notifications to InSight. This issue is resolved. Liquent InSight Rendering now does not send extra notifications.
2134		Change to Business Service Distribute, distribute-folder request: InSight Publisher uses the distribute-folder request to distribute published output. In previous versions, this was part of a database transaction, so if any single file could not be distributed, the transaction was terminated and nothing was distributed. Now if there is a failure, files that have already been distributed will remain (but the distribute will stop).

JavaScript must be enabled in order to use this site.Please enable JavaScript in your browser and refresh the page.

Resolved Issues: Liquent InSight Rendering 4.4

The following issues that were reported to Technical Support have been resolved. Issues are listed in descending order by their tracking numbers. Customer incident numbers that were recorded when the issues were reported are included in brackets [#####] following the tracking number.


Issue	Build	Description
4898		The CDCXref tool is not supported. Links created by the CDCXref tool will be stripped out of the rendition. In order to continue to use the links, the affected PDF renditions must be edited with Liquent SmartLink for PDF to recreate the links in a PDF to be used as a source document.
4897; [00056710]		Using the estext plugin, a very large document failed to render and an "`unable to transform to PDF`" error was displayed. This issue is resolved by modifying the plugin to use less memory.
4891; [00054164]		When using the DMS Browse window in Liquent InSight to browse SharePoint documents, the DMS Search Results frame displayed the Creation Time and Last Modified dates of the documents as 01-Jan-1970 when the locale/region on the SharePoint server was not set to US. Attempting to assign one of the SharePoint documents resulted in an error. This issue is resolved by reinstalling the LIQUENT SharePointServices installer on your SharePoint server.
4887; [00055257]		Due to an issue with Microsoft Word 2016, link boxes in the rendered PDF for page number links in TOCs were only one digit wide, regardless of the number of digits in the page number. This resulted in a portion of page number links with multiple digits being outside of the link box. This issue was resolved by updating the code to avoid the issue.
4870		The CDCXref tool is not supported. Links created with the CDCXref tool will no longer appear in the PDF rendition. In order to continue to use the links, the affected Word source document must be edited with Liquent SmartLink for Word to recreate the links in the source document. If the links are not to be preserved, re-render the affected Word source document to remove these links from the PDF rendition.
4859; [00053717, 00052994]		Due to an issue caused by Microsoft updates, attempting to publish to PostScript resulted in an error. This issue was resolved by modifying the code to workaround the issue with the Windows SDK.
4852		Liquent InSight Rendering Online Help was migrated to a new server. As a result, any previous manually entered help URLs will not need to be updated. The new server uses the https protocol.
4843; [00052540]		Very large Microsoft Word documents with tens of thousands of tables and no links were taking several hours to render. The algorithm to iterate through the tables in a document was refactored to reduce the time required to render the documents.
4835; [00052177]		The occurrence of a "next line" character (`0x0D` or `0x0A`) together with the "feed form" character (`0x0C`) on the last line of a page caused the ESText plugin to render blank pages in the PDF rendition. This issue is resolved.
4802; [00050141, 00051465]		The password character length for the Liquent InSight Rendering installer was limited to the size of the dialog window. This issue has been resolved. The password can now be set up to 32,767 characters in length.
4783; [00048853]		It can take over an hour to render a document when the Microsoft Word option Show Only Comments and formatting in Balloons is selected. This issue has been resolved. The document now renders in a reasonable time.
4759, 4325; [00045108]	4.3.0.34	When rendering via InSight Publisher, the Title of a PDF rendition was being set to the original filename plus extension and not to the Title of the source document. This issue has been resolved. Now, if the document is in Documentum, the Title in the rendition will be Documentum's Title property. If the document is not in Documentum, the Title in the rendition will be the Title property of the document. You will have to re-render all documents that need the Title updated.
4750, 4801; [00047063], [00049812]		Links and TOC entries in Microsoft Word 2013 source documents targeted the wrong page in the PDF rendition when the "All Markup" option was selected. This issue is resolved. Note: The issue will still be present if the "Simple Markup" option is selected. The "All Markup" option must be used.
4748; [ 00046492]		Bookmarks below the selected level were being expanded after publishing. This issue is resolved.
4747; [00046851]		Single-character reference field links in a Microsoft Word document did not target the correct destination page in the PDF rendition. This issue is resolved.
4715		Liquent InSight Rendering sometimes sent multiple notifications to InSight. This issue is resolved. Liquent InSight Rendering now does not send extra notifications.
2134		Change to Business Service Distribute, distribute-folder request: InSight Publisher uses the distribute-folder request to distribute published output. In previous versions, this was part of a database transaction, so if any single file could not be distributed, the transaction was terminated and nothing was distributed. Now if there is a failure, files that have already been distributed will remain (but the distribute will stop).