74
Admin Guide – AutoStore 6.0
131
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Field
Name
Description
Name
The name of the form to be displayed on the Fujitsu scanner.
For example, if this form is used to send the scanned documents to the user’s home directory,
then you can name the form Scan to User’s Home Directory. This name must be unique
among the forms of the current level.
Single
Touch
Scan
Check this option if you do not want the user to enter any indexing data about the document.
By selecting this option, the scan will start immediately after the user presses the "form"
button on the device.
Scan
Settings
This table lists all the available Fujitsu Network Scanner scan settings. In the value
e
column
you can set default scan settings, which will be used if the user does not change the setting at
the device panel. Check Allow changes
s
checkbox on each setting to provide the user the
ability to change setting from the device panel. See Fujitsu Operator’s guide for detailed
description of each scan parameter.
•
Max Page Count per Batch - A batch can be from 1-999. Default is 0 which is equal to
999. If set to 2, the user can scan 2 pages at a time; if the user wants to continue
scanning he/she should click ‘Scan More’ to add to the existing batch.
•
Color Mode - Select from Auto, Color, Gray Scale (6010) or Black & White (6000), Black
& White (6010).
•
Paper Size (mm) - Select from the drop-down list. By selecting the custom option, you
can enter paper height and width.
•
Regular paper size - Width ranges from 1.0mm to 215.9mm (8.50 inch), Height
ranges from 1.0mm to 355.6mm (14.00 inch).
•
Long pages - Width ranges from 1.0mm to 215.9mm (8.50 inch), Height ranges
from 1.0mm to 863.6mm (34.00 inch).
•
Resolution - enter the resolution level that is desired.
•
Scan Mode - select from Simplex to scan the front side and select Duplex to scan front
and reverse sides.
•
File Format - Select from TIFF, MTIFF, JPEG (JPEG format is not compatible with Black
& White), and PDF
•
PDF Password - If PDF File Format is selected, you can check this box and provide a
password for opening the PDF file.
•
Searchable PDF - When the file format is PDF, the scanned data can be converted to a
searchable PDF. You can select which pages are to be made text searchable. This
functionality works with US and European devices.
•
Brightness - Select a level by moving the bar.
•
Contrast - Select a level by moving the bar.
•
Auto Page Orientation - Automatically rotates each scanned page that contains text
through 0,90, 180, or 270, so the text is upright.
•
Blank Page Skip - This feature removes the Blank Page from the scan job. This feature
comes handy when scanning both one-sided and two-sided documents in Duplex
mode. When this option is checked, the reverse sides (blank pages) are removed.
•
Multi-feed Detection - When two or more sheets are fed simultaneously into the
the
74
Admin Guide – AutoStore 6.0
132
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Field
Name
Description
scanner by the ADF, this setting detects multi-feeds.
.
Dynamic
Form
Enable Dynamic Form:
Standard behavior of a form can be modified by responding to events.
This checkbox allows the workflow server to load form snap-ins. Here are some examples of
what enabling dynamic forms can do:
•
Add and remove fields.
•
Change field contents (Example: load the contents of a list field from a database).
•
Validate field contents before the document is scanned into the server.
Snap-in path:
:
Path to the compiled snap-in (.net assembly) that contains the code to respond
to form and field events. If you have an existing snap-in you want to use, you can browse for
it using the ellipsis button next to the Snap-in path box.
Create/Edit Snap-in:
:
You can also click the Create/Edit Snap-in button to open a code editor
window with basic snap-in code. For details of the code editor window and the object model
used to respond to form and field events, please refer to the Fujitsu Capture Component Snap-
in documentation by clicking Help in the code editor window.
Source Path
: Path to the source code of the snap-in. This path is used by code editor to
compile the snap-in only during design time.
Form is Loaded
: Check this checkbox to cause the form to initiate an event every time the
user enters the form.
Form is Submitted
: Select this checkbox to make the form to initiate an event every time the
user presses Scan
n
button in this form.
Fields Tab
Configure the indexing fields that will be presented to user. Add fields by clicking on the New field
button appearing as the first column header and labeled with “N”. Once you have added the first row,
you can tab through to get additional fields added.
•
Name -
The field name should be unique among the other fields within this form.
•
Display -
The text which is displayed above the field at the device panel.
•
Size Type -
A field can be full sized or half sized. A full sized field takes the entire space form the
left margin to the right margin on the scanner panel, a half sized field takes only half the space
between the margins.
•
Type -
A field type represents the format by which data is collected at the device panel.
Regardless of field type, the result will be in text format. The following field types are supported:
•
Text
- allows a user to enter un-formatted text.
•
Numeric
- allows a user to enter numbers (with or without decimal point).
•
Checkbox
- allows a user to set yes/no or true/false values by pressing a button.
•
DateTime
- allows a user to enter date and time information in different formats
61
Admin Guide – AutoStore 6.0
133
Version 1.2
Copyright 2012 Notable Solutions, Inc.
•
List
- allows to present users with a list of choices from which users select the desired item.
Use this field type if you want a text field with auto complete capabilities. If a list of choices
is too long, the list can be made searchable.
•
AddressBook
- allows a user to perform a search in LDAP directory.
•
Button
- allows a user to raise an event on server side.
•
Tree
- allows to present users with a list of choices in a tree from which users select the
desired item.
•
Required Field -
If checked, the user must enter the field at the scanner panel.
•
Notify Server -
If checked, this field triggers an event when the value of the field changes. You
can respond to this event in the snap-in that was configured for the dynamic form section in the
General tab. For details on how to respond to form and field events, refer to the Fujitsu Capture
Component Snap-in documentation.
•
Properties -
Allows editing additional properties of the field type.
Components Tab
Configure the component for this form by clicking the Properties button (rightmost column on each
row). The configuration window for the component will be displayed. Refer to the help for the
component for instructions to configure.
Appearance Tab
Field Name
Description
Display Text Enter the form name as you want it to display on the scanner panel.
Button
Images
•
Normal
- browse to the image that you want to be displayed for this form.
•
Focused
- browse to the image that you want to be displayed upon pressing this
form.
•
Pressed
- browse to the image that you want to be displayed after the form is
selected.
Text Position The position of the text on the button can be moved from 0-100 pixels.
s.
Edit
Select the Group, Menu or Form that you want to update and click Edit.
Remove
Select the Group, Menu or Form that you want to delete and click Remove.
Preferences Tab
In this tab, you can specify the location where the server will store the program files for the job that is
being processed.
37
Admin Guide – AutoStore 6.0
134
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Port Number
Enter the port number used by the scanner to communicate with the Server. The device must be
configured to use the same port number to communicate with the server. If the device is having
problems communicating with the server check the port settings on the server to make sure they match
the device port number. Also make sure there are no firewall equipment blocking the specified port.
Home Folder
The root directory where the server creates all temporary directories and files necessary for controlling
device related traffic. The server must have proper permission to write to this directory.
Encrypt all connections
Check this option to encrypt all communication between the device and workflow server.
Keep
Processed Files
- Select Processed files to keep a copy of all files that are processed without errors.
Enter the directory where these files will be kept.
Warning
- if this option is enabled, a copy of every file that has been routed successfully is saved in the
Processed Files directory. Make sure that proper disk storage is allocated when using this option
Rejected Files
- Select Rejected Files to keep a copy of all files that failed to be process entirely. Enter
the directory where these files will be kept.
Important Note:
The service account for the service must have write permissions on the Processed Files
and Rejected Files directories.
Server Timeouts
Form Inactivity Timer
- The amount of time in minutes that a form can be inactive before the
corresponding server object is deleted.
For example if the user enters a form and doesn't press any other button within 30 minutes (default
Form Inactivity Timer), the form on the server side becomes unavailable and as a result the following
message is displayed to the user: ‘Server object does not exist’.
When a user makes additional calls to the form on the server side (by manipulating the fields that have
server side events or by pressing Scan setting button), the Form Inactivity Timer is reset to 30 minutes
again from the moment the call takes place.
49
Admin Guide – AutoStore 6.0
135
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Note: If you expect high volumes of scanning to occur in one scan job, it is recommended to adjust this
parameter to be set to a value larger than maximum scan time.
Authentication Tab
Contents of this tab do not apply to fi-6000 NS devices, as authentication is not supported by this model.
Setup the authentication attributes for fi-6010 NS devices in this tab.
Authentication Type
Select the authentication method you want to use. The following options are:
•
Standard
- Two options are available:
•
Windows bind (selected by default) - if authentication is within the same domain, the
Server or LDAP path
can be left blank.
•
Fast Bind - If disabled, the Active Directory Server returns all the user attributes to
the workflow server.
•
Server Bind - If disabled, the Active Directory Server tries to connect to DNS server
to resolve the IP address of the workflow server.
•
Use SSL - If disabled, the connection between LDAP and Workflow server is not
encrypted. To use SSL option you must have a server certificate for the ADAM
service
. If verifying against another domain, enter the server name and port
number (i.e. LDAP://server name,5001).
Click Test
to verify that the username created on the server authenticates
successfully.
•
Simple bind - Enter the Server or LDAP path
(i.e. LDAP://server name,5000)
•
Fast Bind - If disabled, the Active Directory Server returns all the user attributes to
the workflow server.
•
Server Bind - If disabled, the Active Directory Server tries to connect to DNS server
to resolve the IP address of the workflow server.
•
Use SSL - If disabled, the connection between LDAP and Workflow server is not
encrypted. To use SSL option you must have a server certificate for the ADAM
service
. If verifying against another domain, enter the server name and port
number (i.e. LDAP://server name,5001).
Please refer to Microsoft web site to learn about setting the LDAP Bind options.
45
Admin Guide – AutoStore 6.0
136
Version 1.2
Copyright 2012 Notable Solutions, Inc.
•
Netware
- This will prompt the user for their NDS context and tree. Enter the default NDS tree in
the NDS Tree box under Netware. Enter the default Novell context in the NDS Context box under
Netware. Note that if the device is configured to use an Authentication Server with the
authentication type being NDS, then the credentials provided will be used by workflow server. If
the Authentication Type of the device is other than NDS, then in addition to workflow server login
screen, the device’s authentication screen is also displayed.
•
Custom
- The administrator has full control over the prompts that will be presented to the user as
well as how the prompts are validated.
Snap-in path
- Path to the compiled snap-in (.net assembly) that contains the custom authentication
code. If you have an existing snap-in you want to use, you can browse for it using the ellipsis button next
to the Snap-in path box.
Create/Edit Snap-in
- You can also click the Create/Edit Snap-in button to open a code editor window
with basic snap-in code. For details of the code editor window and the object model, please refer to the
Fujitsu Capture Component Snap-in documentation by clicking Help in the code editor window.
A sample custom script is available with this component.
Source Path
- Path to the source code of the snap-in. This path is used by code editor to compile the
snap-in only during design time.
Use LDAP search to retrieve email
- Select this checkbox to look up the email address and other
attributes for the authenticated user. Note that when windows authentication is selected, the email
address is retrieved automatically as part of the authentication and as a result an LDAP search is not
required if only the email address is needed.
To Configure the LDAP server, enter the following information:
•
Search Root - Enter the search root folder you want to begin searching against. If this field is left
blank, the search starts at the LDAP default directory.
•
Authentication - select the required authentication type and provide the user credentials.
•
Directory Search - Search the entries in the address book directory services database.
•
Test Look-up - To test the search settings, enter a sample user name in the Username box and
click Test
.
34
Admin Guide – AutoStore 6.0
137
Version 1.2
Copyright 2012 Notable Solutions, Inc.
RRT Format Tab
This tab allows you to configure the format of RRTs that represent date and time.
# of ‘Received Time’ RRTs
- Use this field to specify the number of RRTs that represent Received Time.
For example if you set this value to 2, then 2 sets of RRTs (representing the Scan Time Stamp) will be
available for use.
The grid allows you to specify which time format a particular date-time RRT will have.
The Time Stamp list on the right shows some examples of date time formats. You can drag & drop to fill
out format strings or press "<" button.
Full description of format strings can be found in Custom DateTime format strings
and Standard
DateTime format Strings.
File Size Format
- Use this field to specify the unit in which File Size RRT will be represented.
Obtain Device Host Name
- Check this box to enable the DeviceHostName RRT to return the host name
of the device. This option comes handy in environments where Host Name resolution is slow. In such
environments, you may want to leave this checkbox unchecked.
Runtime Replacement Tags
What are RRTs?
Runtime Replacement Tags (RRT) are tags placed within the configuration file for replacement by meta-
data values during execution time. At runtime (when a component is executed within the application),
each component is responsible for searching all items within the configuration memory structure and
replacing their assigned RRTs with actual meta-data values.
How does it work?
When you create a process that consists of a series of components, the components are executed in
order from left to right (Capture to Route). Each component, prior to its termination, searches all
configuration entries and replaces all its own RRTs with actual meta-data values. As an example, the
XML Knowledge Package Loader component will search for RRT’s starting with “~ASX::” and replaces
them with actual metadata values.
31
Admin Guide – AutoStore 6.0
138
Version 1.2
Copyright 2012 Notable Solutions, Inc.
The order of execution of components within a process is significant. Due to the component execution
order (Capture to Route), RRT’s owned by components that appear later in a process cannot be placed
within components that appear earlier in a process. As an example, placement of Folder Store
component RRT’s within a Capture component such as Poll Directory is invalid and will not be replaced
at runtime.
RRT naming convention
The figure below provides you with an illustration of the RRT definition. Each part of the RRT is designed
to create a standard field tag replacement that can be expanded to all components designed and
developed within the component framework.
Important Note:
RRT’s are case sensitive. You must follow the proper case for all RRTs. You cannot
introduce space characters in between the RRT segments.
The table below provides details on each segment of the RRT:
Segment
Name
Description
Markers
Special characters used to mark the beginning and the ending of each RRT. The “~” is
used to mark each end. Note that you cannot use the same character anywhere within
the other parts of the RRT. Having “~” appear as a value of a special field is not
supported with this new RRT design.
RRT ID
Special three characters identifying the component owning the RRT and responsible for
replacing the tags with the actual values.
Separators
Double colon “::” characters used to separate the Component RRT ID from the actual
Replacement Tag Name. Double colon is now reserved and cannot be used within other
51
Admin Guide – AutoStore 6.0
139
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Segment
Name
Description
parts of the RRT. Example of an illegal use of :: is “~MYC::Invoice::Number~” where the
double colon is repeated within the replacement tag name
Replacement
Tag Name
The Replacement Tag Name or RTN can be the name of the metadata collected from a
content source (e.g., device, etc.), or a metadata generated by the component itself
(e.g., XML data field, etc.). The following types of RTN are currently supported:
i.
Reserved (RRTN)
– Each component is allowed to create and maintain a set of
reserved RTN or RRTN. Within the boundaries of each component reserved names
have special meaning. Each component defines a list of RRTNs.
ii.
Field (FRTN)
- Some components that support field names allow the fields to be
referenced using the special enclosure character: “%”. An example of field name
used within RRT is:
~MYC::%Invoice Number%~
This example allows replacement for a field called “Invoice Number” within the
MYC component with the value of the field Invoice Number.
iii.
Special Sets (SSRTN)
- These are special set of characters providing you with
useful information on the job such as document date, document time, etc. It’s
important to note that not all components support the SSRTN values. Look in
documentation for each component to find the components that do support
SSRTNs
Fujitsu Component RRTs
Component RRT ID
The RRT ID for this component is FUJ
.
Reserved Replacement Tag Names (RRTN)
The following table describes the reserved RTN values for this component:
Name
Description
FileFormat
Format of the files in a batch (TIFF, MTIFF, JPEG (JPEG format is not compatible with
Black & White), PDF). A batch cannot contain files of different format.
PageCount
Number of Pages received in a batch. A batch can contain either several single page
files or one multi-page file. In both cases Page count returns a number of pages in a
batch. Therefore if Number of files is greater that 1, then PageCount = Number of files.
NumberofFiles Number of Files received in a batch. If Number of Files > 1 then Page count = Number
r
77
Admin Guide – AutoStore 6.0
140
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Name
Description
of files
FileSize
File Size in Byte, KByte, MByte, or GByte. The unit depends on the File Size Format
field.
FormName
The name of the form selected at network scanner
FormID
The guid of the form selected at network scanner
BatchID
The guid of the received batch
SenderUsername The authenticated users domain name if Authentication has been turned on for the
device.
SenderEmail
The authenticated users display name if Authentication has been turned on for the
MFP device.
DeviceIP
IP Address of the device from which a batch has been received.
DeviceHostName The domain name of the device from which a batch has been received. If Obtain
tain
Device Host Name
checkbox is unchecked, this RRT returns an empty string.
ColorMode
Color or Black and White document (Auto, Color, Gray Scale (6010) or Black & White
(6000), Black & White (6010)).
ResolutionType Type of resolution (150dpi, 200dpi, 300dpi, 600dpi)
PaperSize
Paper size of the scanned document
ReceivedTimeX The time stamp at which the batch was received by the workflow server. Please refer
r
to RRT Format Tab
b
for details.
Field Replacement Tag Names (FRTN)
This component does not support FRTNs.
Special Set Replacement Tag Names (SSRTN)
This component does not support SSTNs.
Troubleshooting Tips
Problem
Possible Cause
Solution
Error Message: This key was
not present in the directory
European Mode : The
Administrator modified
the configuration and the
user is at the Form level
Cancel out of the Default form and go up two
levels and try to access the Default Form again.
The error won’t be listed anymore.
Searchable PDF functionality
doesn’t work
Searchable PDF
functionality works only
with the US device and
Europe device.
US Device and Europe device. This option is not
available with non-OCR scanners.
List Values are getting
appended and repeat itself
‘Allow to edit value on
the device side’ is
checked
If ‘Allow to edit value on the device side’ is
unchecked, the values if selected once will be
unique.
Error Message: Expected
shared key from server
‘Encrypt connection’
unchecked on device but
If ‘Encrypt connection’ is checked on device then
turn the ‘Encrypt connection’ on device to YES.
Documents you may be interested
Documents you may be interested
