What's New for v12.2

PrizmDoc v12.2 introduces the following new features:

You can now programmatically set the initial zoom level of the Viewing Client before any content is displayed.
The addMarkFromSearchResult API has been added to ViewerControl that allows adding a text-based mark from a search result. This allows for a quick conversion of a search result into a mark.
We have taken steps to make it possible to support Content Security Policy (CSP) compliance in the Viewing Client. Please contact Customer Support for additional details.
E-Signature Improvements
- We've added support for adding input masks to a text box. You can require a signer to fill in the text box with specific information, such as a Phone Number, Social Security Number, Date, Zip Code, or Model Number.
- Fields can now be marked as "Read Only" in the Template Designer. If a field is marked as "Read Only", the content cannot be modified in the Signing Module. This is useful in scenarios where data is filled in programmatically and the developer doesn't want the end user to modify the field.
- The selectEditorText API has been added to ViewerControl to allow selecting the editable text within a mark's text editor.
- We've added APIs that allow setting/getting filled-in field data in the Signing Module. This makes it possible to set these values easily for your particular scenarios.

You can now programmatically cancel long-running search tasks (such as searching on very large documents) for PrizmDoc Application Services and PrizmDoc Server.
The Content Conversion Service now supports conversion of password protected PDF and Office documents.
Two new central configuration parameters are now available to define the background color for viewing CAD documents:
- fidelity.vectorBackgroundColor.view.default - can be used for those CAD cases when the background is not specified in the document (most CAD files except DGN).
- fidelity.vectorBackgroundColor.view.override - can be used when the intention is to ignore the background color specified in the document.
The Content Conversion Service now reports more granular "percentComplete" status when converting documents (previously it was only reporting 0% and 100%).