PrizmDoc Viewer v13.7

Adds support for Ubuntu 18.04 LTS, plus upgrades to JSON markup layer capability in the Redaction Creator API.
May 13, 2019 - 8:14
New Version


  • Now supports Ubuntu 18.04 LTS.
  • JSON support in the PrizmDoc Server Redaction Creator API - Previously, the Redaction Creator API only created the PrizmDoc legacy XML format for text matching a Regular Expression. This was inconsistent since JSON markup layer is used in all other areas of PrizmDoc.
  • Improved stability of PrizmDoc Server running on Linux by updating Mono run-time components to address possible unresponsiveness of PCC Imaging Services when loading configuration settings on start up.
  • Improved MSO conversion service's resistance to faulty conversion transactions by properly detecting and recycling its child processes without having to become unhealthy and restart the service.
  • Improved the consistency of the burn-in operation performed over the text redaction markup for every character regardless of its glyph outline. Now, a character becomes redacted if the redaction area overlaps the character's glyph area (calculated by width * height) by 40% or more.
  • Improved the cursor behavior in the viewer to better indicate the effect of using the mouse. In supported browsers, the grab cursor is now displayed when the hand pan tool is selected. The cursor no longer changes when hovering over a mark if the selected mouse tool does not support mark selection. If the selected mouse tool does support mark selection, the move cursor is displayed over a mark only if the mark is selectable.


  • With the PrizmDoc Viewer v13.7 release, support for Windows Server 2008 (R2) will be deprecated. With the future release of PrizmDoc Viewer v14.0, support for Windows Server 2008 (R2) will be discontinued altogether.
  • Addressed an issue where the installed samples are not able to build when following the provided README steps due to a missing folder and misplaced assets.
  • Addressed the Markup Burner issue with text annotations containing tabulation characters that were incorrectly converted to white square characters in the output PDF upon burn in. We are now replacing tabulations with spaces for more accurate fidelity in the output PDF.
  • Addressed PrizmDoc limitation of the MSO rendering engine causing the conversion process to fail on any PowerPoint document once the MS PowerPoint instance becomes unresponsive.
  • Addressed issues where PrizmDoc's file downloading APIs failed to download files which had non-ASCII characters in file names, or corrupted filenames during the downloading. These APIs now use an RFC 8187 compliant Content-Disposition header in their responses to correctly support such file names. The only exception is GET /PCCIS/V1/WorkFile/{fileId}, which continues to use the simpler ASCII-only syntax when using an automatically generated file name. This was done to preserve backward compatibility for customers who use PrizmDoc Client package v13.6 or older.
  • Addressed incorrect recycling of MSO conversion service's child processes upon the service's startup, which could result in a faulty conversion transaction making the entire MSO conversion service permanently unhealthy.
  • Addressed incorrect location of text redaction markups over bulleted text in PDF output to match what appears in the viewer.
  • Addressed an issue within the Markup Burner API that resulted in a duplicate Redaction Rectangle mark in the output PDF. This would occur when applying a Filled Rectangle redaction over a PDF with the transparency area defined by the image mask (a mask entry in the image dictionary).
  • Addressed PAS host header translation issue which made it impossible to route requests from PAS to PrizmDoc when there is a load balancer in between them. Now, PAS sets the outgoing request host header to PrizmDoc host value.
  • Corrected an issue in the Viewer UI that allowed the user to select the "Exact Phrase" option which is not a viable option for Wildcard search. The Exact Phrase option is now disabled in Wildcard search.
  • Updated the Search Tasks API to accept a JSON body of up to 1MB in size. Previously, this value was set to 100KB which could have resulted in "Invalid JSON" errors for valid JSON bodies that were greater than this value.
  • Addressed the Markup Burner API issue occurring when attempting to redact text in the text block immediately following a previously redacted block in the source PDF document.
  • Addressed an issue where in some cases the last page of a document was blank when printed.
PrizmDoc Viewer

PrizmDoc Viewer

HTML5 Document Viewer and Web APIs.

Got a Question?

Live Chat with our Accusoft licensing specialists now.