61
Admin Guide – AutoStore 6.0
463
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Use a Send to Email form when you need to send the document to an email destination. A Send to Email
form is commonly used in conjunction with the Send to SMTP and Send to Exchange Route components.
To add a Send to Email form, perform the following steps:
1.
Go to the Groups
tab. Select the group where you want to add the form to and click Add Form
>
Send to Email Form
.
2.
Configure the name and scan settings for the form in the same way as for a basic form
.
3.
Go to the Send to Email fields tab, and choose from the following options:
•
Select the Do not show a From field
. This will use the device logged in user's email address
check box to omit the ”FROM” field. This is usually selected if you plan to use the logged in
user email’s address.
•
Select the Show CC Field
check box to show the ”CC” field in which the user can specify a
secondary list of people that will receive the message.
•
Select the Show BCC Field
check box to show the ”BCC” field in which the user can specify
people that will receive the message secretly.
•
Select the Global Address List
check box under Contacts Search Locations to allow the
users to search the Global Address List for addresses that can be added to the To, CC and
BCC fields. In the Display As
box type the display value for this search option.
Note that the Global Address List that will be searched will be decided based on following
criteria:
•
If Windows Authentication is used, then the search will be performed on the Global
Address List associated to the device logged in user.
•
If Custom Authentication is used and the authentication code populates the
Username and Domain fields, then the search will be performed on the Global
Address List associated to the device logged in user.
•
If there is no logged in user then the search will be performed on the Global Address
List associated to the service account for the AutoStore service.
Regardless of which Global Address List is used, the service account for the AutoStore service
must have enough permissions to perform this search.
•
Select the Exchange Contacts
check box under the Contacts Search Locations to allow
users to search their Microsoft Exchange contacts folder for addresses that can be added
to the To, CC and BCC fields. In the Display As
box type the display value for this search
option.
•
Enter the full address of the Exchange Server (IP address or host name). If the
address is unknown, contact your system administrator.
76
Admin Guide – AutoStore 6.0
464
Version 1.2
Copyright 2012 Notable Solutions, Inc.
•
If a secure socket layer (SSL) connection should be used to connect to the Exchange
Server, select the Use SSL
checkbox.
•
Select the LDAP Server
check box under Contacts Search Locations to allow the users to
search an LDAP Server for addresses that can be added to the To, CC and BCC fields.
•
In the Display As
box type the display value for this search option.
•
In the LDAP Server
box type the address or host name of the LDAP server.
•
In the Search Root DN
field type the distinguished name for the node where the
search should start. For example: DC=Sales, DC=MyCompany, DC=com. If this field
is left empty then the starting point of the search will be the root of the directory
tree.
•
In the Email Address field
type the name of the LDAP attribute that represents the
email address.
•
In the Name Field
type the name of the LDAP attribute that represents the name of
the user.
•
Select the Login as Anonymous
check box to establish an anonymous connection to
the LDAP server.
•
Select the Login with following credentials
check box to log in to the LDAP server
with the specified Username and Password.
Note that if the LDAP server is an Active Directory server, then NTLM authentication will be used
•
Set the Maximum number of contact to return
field to the number of contacts that the
search will return.
Adding a Send to Folder Form
Use a Send to Folder form when you need to send the document to a folder destination. A Send to
Folder form is commonly used in conjunction with the Send to Folder and Send to Folder eConnector
components.
To add a Send to Folder form, do the following:
1.
Go to the Groups
tab. Select the group where you want to add the form to and click Add Form
>
Send to Folder Form
.
2.
Configure the name and scan settings for the form in the same way as for a basic form
.
3.
Go to the Send to Folder
tab and configure the
•
In the Base Directory
box enter the location of the directory that the user can browse to
select the destination of the document.
•
In the Default Document Name
check box, type the default value that will be used for the
document name field.
4.
Configure the components in the same way as for a basic form
.
5.
Click OK
to save the form.
49
Admin Guide – AutoStore 6.0
465
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Form Templates
To save an existing form as a template, do the following:
•
Go to the Groups
tab and right-click the form you want to save.
•
Select Save as Template.
•
Enter the location where you want to save the template.
•
If dynamic form is enabled then you have the option of copying the associated .Net script to the
same location where the template will be saved.
•
Select Save.
•
If the operation is successful you will see a message indicating that the template was saved.
To create a form from a template, do the following:
•
Go to the Groups
tab. Click on the group where you want to add the form.
•
Click Add Form > Load From template.
•
In the Template file
box, enter the location of the template. This must be a form template saved
previously with Save as Template
.
•
In the Dynamic Form script file
box, enter the location of the .Net script file associated to the
template.
•
Click Create.
Editing and Removing Forms
To edit a form, double click the form name in the Groups
tab or select the form name and click edit.
To remove a form, select the form name in the Groups
tab and click Remove
.
Runtime Replacement Tags (RRT)
What are RRTs?
Runtime Replacement Tags (RRT) are tags placed within the configuration file for replacement by
metadata 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 metadata values.
26
Admin Guide – AutoStore 6.0
466
Version 1.2
Copyright 2012 Notable Solutions, Inc.
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 metadata values.
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
49
Admin Guide – AutoStore 6.0
467
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Segment
Name
Description
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
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
Sharp MFP (OSA) Component RRT
Component RRT ID
The RRT ID for this component is SH2
.
Reserved Replacement Tag Names (RRTN)
The following table describes the reserved RTN values for this component:
76
Admin Guide – AutoStore 6.0
468
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Name
Description
FormName
Name of the form.
Sender
The user name of the authenticated user that is submitting document(s) is returned. If
authentication is set to None
e
and CAC is not used, this will return blank. If CAC is being
used, the user credentials for the logged in CAC user will be returned.
SenderEmail
The email of the user. If authentication is set to None
e
and CAC is not used, this will
return blank. If CAC is being used, the email address for the logged in CAC user will be
returned.
SenderDomain The authenticated user’s domain name. This is available Windows authentication has
has
been turned on for the MFP device or if Custom authentication is used and the
associated .Net script populates the Domain
n
property of the UserInfo
o
object.
IP
The IP address of the MFP device.
HostName
The resolved host name of the MFP device.
ServerIP
The IP address of the Sharp OSA Web Connector server
ServerHostName The Host Name of the Sharp OSA Web Connector server
r
PageCount
Number of pages of the scanned file.
Format
Format of the scanned file. Possible values are:
•
TIFF
•
PDF
•
JPEG
•
EncryptedPDF
FileSize
Size in bytes of the scanned file.
Note:
When CAC is used, Sender, SenderEmail
and SenderDomain
will be set according to credentials
on CAC. When CAC is used with the following authentication settings:
•
If set to None
, Sender, SenderEmail and SenderDomain will be set according to device
information for the logged in CAC user.
•
If set to Windows
, Sender, SenderEmail and SenderDomain will be set according to device and
server authentication information for logged in CAC users who have Windows logins. Device
information has priority for these three reserved RTNs.
•
If set to Netware
, Sender, SenderEmail and SenderDomain will be set according to Netware
authentication. Device information will be discarded.
•
If set to Custom Script
, Sender, SenderEmail and SenderDomain will be set according to device
and custom script information for the logged in CAC users that are verifiable through the custom
script. Device information has priority for these three reserved RTNs.
Field Replacement Tag Names (FRTN)
This component supports FRTNs and replacement of field names generated from the MFP devices. The
following example provides some sample usage for your reference:
51
Admin Guide – AutoStore 6.0
469
Version 1.2
Copyright 2012 Notable Solutions, Inc.
~SH2::%Client ID%~
- replaced by ”Company” if the user types in ”Company” for the field name called
"Client ID”.
User attributes Replacement Tag Names (URTN)
This component supports URTNs and replacement of user attributes specific to the authentication
method used. The following example provides some sample usage for your reference:
If Custom authentication is used and there is a user attribute named ”Display-name” with the value John
Doe then the RRT will look like:
~SH2::User,%FullName%~
- this RRT will be replaced by ”John Doe”.
Note:
When CAC is used, all attributes will be pulled from the device and every attribute name will be
pre-fixed with the text "MFPUserAttr-
" to distinguish normal user attributes. For example, if CAC
provides attribute "Display-name", the CAC user's attribute name for this will appear as "MFPUserAttr-
Display-name". The RRT will look like:
~SH2::User,%MFPUserAttr-Display-name%~
- This RRT will be replaced by "John Doe" with the logged
in user's display name from CAC.
Special Set Replacement Tag Names (SSRTN)
This component supports all the Date/Time tag names listed below:
Name
Description
%a Abbreviated weekday name
%A Full weekday name
%b Abbreviated month name
%B Full month name
%d Day of month as decimal number (01 – 31)
31)
%H Hour in 24-hour format (00 – 23)
23)
%I Hour in 12-hour format (01 – 12)
12)
%j Day of year as decimal number (001 – 366)
66)
%m Month as decimal number (01 – 12)
12)
%M Minute as decimal number (00 – 59)
59)
%p Current locale’s A.M./P.M. indicator for 12-hour clock
ck
%S Second as decimal number (00 – 59)
59)
%U Week of year as decimal number, with Sunday as first day of week (00 – 53)
53)
%w Weekday as decimal number (0 – 6; Sunday is 0)
0)
36
Admin Guide – AutoStore 6.0
470
Version 1.2
Copyright 2012 Notable Solutions, Inc.
Name
Description
%W Week of year as decimal number, with Monday as first day of week (00 – 53)
53)
%y Year without century, as decimal number (00 – 99)
99)
%Y Year with century, as decimal number
r
Device Setup & Configuration
The connection between the device and AutoStore is done through a web application called Sharp OSA
Web Connector.
To connect a Sharp Device to AutoStore, do the following:
Verify the pre-requisites for installing the Sharp OSA Web Connector.
Install the Sharp OSA Web Connector.
Configure the device to connect to the Sharp OSA Web Connector
.
Note that when Sharp OSA Web Connector has been installed, you can connect multiple devices to the
Sharp OSA Web Connector. Alternately, you can install additional web connectors for the case when you
have a large number of devices.
Pre-Requisites
Sharp OSA Web Connector Prerequisites
•
Internet Information Server 5.x, 6.x or 7.x with .Net Framework 2.0 installed.
•
FTP Server
Note that when HTTP is the only transfer protocol used, FTP server does not need to be installed.
But for devices that do not support HTTP repositories, Local FTP can be used as an alternate
repository. Regardless of the situation, it is advised that FTP server be installed.
Device Prerequisites
The device must be Sharp OSA Enabled. Refer to the AutoStore website
for information on devices that
currently support OSA.
Documents you may be interested
Documents you may be interested
