92
Admin Guide – AutoStore 6.0
341
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Field
Name
Description
•
Edge Erase (Top, Left, Right, Bottom)
– Specifies the amount of image data to erase at
t
either the top, left, right or bottom of the original image window. This option allows
the user to eliminate unwanted marks along the edge of the target document.
•
Scan Preview (hard drive)
– When enabled, the user will see a thumbnail of the image
scanned. With flatbed devices, a thumbnail will be displayed for each page scanned.
For ADF devices, a thumbnail will be displayed for only the first page.
•
Background Removal
– Specify the background removal level of a scan. Higher values
change lighter shades to white. A value of zero (0) is neutral.
•
Color Dropout (2.0)
– Turns the selected color to white in order to aid with forms
processing functions. Also turns dark marks and notations to black. This setting only
affects grayscale jobs.
•
Color Dropout Threshold (2.0)
– Specify the threshold for shades to become either
black or white. By increasing the threshold, darker shades become black while lighter
shades become white. By decreasing the threshold, darker shades become white
while lighter shades become black.
•
Contrast
– Specify the contrast level of the scan. Higher values results in more
contrast.
•
JPEG Quality
– The amount of image quality and detail to be retained by the JPEG
compression algorithm.
•
Source
– Specify the scanning source.
•
Negative Image (2.0)
– Specify whether the image produced by the scan is to be
inverted.
•
Shadow Detail
– Specifies the black-point level of the scan.
•
Scan Edge to Edge
– Specify whether target document will be scanned from edge to
edge or only within the specified margins.
•
Sharpness
– Specify the sharpness of the image. Increasing the value may be useful
for blurry text. Decreasing the value may be useful for moiré patterns.
•
Action Button Text (2.0)
– Specify the text to be displayed on the “Action” button. If
no text is specified, the default text for the action is used.
•
One Page Copy
– Specify whether scanner scans an entire job at one time or one page.
•
Pdf Password (1.2 on X940e, X945e)
– User can specify a password to use for secure
PDF. File Format
must be set to SECURE PDF
. This setting does not apply to
Framework versions 2.x.
•
Pdf Algorithm (1.2 on X940e, X945e)
– Specify the encryption algorithm to use with
secure PDF. File Format
must be set to SECURE PDF. With Framework versions 2.x,
the encryption algorithm is selected automatically.
•
Restart Job (1.2 and older)
– Specify whether the job must be resubmitted when the
job is cancelled for any reason. This setting does not apply to Framework versions 2.x.
For Framework versions 2.x, the user can use Scanner Jam Recovery
instead of this
setting.
•
Scan Recovery (1.2 and older)
– Specify whether a job resumes immediately after the
MFP devices jams. Successfully scanned pages will be preserved and scanning will
resume after the last good page. If setting is not selected, the job will not resume after
the MFP device jam.
74
Admin Guide – AutoStore 6.0
342
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Field
Name
Description
•
Scanner Jam Recovery (2.0)
– Specify whether the full or partial job must be
e
resubmitted when the job is cancelled for any reason. If Page-level
is selected and the
entire job must be restarted, then the job must be resubmitted. The Page-level
setting
saves all properly scanned pages but all pages after the first jammed must be
resubmitted.
Dynamic
Form
Enable Dynamic Form:
Standard behavior of a form can be modified by responding to events.
This checkbox allows the workflow sever 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.
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.
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 Lexmark Capture Component
Snap-in documentation by clicking Help in the code editor window.
Raise event when Form is Loaded:
Check this checkbox to cause the form to initiate an event
every time the user enters the form.
Raise event when 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.
•
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.
•
Integer
– allows a user to enter integers (whole numbers only).
•
Numeric
- allows a user to enter numbers (with or without decimal point).
53
Admin Guide – AutoStore 6.0
343
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.
•
Tree
– Presents a list of choices in tree form.
•
N (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 Lexmark
Capture Component Snap-in documentation.
•
P (Properties) -
Allows a user to edit additional properties of the field type.
Components Tab
Configure the component for this form by clicking the Properties button (right-most 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
Description The name that will be displayed on the MFP for this form.
Scan Button
Label
Check this option if you do not want the user to enter any indexing data about the
document. By selecting this option, the scan operation will start immediately after the
user presses the "form" button on the device.
Button
Images -
Normal
Enter the location of the image that will be displayed on the MFP panel (this image will be
the icon that is displayed prior to the user pressing that icon on the MFP panel). If no
image is selected, the default image on the MFP panel will be used.
Button
Images -
Pressed
Enter the location of the image that will be displayed on the device once the user has
pressed the icon (this image will be displayed for a corresponding icon once the user has
selected that icon; i.e. the image used will change from the one specified in the Normal
field to the one specified in the Pressed
field). If no image is selected, the default image
on the MFP panel will be used.
Shared Form
A shared form is exactly the same as a regular form with the exception that any specific shared form can
be referenced multiple times. This option allows the user to create one shared form and reference the
same form in another group or menu.
42
Admin Guide – AutoStore 6.0
344
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Field
Name
Description
Add
Select Add to create and customize a shared form. For information on creating and
customizing a form, see the Form
m
help page.
Remove Select Remove to delete a shared form.
.
Edit
Select Edit to edit and customize a shared form.
Ref
Select Ref to display information on the number of references a shared form may have. Keep
in mind, that a shared form may not have any references (i.e. a shared form can be created but
does not have to be placed within a group or menu).
The different groups or menus that reference a shared form can be managed by selecting Ref.
Edit
Select the Group, Menu, Form or Shared Form that you want to update and click Edit.
Remove
Select the Group, Menu, Form or Shared 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.
Server
Specify the web server that the scanned document image(s) and associated metadata should be
transferred via HTTP or SSL. This allows a web application/service to directly receive the data rather than
watching for a file to appear at a predetermined location.
Server URL
: The http URL from which the data will be retrieved by the workflow.
Server SSL URL
: The https (SSL) URL from which the data will be retrieved by the workflow.
SSL Certificate
: The certificate by which data can be retrieved by the workflow server, when using https
(SSL).
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.
C# Word - Word Conversion in C#.NET Word documents in .NET class applications independently, without using other external third-party dependencies like Adobe Acrobat. Word to PDF Conversion.
how to delete text in pdf preview; how to delete text from pdf document
34
Admin Guide – AutoStore 6.0
345
Version 1.2
Copyright 2012 Notable Solutions, Inc.
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
– Selected Rejected Files to keep a copy of all files that failed to be processed. Enter the
directory where these files will be kept.
Note
: The service account for the service must have write permissions on the Processed Files and
Rejected Files directories.
RRT Format Tab
This tab allows you to configure the format of RRTs that represent date and time.
# of ‘Received Time’ RRT's
- 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
.
File Size Format - Use this field to specify the unit in which File Size RRT will be represented.
Authentication Tab
In this tab you can set up the authentication parameters.
Authentication Type
Select the authentication method you want to use. The following options are:
VB.NET PDF: How to Create Watermark on PDF Document within create a watermark that consists of text or image (such And with our PDF Watermark Creator, users need no external application plugin, like Adobe Acrobat.
how to remove highlighted text in pdf; how to edit and delete text in pdf file
58
Admin Guide – AutoStore 6.0
346
Version 1.2
Copyright 2012 Notable Solutions, Inc.
•
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.
•
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.
41
Admin Guide – AutoStore 6.0
347
Version 1.2
Copyright 2012 Notable Solutions, Inc.
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
.
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
348
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
54
Admin Guide – AutoStore 6.0
349
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
Lexmark Capture Component RRTs
Component RRT ID
The RRT ID for this component is DS2
.
Reserved Replacement Tag Names (RRTN)
The following table describes the reserved RTN values for this component:
Name
Description
Number of Files
Number of Documents received in a batch.
File Size
Size of the received file.
Form ID
The GUID of the form selected at the network scanner.
Batch ID
The GUID of the received batch.
Sender Username
The name of the user authenticated on the device.
Sender E-mail
The email address of the user authenticated on the device.
18
Admin Guide – AutoStore 6.0
350
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Name
Description
Device IP
IP Address of the device from which a batch has been received
Device Host Name
Host Name of the device from which a batch has been received
Device Domain Name The domain name of the device from which a batch has been received
Device MAC Address The network MAC address (UAA) of the device
Device Model Number The model name of the printer.
Device Serial Number The serial name of the device.
Field Replacement Tag Names (FRTN)
This component does not support FRTNs.
Special Set Replacement Tag Names (SSRTN)
This component does not support SSTNs.
Documents you may be interested
Documents you may be interested
