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 contact automation platform built to help your team success
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"
What is the absolute bare minimum I need to use PrizmDoc Cloud?
This will allow you to load a document via a URL using PrizmDoc Cloud. Just include your PrizmDoc Cloud API key in the POST request headers.
Please note: This is purely intended as a proof-of-concept. You should never include your API key in your client-side Javascript.
<!DOCTYPE html> <html lang="en"> <head> <!-- Metadata --> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> <meta name="description" content="" /> <!-- Title --> <title>AccuSample</title> <!-- Libraries --> <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.0/normalize.min.css"> <!-- PrizmDoc CSS --> <link rel="stylesheet" href="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/css/viewercontrol.css"> <link rel="stylesheet" href="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/css/viewer.css"> <!-- Inline Stylesheet --> <style></style> </head> <body> <!-- #viewer --> <div id="viewer" class="pccv pcc-full-screen"></div> <!-- Libraries --> <script src="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/js/jquery-3.4.1.min.js"></script> <script src="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/js/jquery.hotkeys.min.js"></script> <script src="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/js/underscore.min.js"></script> <!-- PrizmDoc JS --> <script src="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/js/viewercontrol.js"></script> <script src="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/js/viewer.js"></script> <script src="https://raw.githack.com/Accusoft/hello-prizmdoc-viewer-with-nodejs-and-html/master/public/viewer-assets/js/viewerCustomizations.js"></script> <!-- Inline Script --> <script> let viewingSessionId; let viewerControl; $(document).ready(function() { $.ajax({ "type": "POST", "url": "https://api.accusoft.com/prizmdoc/ViewingSession", "headers": { "acs-api-key": "4lTamQVZmrkqZhH8cZhdu7L0xyhUa3gorcaCFQpA_zmuowZs4zoF39V4IckpnVW_" }, "data": JSON.stringify({ "source": { "type": "url", "url": "https://www.usability.gov/sites/default/files/creating-wireframes.pdf" } }) }).done(function(response) { PCCViewer.Ajax.setHeaders({ "acs-api-key": "4lTamQVZmrkqZhH8cZhdu7L0xyhUa3gorcaCFQpA_zmuowZs4zoF39V4IckpnVW_" }); viewingSessionId = response["viewingSessionId"]; // Initialize viewer viewerControl = $("#viewer").pccViewer({ "documentID": viewingSessionId, "imageHandlerUrl": "https://api.accusoft.com/prizmdoc", "language": viewerCustomizations.languages["en-US"], "template": viewerCustomizations.template, "icons": viewerCustomizations.icons, "annotationsMode": "LayeredAnnotations" }).viewerControl; viewerControl.on("ViewerReady", function() { console.log("Ready!"); }); }); }); </script> </body> </html>
Can I use all of the features and configuration options in PrizmDoc Cloud-Hosted that I can in PrizmDoc Self-Hosted?
Currently, PrizmDoc Cloud does not allow for editing the server central configuration parameters, but the defaults have been set to allow for more complex documents that might otherwise fail in order to account for the lack of ability to modify these options.
What are the best quality images to use when processing form data and recognition?
In all cases, you’ll 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 will allow 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 was reading it, you’ll want the text objects on the image to be as legible as possible. For ICR, make sure 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. You’ll also want to make sure that the bars in the barcodes are clearly defined on the image and are not mal-formed (for example, the barcodes should have the proper start and stop sequence, etc). As always, 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. Make sure that your resolution is consistent between your form templates and incoming batch images as well. 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.
We are using the Webforms Samples and want to know how to enable the “Always User Raster” feature. Which file needs to be modified and how should it be modified?
In order to enable the “Always Use Raster” option for our Webforms sample, you will need to do the following:
How To:
\Prizm\Samples\dotnet\webforms\full-viewer-sample\Default.aspx
Line to Replace:
} else { sessionData.source = getDocumentSource(query.document || ''); }
Replace with:
} else { sessionData.source = getDocumentSource(query.document || ''); sessionData.render = { html5: { alwaysUseRaster: true } }; }
Next, to update the Central Configuration file you will need to stop the Prizm Services.
Make a backup of the prizm\prizm-services-config.yml file.
Edit the .yml file and remove the leading # for the following line and add true to the array so that it looks like the following:
viewing.sessionConstraints.render.alwaysUseRaster.allowedValues: [true, false]
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.