An Organisation needs a minimum of one Document type. To create them in Admin Panel, go to the ‘Document Types’ and create a new ‘Document Type’.
Screenshot above: typical setup of a Document Type
The settings are mostly optional for the purpose of the iConnector integration. The following is an explanation of some useful parameters related to the iConnector integration.
Unique (Document) ID
The Unique Id is generated and can be used to uniquely identify this Document Type.
Save Name Template
The Save Name Template can be used in the backend to define the filename that is used to store documents. Note: the creation of the file is controlled by the iConnector Server and depending on your implementation you can make use or completely ignore this field.
Document Format
The Document Format can be PDF, TIFF or JPG. If the Document Format is PDF or TIFF, all pages will be part of a single document that is uploaded. If the Document Format is JPG, each document page is uploaded separately. When documents are captured by Mobile Capture or the Mobile Capture SDK, it is advisable to select JPG for color images and TIF for black and white images.
Custom Configuration (Document type)
The Custom Configuration can be used to pass any data to the backend with the Metadata Upload; for example a JSON data structure with routing information specific to this Document Type. The value will not travel through the Web Browser / JavaScript, but is directly forwarded from the Admin Panel to the upload.
Get Field Metadata from Server
If Get Field Metadata From Server is switched to ON, the Field Definitions are retrieved from the backend. Normally, the Field Definitions are defined in the Admin Panel and stored in the CumulusPro Admin Panel Repository.
Validate on Submit
Validate On Submit is ON by default. This means that fields will only be validated when the document is uploaded. If Validate On Submit is OFF, fields will be validated as soon as a field value is changed. The following two functions are triggered if Validate On Submit is OFF each time a field value has changed: