Before you begin using this application, it is important to make sure that you have met the prerequisites in the following sections.
Before you begin using this application, it is important to make sure that you have met the prerequisites in the following sections.
What are the minimum server and application specifications required for inDocs to run successfully?
inDocs requires its own dedicated application server where it will have unrestricted use of all available resources.
The minimum server specifications for inDocs to run are:
The existing SQL Server installation used for Intact iQ will be used.
The server authentication needs to be set to use SQL Server and Windows Authentication Mode.
If you have an existing Infrastructure Support Contract (Hardware Support) with Intact, this will be configured for you. However, if your environment is supported by a third party, you will need to request this change directly with your third party support company. Note that your third party may cancel any support you have if an Intact employee has changed the configuration without prior notice.
Web Browser
A W3C compliant browser must be used to use the inDocs Server Web Client.
Our tested and approved browsers are:
However, any “Chromium” open-source web browser may work. Internet Explorer and Microsoft Edge Legacy (pre-2020) is unsupported, as neither of these are W3C compliant. Failure to use a supported browser will result in the inDocs Server Website displaying incorrectly with missing information.
The Intact Support team will not be able to provide application support for any other browsers other than the above approved browsers.
Microsoft Webview2 Evergreen Bootstrapper
Download the Webview2 Runtime (Evergreen Bootstrapper) and install on all servers and/or PCs where iQ runs.
https://developer.microsoft.com/en-us/microsoft-edge/webview2/#download-section
Microsoft Visual C++ 2015/2022 Runtime 14.36.32532 and above
Download the MS Visual C++ Redistributable and install on the server that inDocs will be installed on.
https://aka.ms/vs/17/release/vc_redist.x64.exe
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
Intact iQ
inDocs requires Intact iQ R33S6 or above.
The REST API licence must be purchased for the InAP module. There are two versions:
We will always ensure that you are running the latest stable release of inDocs and its relevant plugins as your Intact iQ application release is updated.
Legacy Support
There is legacy support for Intact iQ Web Services. However, this is limited to only the Scan module. This is only available to customers migrating from BlueScan (2018 v1.5 – 1.7) to inDocs.
Application License
An inScan(BlueScan), inAP(BlueOCR) or both licences will need to be purchased before the application can be installed.
Do I need to use labels with a inScan? Are they required on all documents and is there a recommended size?
Labels are only required when attempting to scan in third party documents, i.e. a suppliers invoice. The are not required for inAP or Intact iQ generated documents i.e. sales delivery note.
The default label form size is 76mm x 25mm and has been tested using Zebra brand label printers (ZD420).
Any changes to this label size will require further configuration to the iQ Printer form which may be quoted for.
What is the recommended scanner to use with inDocs (inScan).
inDocs does not communicate or link with any scanner. Instead, PDF documents are processed and read from a shared folder, or mailbox if using inAP.
Intact are unable to recommend any make or model of scanner. However, you are free to use any scanner you wish to use if it can support the following:
Intact cannot be held responsible for the reliability of any third-party hardware or software drivers even if it was supplied by Intact.
What is the recommended File Formats and File Structure for inDocs?
Intact will create the following directories and shares if we maintain the infrastructure. Otherwise, it will be the responsibility of the whomever supports the infrastructure.
inScan will read PDF, Compact PDF files that contain a bespoke QR code (see Compatibility section for more information regarding QR codes). inAP will read PDF and Compact PDF files.
A minimum of two shared folders will need to be created, one for the inDocs to monitir and the other for Intact iQ to store the files.
The two shared folders (and subsequent sub folders) should be called:
inDocs Worker Service – This is used to monitor incoming files. Two sub folders should be created:
inScanFiles – The destination for the processed documents, which Intact iQ system will access. You will be advised where the final share will be located unless you have specified your own.
How do I make it easier to identify scans from a branch?
Additional subfolders can be created in the inScanWatcher folder to help identify scans from different branches when dealing with issues in the inDocs web interface.
For example, if the are placed in a subfolder called Southampton, the folder name is recorded and shown under the Folder column in inDocs/Scan/Scans to help indentify where that scan came from. Therefore it is recommended to ensure that each branch’s scanner is pointing to their own subfolder.
Subfolders can be created in the BlueOCRWatcher folder to help identify documents from different companies when dealing with issues in the inDocs web interface.
The folders must be prefixed with the ERP address number i.e.
1-Southampton
2-Nottingham
For example, if a folder is called 1-Southampton and the user or Email Scraping is placing the files into that folder, the correct ERP dataset will be used, and folder name is recorded and shown under the Folder column in inDocs/OCR/Documents.