1 Workstation
The workstation is the classification pseudonym for one scanner addressed by a special TWAIN driver. Only one entry on a workstation must be characterized as default scanner. If there is no assignment document specified, all scans are done on this scanner. The characteristics duplex/document introduction are not used at present. Pushing "validate system" actionbutton it updates this view. All currently installed TWAIN drivers are enumerated.
2 Configuration
Under configuration different scanner configurations can be found.
Common -- >Name is a pseudonym for the configuration. The application has to call a certain configuration. By the call of DocSLN.exe this pseudonym has to be supplied as the 4th parameter.
In Scan-->Documentsource it is possible to choose the ADF or the flatbed to scan from. Using ADF, all inserted sheets will be attached to the document. Selecting flatbed, the number of scans has to be set in option Scan -- ># to scan so it is possible to create multi-part documents without an ADF. Between the scans only one keypress starts the next scan. Combining this feature with the PDF file format it almost replaces an ADF.
If image -- >integration is set to "embedding" the size is additionally affected by the chosen DPI resolution of the scan.
In file -- >Pagename/Attachmentname the prefix of each name can be set. DocSLN searches for documents with the same prefix set here before it attaches a new scan and increments the finishing number of the document for the new scan.
Dialogs -- >Twain turns the dialogue of your TWAIN driver on or off to be able to change unconsidered options (note: One Button Scan is not possible anymore if it is turned on).
Dialogs -- >Preview should not be used at this point.
For certain users a global configuration can be overwritten by a personal configuration. The adjustment possibilities of the global configuration are added by a user name for whom the configuration is valid.
3 Assignment
In the assignment document a certain announced user on a certain workstation is assigned to another but the default scanner. All scans initiated by that user on the specified workstation are done on this scanner.
4 Licenses
Registered licenses for different users or organizations can be configured here.
Configuration depending on settings in destination document
With Version 2.0 you can change nearly all configuration settings according to special field values in the document you want to scan to. E.g. say you have a form named invoices and you want to set the name of the attached document. Then you only have to insert a calculated text field "DocSLN_confDocName" and set the value of this field to the desired name or calculate it with a formula or LotusScript. This settings will override the settings of the chosen configuration document. In the following list you can see all possible fieldnames and its expected values
| Fieldname |
Value |
Description |
| DocSLN_confColor |
0
1
2
3 |
black/white
greyscale
256 colors
maximum colors |
| DocSLN_confDocName |
[string] |
Name of document |
| DocSLN_confEmbedRatio |
1-100[%] |
Scale of preview picture |
| DocSLN_confFBCount |
0
1 |
scan multiple pages
scan only one page |
| DocSLN_confFieldname |
[string] |
name of the richtext field the embedding should be done to |
| DocSLN_confFormat |
0
1
2
3
4 |
Bitmap (.bmp)
JPEG (.jpg)
Portable Document Format (.pdf)
Portable Network Graphic (.png)
Tagged Image File Format (.tif) |
| DocSLN_confIntegration |
0
1 |
attach
embedd |
| DocSLN_confJPGCompress |
1-100% |
compression ratio of JPEG image |
| DocSLN_confPageName |
[string] |
Name od Page |
| DocSLN_confPreview |
0
1 |
don't show preview dialog
show preview dialog |
| DocSLN_confResolution |
0
1
2
3
4
5 |
scan with 72 DPI
scan with 100 DPI
scan with 150 DPI
scan with 200 DPI
scan with 300 DPI
scan with 600 DPI |
| DocSLN_confTwainDLG |
0
1 |
don't show dialog of TWAIN driver
show dialog of TWAIN driver |
| DocSLN_confUseADF |
0
1 |
don't scan from document feeder
scan from document feeder |
| DocSLN_confUseDuplex |
0
1 |
don't scan in duplex mode
scan in duplex mode |
| DocSLN_confOCREnabled |
0
1 |
don't do OCR processing
do OCR processing after scan
|
| DocSLN_confOCRLanguage |
0
|
do OCR with english dictionary
|
| DocSLN_confOCRResultField |
[string] |
name of the richtext field the results of the OCR should be saved to
|
General
If DocSLN operates in server environment it is inevitable to put the configuration database down in the root directory of the database server otherwise it is not found.
DocSLN is completly backend orientated. Consider that the clumsy call of DocSLN.exe can result in save conflicts in the destination database. This is inevitable (you can keep on working while DocSLN scan is in progress) and can only be prevented by skillfully integration of the DocSLN call.