When configuring a DIP process, it is important to take the Default File Format of the Document Types associated with the process into account.
Multiple file formats can be processed via DIP into the same Document Type, but including a Document Type configured to use Image File Format as its Default File Format in a DIP process will cause the process to behave slightly differently than when other Default File Formats are used.
DIP processes attempt to open image files to determine the number of pages (i.e. individual images) included in each file. If non-image files are imported via DIP into a Document Type configured to contain, by default, image documents, errors may be displayed in the Verification Report or the documents may not be able to be displayed in the Client.
If you are importing files of a file format that is different from the Document Type's Default File Format, you must include the >>File Type Default Keyword Type in the Import Index file. If the >>File Type Default Keyword Type is not added, you are unable to view your imported documents.
You should thoroughly test your DIP process configurations, including examining your Document Type and file format settings, and occasionally examine the documents imported via DIP to ensure that all documents are being imported properly.
If a batch contains one or more corrupt image files, the batch will process correctly, but the corrupted files are not imported into OnBase. The batch is moved to the Awaiting Commit queue, but the Import Index file is moved to the ERROR_FILES folder.