Data Group Auto-Mapping allows data groups to be automatically imported into PaperVision Enterprise or ImageSilo which removes the need for manual processing. You must enable and configure auto-mapping in either PaperVision Capture or PaperFlow when creating new or editing an existing export job. This option is available in PaperVision Capture (R83 or later) and PaperFlow (R81 or later) releases.

Users may receive an error message similar to the following when attempting to open/view a document from the search results:

The server returned the following error information:
Function LoadDocInfoEx.pvtCachePageRange.CachePage.PVDMSystem:
Error -28000; Server01 was unable to locate file
[ABCD0001]\ABCD0001\IMG1\00001\00001001.TIF

The Direct Launch option changes the way the document viewer launches and displays documents. The Direct Launch method passes a URL to the operating system that tells it to launch an executable that will then open the Web Assistant and display a document. With Direct Launch, there is no bi-directional communication with the Web Assistant. For example, altering index values, adding documents, or checking documents in or out will not automatically update the search results window.

This article explains how to manually configure the PaperVision Automation Service (PaperVision ProcessInitiator2) using the PaperVision Configuration Utility. If a user skipped configuring the Automation Service during the setup wizard, the steps below can be used to configure the service.

Note: These steps are only applicable for PaperVision Enterprise R74 and above.

In certain scenarios users may receive an Error -30000 message when viewing images through the PaperVision Enterprise website. This may be a result of the anonymous account having all the necessary permissions and rights; but the images are stored at a different location from the Web Server. In some scenarios, the images may even reside on the same physical computer but are being accessed over the network using UNC paths. This type of configuration requires that the “ASP.NET Impersonation” option be enabled for IIS versions 7.5 and higher.