Known Issues
The following items are either currently under investigation by the Accusoft Engineering organization or provide further information regarding PrizmDoc Viewer. Should you require an updated status on any of these items, please contact Accusoft Customer Support.
Installer
Please note the following important information about the PrizmDoc Viewer installer:
- Currently, the path PrizmDoc Viewer is installed to on Windows cannot exceed 64 characters total. Longer paths are rejected by the installer.
- When installing PrizmDoc Viewer on Windows, the account used to start the PrizmDoc service requires a password to be defined. Without a password, the Installer will not be able to proceed.
PrizmDoc Viewer
- When evaluating PrizmDoc Viewer Self-Hosted without an installed license, the informative dialogs indicating the product is running in evaluation mode and notifying about evaluation limitations may not show in IE browsers.
- Safari browser may truncate long file names (containing 96 or more ASCII characters or 27 or more non-ASCII characters) when downloading source files from PrizmDoc viewer. This issue only exists when connecting to PrizmDoc Viewer via http/1.1 protocol (with or without https). Setting up an http/2 proxy in front of PrizmDoc viewer avoids the issue. See also Safari bug report 47914517.
- Border of graphic elements may not render for specific PDF documents.
- Starting from 13.6 release some PDF documents may render slightly shifted compared to previous versions of PrizmDoc.
- Raster images using CMYK colorspace in PDF documents may be rendered with a slightly different color.
- 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.
- Burning markup into PDF documents that contain AcroForm fields is unsupported. Attempting to burn AcroForm fields in PDF documents will leave those field values unchanged.
- 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 Viewer. 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 Viewer.
- When printing documents with the Viewing Client in Safari browser on Windows, blank pages are sometimes created, causing extra pages in the document.
- PrizmDoc Viewer does not currently perform text-extraction and search on PDF annotation markup within PDF documents. This annotation markup includes Text and FreeText annotation types as specified in the PDF reference guide.
- PrizmDoc Viewer does not currently provide full support for searching and extracting text which reads from right-to-left (like Arabic and Hebrew), which may cause the search and text extraction results to display such text in wrong left-to-right direction.
PrizmDoc Server
- 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 Viewer will restart the PDFPS microservice.
- The Document Compare feature is designed for comparing different revisions originating from the same.
- PrizmDoc Viewer services render 2-bit LZW-compressed TIFF images incorrectly on Windows.