Eclipse Signature Capture Suite Rel. 8.6.4 (Eterm)
2 © 2008 Activant Solutions Inc. All rights reserved.
Signature Capture and Document Imaging Guidelines
In order to attach signatures to transactions using the Signature Capture Suite companion
products, you need to define signature storage locations on the network host. Use the Document
Imaging companion product to define these storage locations by setting up storage IDs and
indexing profiles.
Storage IDs define where certain file types, such as signatures, are stored. Indexing profiles
define how storage IDs are organized. In short, storage IDs and indexing profiles are electronic
filing cabinets.
For example:
You currently have a filing cabinet in your office holding all signed manifests. Each drawer is
designated for a different customer. Within each customer's drawer are files for every month of
the year, holding the signed manifests for the respective month. With the Document Imaging and
Signature Capture Suite companion products, the network host replaces your filing cabinet, the
indexing profiles replace each customer's drawer, and the storage IDs replace the files for each
month of the year.
For information on how to define storage IDs and indexing profiles, see Defining Document
Storage Locations.
Additional Document Imaging Settings for EPad
In addition to setting up storage IDs and indexing profiles on the network host, you can set up
temporary storage locations for signatures captured with EPad.
When you capture signatures using EPad, you commonly do so from counter terminals at your
warehouse branches. If you capture large amounts of signatures at a branch, set the system to
temporarily store these signatures on the counter terminals until you can copy them to the
network host for permanent storage. You must define the temporary signature storage locations
on each terminal used for EPad.
Note: Set up temporary storage locations only for terminals that collect a large
volume of signatures on a daily basis. If you do not capture a large volume
of signatures at a terminal on a daily basis, you can copy signatures directly
to the host without temporarily storing them.
Copy signatures from the terminals to the network host by running a replication. After defining
both host and temporary storage locations, set up a replication schedule to indicate how often
stored signatures are copied. For example, schedule a replication to run nightly in order to copy
all collected signatures from the day.
In addition to storing and replicating signatures, you need to maintain your warehouse terminals.
To keep each terminal from becoming overloaded with the temporarily stored signatures, define
how long to keep the signatures stored on the terminals before the system deletes them. For each
temporary storage location, you can define the number of days to keep signatures before deleting
them, as well as schedule a routine purge of the signatures. Just make sure to replicate the
