Join us for an engaging webinar, as we unravel the potential of AI for revolutionizing document management.
Watch Now
Enable your employees to remain productive throughout the document management process.
Read More
Learn how SmartZone uses a regular expression engine integrated into the recognition engine to achieve the best possible accuracy on data that can be defined by a regular expression.
Docubee is an intelligent contract automation platform built to help your team success
What are the absolute essentials for embedding the PrizmDoc Viewer into my web page/application?
Viewer API (viewercontrol.js)
The Viewer API is the base building block of the Viewer. We ensure that API changes are backward compatible with point releases (for example, PrizmDoc v13.5 → PrizmDoc v13.6) and will not introduce breaking changes unless critical. With major releases we also endeavor to ensure backward compatibility with previous releases of the Viewer API.
HTML Templates (viewerCustomization.js) and CSS (viewercontrol.css, viewer.css)
The Viewer that is shipped with the product will be maintained and enhanced from release to release. The Viewer HTML and CSS markup will change with each release. Once you have begun to modify your markup, it is recommended that you consider subsequent PrizmDoc releases as sample code, in which you would evaluate product changes and choose to incorporate all or parts of those changes into your customization.
JavaScript files (viewer.js)
The Viewer JavaScript that lies above the Viewer API is unobfuscated and open for customization. While we expect many developer needs will be satisfied through configuration parameters and minor HTML or styling changes, some developers will desire to modify viewer.js for more advanced customization. You should carefully consider your development and ongoing maintenance strategy to ensure that future releases of PrizmDoc are easy to integrate into your customizations. We cannot guarantee backward compatibility of viewer.js in future releases as it is central to the functionality of the Viewer.
For information on integrating PrizmDoc Viewer, see the Getting Started section of the documentation.
For more in depth customization, see the PrizmDoc Customization section of the documentation.
I am receiving a 401 Unauthorized when trying to use PrizmDoc Cloud. What could be the issue?
This error is likely the result of neglecting to specify your API key.
To fix this, specify your API key in the headers of your request to create a viewing session.
I’m receiving Uncaught ReferenceError: viewLabel is not defined when trying to embed the PrizmDoc Viewer in my web application. What could be the issue?
Uncaught ReferenceError: viewLabel is not defined
This error indicates that the language property in the viewer initialization has not been specified or is undefined.
language
To fix this, ensure you are loading viewerCustomizations.js.
viewerCustomizations.js
If the version you are working with predates viewerCustomizations.js, you can get a copy of viewerCustomizations.js from the viewer assets hosted here and update your viewer initialization code.
I’m receiving the error “Uncaught TypeError: Cannot read property ‘viewer’ of undefined” when trying to embed the PrizmDoc Viewer in my web application. What could be the issue?
This indicates that the template property in the viewer initialization has not been specified or is undefined.
template
If the version you are working with predates viewerCustomizations.js, you can get a copy of viewerCustomizations.js from the viewer assets, hosted here, and update your viewer initialization code.
How do I store and retrieve documents in subdirectories of the configured documents directory in PrizmDoc PAS?
You can retrieve documents from subdirectories when dealing with local files. Simply pass the subfolder in the fileName parameter when creating the viewing session. You can test this by manually placing a document inside a subfolder and making the following POST request:
fileName
POST
`http://localhost:3000/ViewingSession` { "source": { "type": "document" "fileName": "folder/document.pdf" } }
How do I ensure temp files are deleted when closing ImageGear .NET?
All PDF objects are based on underlying low-level PDF objects that are not controlled by .NET resource manager and garbage collector. Because of this, each PDF object that is created from scratch should be explicitly disposed of using that object’s Dispose() method.
Also, any ImGearPDEContent object obtained from ImGearPDFPage should be released using the ImGearPDFPage.ReleaseContent() in all cases.
This should cause all temp files to be cleared when the application is closed.
What does it mean when I see “Email Address is not Registered” when entering in an email in the Evaluation Dialog?
You will see this error if you have not registered on the Accusoft website.
To register your email address, please visit the following link below:
https://my.accusoft.com/Account/FirstTimeUser?Length=7
How do I use a Network Drive path for Image and ART storage in my ImageGear .NET web application?
In an ImageGear .NET web application, you have to define the location of the images and annotations directory in the storageRootPath and artStorageRootPath configuration property. In the current version of ImageGear .NET, the storageRootPath and artStorageRootPath do not work with a network drive path \\SERVER-NAME\sharefilename.
storageRootPath
artStorageRootPath
\\SERVER-NAME\sharefilename
The workaround for this would be to create a Symbolic link from a local directory to the network drive directory.
> mklink /d "local path" \\SERVER-NAME\sharefilename
web.config: storageRootPath="local path" artStorageRootPath="local path"
How can I improve the performance and memory usage of scanning/recognition in Barcode Xpress?
Barcode Xpress supports a number of optimization settings that can improve your recognition performance, sometimes up to 40%, along with memory usage. The best way to optimize Barcode Xpress is to fine-tune the properties of the Reader class to be specific to your application’s requirements.
Reader
BarcodeTypes
MaximumBarcodes
Area & Orientation
ScanDistance
Finally, BarcodeXpress Professional edition does not impose a 40 page-per-minute limit on processing.
What quality should my images be for processing form data and recognition using FormSuite?
In all cases, you want to have your images as clear and as clean as possible. For any particular procedure, please consider the following:
OCR and ICR: Capture images in at least 300 DPI resolution. Ideally, working in black and white allows the objects of interest on your image to be better defined and recognized. Free the image form all noise as much as possible. As if a human were reading it, you want the text objects on the image to be as legible as possible. For ICR, ensure that the characters are printed (no cursive text, etc).
Barcode recognition: As with OCR and ICR, capture images in at least 300 DPI and working with black and white content can provide excellent results. Ensure that the bars in the barcodes are clearly defined on the image and are not malformed (for example, the barcodes should have the proper start and stop sequence, etc). Clear as much noise from the image as possible.
Forms matching and registration: As with the prior 2 items above, capture your documents in at least 300 DPI. Ensure that your resolution is consistent between your form templates and incoming batch images. Form templates should only contain data that is common to every image that is being processed (i.e. Form fields, the text that appears on the blank form itself, etc). The template should not have filled-in field information as this will affect the forms matching process.
On Windows, are there any restrictions on the type of account that I can install PrizmDoc under? If so, what are they?
The account that you install PrizmDoc under has to be part of the Local Administrators group. As the installer creates Windows services, administrative-level permissions are required.
What operating systems (Windows, Linux, etc.) does PrizmDoc officially support?
Please refer to our latest documentation for the most up-to-date list of supported operating systems:
For documentation on older versions of PrizmDoc, please see our documentation archive.