The following items are either currently under investigation by the Accusoft Engineering organization or provide further information regarding PrizmDoc. Should you require an updated status on any of these items, please contact Accusoft Customer Support.
Note: For complete PrizmDoc documentation, refer to the PrizmDoc Online Help.
Please note the following important information about the PrizmDoc installer:
PrizmDoc requires a clean installation when migrating from an earlier version than v12.0. You must first uninstall any previous versions of PrizmDoc and reboot your system. Only then should you install PrizmDoc.
Currently, the path PrizmDoc is installed to on Windows cannot exceed 64 characters total. Longer paths are rejected by the installer.
When installing PrizmDoc on Windows, the account used to start the Prizm service requires a password to be defined. Without a password, the Installer will not be able to proceed.
If you print large documents (100+ pages) from the Viewer, you may run into browser memory constraints that are beyond our control. We recommend downloading large documents as a PDF and then printing them.
Currently, burning markup into PDF documents that contain XFA fields is unsupported. Attempting to burn markup into XFA documents will result in an error.
There are known limitations when trying to use Quick Actions to redact large search result sets that are over hundreds of results.
With some browsers the E-Signature Viewing Client performance could be impacted when the number of fields in the document is more than 1,300.
Note that we have modified the default properties for several marks when creating them via the API. As long as you are setting mark properties, such as color and line width, this should not affect your code.
There are known issues with E-Signing when working on iOS devices that can cause the screen to move erratically when moving from field to field. This does not keep the experience from being usable, but it can be disconcerting while using.
There are limitations to using the Full-Page Redactions mouse tool on a mobile device.
When requesting raster page content, a '500' error may appear in the network log. As part of performance improvements, the viewer now always requests SVG content first. If SVG content is not available, a '500' error will be communicated and the client will then request raster content. Although this does not negatively affect the viewer behavior, this will be changed in a future release to handle the request differently.
When printing a document in Firefox or Safari, embedded images may be truncated or missing in some cases.
When printing a document in Chrome, images may be printed with a black background when the background should be transparent.
PDF files with embedded raster images in the Indexed color space using CMYK palette might not display with the correct colors in the Viewing Client after conversion to SVG.
Search results returned in the Viewing Client for PDF documents may not be highlighted in cases where the PDF contains image over text results. In this case, content will be returned in the Search results tab, but the highlighted search terms will not be displayed in the page view when navigating to the appropriate page. In this case, a message will be displayed indicating that the page does not support text highlighting. This will be improved in future versions.
It is recommended that the document cache be cleared prior to upgrading PrizmDoc. Failure to clear the cache will result in the inability to search documents in the Viewing Client that have been cached in prior versions of PrizmDoc.
When printing documents with the Viewing Client in Safari browser on Windows, blank pages are sometimes created, causing extra pages in the document.
If you are using Viewing Packages in PAS and upgrading from a version prior to 13.1, you must upgrade your database schema. See the setting up your database topic for more information on how to upgrade PAS.
The Content Conversion Service does not support conversion of DICOM files to a searchable PDF document format.
The Content Conversion Service does not support conversion of transparent TIFF files to a searchable PDF document format.
The Content Conversion Service's feature that performs optical character recognition (OCR) to convert a raster file to a searchable PDF document does not support CentOS 6 and Red Hat Enterprise Linux 6 platforms.
If the PDFPS microservice exceeds the open file descriptor limit, then PrizmDoc will restart the PDFPS microservice.
The Document Compare feature is designed for comparing different revisions originating from the same MS Word document. Using this feature for comparing any random MS Word documents is not recommended and may lead to unexpected results.
PrizmDoc relies on a fontconfig package that is not shipped with the product and that might be missing from some distributions of Ubuntu. This was resolved by adding automated checks in the PrizmDoc 13.0 installation scripts. As a workaround for older versions of PrizmDoc, we recommend installing the fontconfig package manually by using sudo apt-get install fontconfig.
All Server-Side configurations should be identical across all the servers in a cluster because documents are frequently sent to a random server for processing. This also applies for the multi-server Microsoft Office Conversion configuration that now supports connectivity to PrizmDoc Servers running on Linux.
HTML conversion on Windows depends on system DPI. Higher system DPI results in smaller HTML content size when viewing HTML.
Abandoned Viewing Sessions - The text extraction process will continue if a user abandons a session before the text extraction process completes. This will be improved in a future release, but it is important to know that a user abandoning a document does not necessarily release conversion resources on the server.
The new POST /v2/searchContexts/{contextId}/completed URL should not have a body. Though the request may still succeed if a body is used in the v12.2 release, it can begin to fail in the future. Using any body with this request should be avoided.
You must have Microsoft Office installed on the server when using the Microsoft Office Conversion license. If you do not have Microsoft Office installed, you will get an error when converting Office documents or displaying them in the PrizmDoc Viewing Client.
Always keep your PrizmDoc Windows server updated with the latest Windows and MS Office updates when using the MSO rendering option. If you don't have the latest updates, you may see rendering issues.
Internal hyperlinks (like TOC bookmarks) within Office documents are not clickable when rendered or converted to PDF with the use of the Microsoft Office Conversion option.
Word documents containing fields with invalid references will result in the MS Office rendering engine to report "Error! Reference source not found" in those fields when converting or displaying those documents in the Viewing Client.
CMYK JPEG files may display as negative (or inverted) color images when converted to PDF or raster formats.
The following TTC font packages on Ubuntu might conflict with Tunga and Latha font substitution implemented in PrizmDoc Office Converter causing inaccurate rendering. You may need to uninstall those packages for better font substitution fidelity:
You may see space between the image tiles (when rendering raster images that are broken into tiles, within HTML tables) if those tables do not fit into one page.
When using PrizmDoc Server in a self-hosted Docker environment, international symbols may not be redacted correctly. In order for international symbols to be redacted correctly, make sure a unicode locale, for example, en_US.UTF-8, is enabled. Add the following settings to your Docker configuration file:
# generate and enable en_US.UTF-8 locale
RUN locale-gen en_US.UTF-8
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8
The new Email Conversion Service fidelity improvements will result in shifting the rendered content (due to inline image rendering support for more accurate rendering of the HTML body) and making the existing annotation and redaction markup not aligned with the old rendered content. Customers wanting to redact the new output would need to re-create the annotation and redaction markups.
Excel worksheets will now be rendered with grid lines, headers, footers, and hidden content visible by default causing the existing annotation and redaction markup to be not aligned with the old rendering content. Customers wanting to redact the new output would need to re-create annotation and redaction markups. Customers wanting to go back to the old style rendering can do that by changing the Excel rendering properties available in the central configuration file.
Embedded OLE objects in CAD files are not currently supported for rendering.
Conversion failures observed for simultaneous EML and MSG files conversions on Windows 2012 R2 multi-processor configurations.
Ubuntu 14.04 kernel v3.13.0-48-generic has been shown to be unstable, which has led to crashes in the version of Mono used by PrizmDoc (https://bugzilla.xamarin.com/show_bug.cgi?id=29212). Upgraded kernel v3.13.0-70 has been validated for use with PrizmDoc on Ubuntu 14.04, and its use is strongly recommended.
Deep Image Redaction may not work as expected when the source PDF contains G32D encoded TIFF images. PDF redactions will be created but any content on the G32D encoded content intended for redaction will not be obscured by black pixel data.
There are some special symbols, such as '@', that cannot be properly processed in auto-redaction.
When converting HTML to PDF using the Content Conversion Service, you may see poor performance on larger documents when pdfOptions.forceOneFilePerPage is set to true. We recommend that pdfOptions.forceOneFilePerPage be set to false when converting more than 20 pages.
Watermarking is not supported for CAD files.
The MarkupBurner, responsible for the underlying process of annotation, redaction and esignature, does not currently support CAD based files.
The ext3 file system limits the number of subdirectories within a single directory to 31,998. Because PrizmDoc creates a directory for each viewing session and/or work file, systems with high traffic combined with longer cache expiration periods may encounter request errors with ERROR_GEN_FAILURE. The ext3 file system is the default for ephemeral drives in AWS as well as many current Linux distributions. Consequently, the possibility of encountering this error exists for these systems unless ext4 was specifically chosen at installation. To enable directories containing greater than the 32K subdirectory limit, ext4 turns on HTree indexes (a specialized version of a B-tree) by default. For systems with extraordinarily high traffic coupled with extended cache expiration times, it is recommended the product be installed on Linux systems with ext4 file systems or at least to configure caching to utilize an ext4 file system.
Watermarks appear in bold and are not transparent.
The PrizmDoc Server "GET Page" call requesting a JPEG thumbnail for a certain page hosted on Windows might return HTTP error 500.
Excel pagination causes the Office converter to generate more pages. This puts more stress on the server and may cause the conversion to timeout.
Certain VML shapes from Word documents might not render properly to the client viewers.