Upload

EzeScan has an optional Upload module built into the EzeScan product. The EzeScan Upload option can be licensed as an option at purchase time, or at a later stage as a module upgrade.
The purpose of the Upload module is to take the output created by the KFI module (images and indexes) and Upload it to one of its supported systems.

Available Upload Connectors

The Upload module currently supports the following connector locations:

• Aconex
• Box
• Civica Authority Purchases
• CSV Creator
• DocuShare and DocuShare Flex
• DocuWare
• Dropbox
• EzeScan Archiver
• File System
• Financial Edge NXT
• FTP
• iManage Work
• IMAP
• Infor Pathway
• InfoRouter (Active Innovations)
• Laserfiche
• MAGIQ Documents
• M-Files
• MicroFocus Content Manager (TRIM)
• MicroSoft Office 365 Outlook
• MicroSoft OneDrive
• MYOB AccountRight 2013.5 and above
  • • Purchases
    • Receive Money
    • Sales
    • Spend Money
• Objective ECM
• ODBC (Databases)
• Open Text eDOCS 5 and eDocs 6
• Open Text Content Server
• PaperSave
• Raiser's Edge (and NXT)
  • • Constituent
    • Gift Batch
• SFTP
• SharePoint (Microsoft)
  • • 2013
    • 2016
• SMTP
• TechnologyOne ECM (CMIS and DAS)
• TechnologyOne Financials
• Therefore
• WebDAV (Compliant Systems)
• Xero

The following sections take you through building a simple Upload definition using the Admin Tool and then running that Upload definition as a production job.

1. You must be licensed to use the EzeScan Upload module.

Are you licensed to run EzeScan Upload?

First you'll need to check whether you are licensed to run the Upload option.

• If the Licensing Options say either "EzeScan PRO All (Eval Only)" or contains the words "KFI" and "Upload" then you may run the Upload option.
• If your current production license is not licensed for Upload but you would like to evaluate the functionality please send an email to support@ezescan.com requesting a 15-day evaluation license with Upload enabled.

Prerequisites for running Upload

Before attempting to configure and run Upload you must have created:

• A job type or Route type that is going to be used with the Upload type you are going to create.
• A KFI type that is linked to that Job or Route type. The output indexes created by the KFI type will be used as the input indexes to the Upload module. It is possible to use Upload without KFI, but this is not how it was intended to be run.

1. Refer to the separate EzeScan KFI User Guide document for details on configuring a KFI type (available on the Help Menu)

Upload Interface

The Operator can select the Upload module from the EzeScan Admin menu by selecting Admin > Upload or by pressing the F8 Key.

Managing Upload Types

The Upload module may be accessed in either of the following means…

1. When the EzeScan image viewer is not displaying images, the Upload Admin form allows the operator to manage (create, edit, delete, rename) any of the available Upload types.

OR

1. When the image viewer is displaying images, the Upload Admin allows the operator to edit the settings of the current Upload only.

The following form is displayed…

Selecting an existing Upload type

Simply choose an Upload Type from the list of available types using the pull down shown in Figure 4

Adding, renaming & removing Upload types

Upload types are managed by using the following lists and buttons:

	Adding a new Upload type Use this button to create and save a new Upload type. It will default with a new name. Overtype this to make it your own and click OK Figure 5 - creating a new Upload type
	Copying a Upload Type Use this button to copy an existing Upload type to a new Upload type. This will automatically put a 2 on the end of the type. For example… Figure 6 - copying an existing Upload type Overtype this to make it your own and click OK
	Renaming a Upload Type Use this button to rename an existing Upload type. Select the required Upload and click Rename and the first screen appears with the existing name + a number (e.g. New Upload Name 3) Overtype the old name to make it your own and click OK For example…
	Removing a Upload type Use this button to remove an existing Upload type. _Default Upload type may not be removed from the list.
	Notes The Notes button provides the ability to add some notes about the Upload so that anyone opening it may be able to understand certain aspects of it.

Upload Properties

After a new Upload type is created the properties must be set.
This will allow the operator to define the Repository, Document, Index File and logging options etc.
The first thing to do is to select the system/application which you wish to Upload to refer to the Available Upload Connectors section on page for a list of supported connectors.

Upload to section

Upload to

Select the drop down box to choose the repository to be Uploaded to. When selected, rows below will appear for the operator to populate with the respective information for the selected repository as shown in Figure 9. For example… DocuShare - will ask for Server, Username & Password etc SharePoint 2016 - will ask for site URL, Login details and Domain etc HPE Content Manager - will ask for Database ID, container type etc After the Upload option is selected, the Field Mappings Grid (to the right) will populate with its default respective fields.

Connector Settings

This part of the Upload settings will change depending on the selected connector. Please refer to respective connector user guide for assistance.Available in the Help menu…

Run Command section

Index File section

Column Names From	Default is (none) This is used to specify which KFI is used with the Upload. If a KFI is selected then associating the field mappings are a lot easier. For Example, if a field in KFI is called "Title" it will most likely need to be mapped to the Title field in Upload. Firstly the operator will need to select the KFI that will be used.   Then in the Source field a drop down list will appear showing the KFI fields. The operator can select the respective KFI field to map to the Upload field. In this case it is "Title"
Index File Number	Default is 1 This option is whether to use the 1st KFI index file or the 2nd KFI index file etc.
Index File Type	CSV (default) The KFI module by default writes out to a CSV file. This will allow the operator to choose the field mappings from the source field as a pull down. Note: if later reconfiguring KFI fields then the operator must come back into upload to check the upload mappings. The operator will be presented a warning in KFI for when this happens. XML If the KFI is configured to use XML output then the mappings are performed by the XML Node name. The operator would select Node Name from the Source Field pull down and type in the name of the field. Please note it is case sensitive and if the field name has a space it needs to be replaced with an underscore. The advantage of using this method is if KFI fields are moved then no remapping needs to be done. Static values can also be set but the node needs to be identified as <<IXN{{field_name}}>> The operator can also do a calcualation on a numeric value. E.g. <<=IXX{{ezescan_kfi_indexes/file/Amount}} + 1>> If using an upload to ODBC then the node name is also defined as follows. <<IXN{{field_name}}>>
Field Delimiter	Default is , (comma) The character used to separate fields in the index file. If using the Column Names From option, this does not need to be set.
Keep	Default is unticked  This is to keep the image file after the image has been Uploaded. The image is kept in the output folder specified in the Admin form.
Process Backwards	Default is unticked  This will start from the last line of the KFI output file and work its way up to the first line (i.e. in reverse order).
Field Count Override	Default is 0 This option would be used if the KFI output file is modified by a third party before being Uploaded. i.e. a KFI may have 10 fields, the third party app may add an additional 2, so the Field Count Override would need to be set to 2 and then the 2 field mappings could be applied.
Upload Condition	Default is Always Run This option can be used to set an UPLOAD to run or not run based from a field value condition. For example a KFI field could be set to Yes or No and that could be passed into Value From setting – In this example if the "Run UPLOAD" KFI field is set to Yes the upload will run. Please note this setting is primarily designed for chained uploads (Pass to UPLOAD setting). The operator may want UPLOAD 1 not to run but UPLOAD 2 to run, based off the value applied.
Pass to Upload	Default is (none) This option will pass the image and index file onto another Upload. i.e. you may require to Upload to an EDRM system and also Upload to an ODBC database. You can also pass the 2nd Upload to a 3rd and so on
Source Type	Default is File This option used for when an Upload job is run on its own or as a scheduled task. It can be set to File or Folder. If set to File, EzeScan will use the index file specified in the Input file setting.For example - this is the Input File setting. EzeScan will process through each line of the output document and Upload to its respective destination If set to Folder, EzeScan will look for an index file and image per document. When this is selected, the Input File setting is greyed out.
Source Folder	Default is blank but must be set if the Folder option is selected If the Source Type is set to Folder, the operator will need to set the Source Folder. This will be where the EzeScan job has saved the output images and index files. For example… Image_1.pdf Image_1.txt Image_2.pdf Image_2.txt Click in the field and then click on the browse button … to set
Source Filter	Default is *.txt This is where the operator can set a filter on what type of index files to run. For example if the job is outputting to text the filter would need to be set to "*.txt". The operator could also specify index filename options, e.g. if the Upload is only to process documents starting with the letter "A" the filter could be set to "A*.txt".

Document section

Log section

Logging will create a file which will write an entry when a document is Uploaded to its destination. It can assist with troubleshooting and list when an Upload has completed successfully.
This is a sample Upload log file…
2010/06/11 13:06:34,C:\Program Files\Outback Imaging\EzeScan 4.2\Output\Image_1.pdf - Upload completed
2010/06/11 13:06:59,C:\Program Files\Outback Imaging\EzeScan 4.2\Output\Image_2.pdf - Upload completed

Halt on Error	Default is ticked  (Yes) Upload will stop when an error occurs
Log to a single log file	Default is ticked  (Yes) Upload will log all information to one log file instead of logging a single log file per file
Log Folder	Default is blank - EzeScan will save the log file in the same folder as the KFI index file. This option will allow the operator to have the Upload log file to be saved into a specific folder. If required, click in the field and then click on the browse button … to set
Email Error Report	Default is unticked  This will send an email notifying the operator that an Upload failure/s has occurred. This feature works when the Upload module is being run on its own. i.e. File -> Run Upload or Admin -> Upload or running Upload as a scheduled task. Below is a sample email of an error report.
Email Address	Default is blank This is the email address that the Upload error log will be sent to. Ensure SMTP settings are configured via Workstation Options

Markup section

The mark-up options allow the output document to have mark-up text applied to them. System and Upload placeholders can be used. E.g. <<S15>>, <<IF6>> etc.

Field Mappings

This is the field Mappings Grid. This is where the source data (from KFI) is mapped to the Target Field for the respective Upload repository. More information on the Target Fields can be found in section 2.5.

What are the columns and what do they do?

Source Field	This is the value which will be "Uploaded" to the target system. There are 4 types of Source fields: (ignore) the field will not be used. NOTE: Source field cannot be left set to (ignore) when Mandatory the box is ticked  (static value) where a value must be added to the Field Value column System related source - e.g. File Path; Operator Name etc A KFI field name, which appears in the list when the "Column names from" has been set against a particular KFI
Field value	A value must be added into this column when the respective field has it's source field set to (static value). Example are… An EDRMS record type. Found by clicking in the field and then on the browse button … to choose the value from the respective connector/system Setting an EDRMS Container to save a record into using KFI values plus text…Claim Folder	<<IF7>>	SBRN(<<IF6>>) Setting a tick box to yes by adding a Y against the respective field
Target Field	The field in the targeted system which the processed document and associated metadata is being Uploaded to; based on the mapping from the Source field
Type	The default type of metadata the target system will use for the Uploaded metadata. Generally left "as is" but may be changed if an option is available
Mandatory	The EzeScan connector plugin will tick these boxes by default depending on the "Upload to" option selected as these values are generally mandatory in the targeted system. NOTE: The Source field cannot be left set to (ignore) when Mandatory the box is ticked 
Max. Length	Dictates the maximum length the Uploaded metadata will allow to be Uploaded to the target system. For example… If the target system metadata field has a size of 50 then the Max. Length value must be set to 50

What are the buttons at bottom of the grid?

	The plus button is to add another field
	The minus button is to remove a field. (Custom fields only)
	The Auto Populate button will connect to the respective system and obtain all the custom fields for it. Please refer to the target mappings section for each system on how to use this option.
	The Remove All button will remove all custom field mappings in the grid

Command Buttons

	Use the Run button to start a manually initiated Upload of the currently selected Upload Type, using the currently selected Input File
	Use the Stop button to stop the Upload of the currently selected Upload Type. This is only used when input files with more than 1 input row are processed. When the program detects that the button has been pressed it will stop at the end of the processing the current row from the input file.
	Use the View Log button to view the results of the last Upload. The log shows whether the Upload worked or failed, and in case of failures may contain some useful error messages relating to the failure.
	The Launch Explorer button will launch the explorer screen.e.g. My Computer.
	The OK button will save the Upload type and then close the Upload form.
	Use the Apply button to save any changes made to the currently selected Upload type.
	Use the Cancel button to close the Upload Admin form, ignoring any changes made since the last time the Apply button was pressed.

EzeScan Connector Target Field Mappings

The following connectors are available in the Upload module.
Please refer to the relevant user guide available from the Help menu to access all of the connector's Upload documentation.

• Aconex
• Alfresco
• Civica Authority Purchases
• CSV Creator
• DocuShare
• DocuWare
• eDOCS 5 (Open Text)
• eDOCS 6 (Open Text)
• EzeScan Archiver
• Financial Edge NXT
• FTP
• HPE Content Manager (TRIM)
• iManage Work
• Infor Pathway
• InfoRouter (Active Innovations)
• InfoXpert (Infovision)
• Laserfiche
• MYOB AccountRight 2013.5 and above
  • • Purchases
    • Receive Money
    • Sales
    • Spend Money
• Objective ECM
• ODBC (Databases)
• Open Text Content Server
• Raiser's Edge
  • • Constituent
    • Gift Batch
• Sage 200
  • • Accounts Payable
    • Accounts Receivable
    • Purchase Order
    • 2016
• Sage 300
  • • Accounts Payable
    • Accounts Receivable
• SFTP
• SharePoint (Microsoft)
  • • 2013
    • 2016
• SMTP
• TechnologyOne ECM
• TechnologyOne Financials
• Therefore
• WebDAV (Compliant Systems)
• Xero

EzeScan Target Mappings

CSV Creator

The CSV Creator allows for a TXT/CSV file to be created. This can be useful if needed to create a CSV after an EDRMS Upload. For example a system may require the document EDRMS number to be supplied after an Upload.

Upload Properties

To create the columns for the CSV file…

1. Select the CSV Creator option in the "Upload to" field in Upload Properties section
2. Click the Remove All button and all of the current Field mappings will all be removed
3. Click the  button and the first field mapping will appear.
4. If creating header rows the following syntax is used…

   
   

   
   

   Header[

   
   

   
   

   LineNo

   
   

   
   

   ]:Column[

   
   

   
   

   ColumnNo]:{Header Name}
5. To create line rows the following syntax is used…

   
   

   
   

   Line[

   
   

   
   

   LineNo

   
   

   
   

   ]:Column[

   
   

   
   

   ColumnNo]:{Column Name}

Below is an example of a CSV file with a header row and line row

Other Upload Properties

Please refer to previous sections.

FTP (File Transfer Protocol)

The File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files between a client and server on a computer network. FTP is built on a client-server model architecture and uses separate control and data connections between the client and the server.

Upload Properties

Other Upload Properties

Please refer to previous sections.

FTP (Secure File Transfer Protocol)

Secure File Transfer Protocol (SFTP) is a secure version of File Transfer Protocol (FTP), which facilitates data access and data transfer over a Secure Shell (SSH) data stream. It is part of the SSH Protocol. This term is also known as SSH File Transfer Protocol.

Upload Properties

Other Upload Properties

Please refer to previous sections..

ODBC (Open Database Connectivity)

Open Database Connectivity (ODBC) is an open standard application programming interface (API) for accessing a database.
By using ODBC statements in a program, you can access files in a number of different databases, including Access, dBase, DB2, Excel, and Text.
The ODBC function provided by EzeScan Upload process allows the insertion of captured data into a SQL based database using ODBC.

Upload Properties

Upload to	Select ODBC
DSN	This is the User or System DSN to be used to connect to the database. Click in the field and then on the browse button … to select the required ODBC DSN This is configured in the "Data Sources (ODBC)" option in the Control Panel Further details about setting up ODBC settings are available in the KFI User Guide
User	This is the database username
Password	This is the database password
Connection String Suffix	Enter additional ODBC connection string settings. For example: "SUPPRESS_WARNINGS=1"
Use Lookup	Default is unticked  Tick this  option to select a Lookup Set instead of an ODBC query Further details about using Lookup Sets is available in the KFI User Guide Ticking this  option will grey out the DSN section (above)
Connection Timeout	Default is 100 (seconds) This is the time to allow EzeScan to connect to the ODBC connection.
Command Timeout	Default is 100 (seconds) This is the time to allow EzeScan to run the SQL Statement.
Use Transaction	Default is unticked  Tick this  option to use an ODBC transaction for statements; which may be required some ODBC drivers to raise validation errors on commit
Copy To Folder	Default is blank (will not copy the file) This is the folder where the document will be copied to. Placeholders can be used to derive the document path, e.g. M:\Storage\<<F1>>\<<F2>>\ Click in the field and then on the browse button … to browse for the folder to copy the file too.
SQL Statement	The SQL statement is entered in here. Click in the field and then on the browse button … and the following screen will display: If you have used the "Column Names From" option in the index file section the available Field Placeholder names from the KFI type will appear in the list. The column names from option is described in the Index File Section Of Upload Properties on page . When the operator fills in the statement, the sample result will display below. e.g. Load a test KFI output Index file to show the data.   If the document is required to be Uploaded into the database as an image attachment/BLOB, two options can be used. The command "UPDATE_WITH_IMAGE" can be used In the example the operator runs an insert statement to firstly Upload the data, and then a select statement to select the row which UPDATE_WITH_IMAGE is used to pass the document in. For example… insert into dbo.invoices (supplier, ABN, invno, invdate, invamount, transactionid) values('<<Supplier Name>>','<<ABN>>','<<Invoice Number>>','<<Invoice Date>>','<<Amount>>','<<Transaction ID>>'); UPDATE_WITH_IMAGE select invfile, transactionid from dbo.invoices where transactionid = '<<Transaction ID>>'; Please Note: In this example the column transactionid is the primary key, it is recommended to include the primary key column in the update_with_image statement. If the operator wishes to Upload a zone image, e.g. a separate image created by the KFI field option "Output As Separate Image" the placeholder "UPDATE_WITH_ZONE_IMAGE" can be used instead.
	The placeholder <<DOCBLOBDATA>> can be used This option is designed if the operator wishes to call a stored procedure (so therefore everything is done in one statement in EzeScan) or instead of using UPDATE_WITH_IMAGE (option 1) the insert statement can call the <<DOCBLOBDATA>> placeholder directly. For example… call poc_Upload.Upload_claim_doc('<<(Field 1)>>,'<<DOCBLOBDATA>>') Please note: If using Oracle with option 2 the operator must use single quotes around the <<DOCBLOBDATA>> placeholder. If using SQL with option 2 the operator must prefix a 0x in front of the <<DOCBLOBDATA>> placeholder. It is not possible to populate a BLOB parameter when calling an Oracle Stored Procedure using the Oracle ODBC Driver. Use NVARCHAR2 instead. The Oracle ODBC Driver is only capable of passing parameters values of up to 32k in size. As soon as you exceed this limit the driver crashes EzeScan. Due to this limitation it is not recommend to use a stored procedure with DOCBLOBDATA with EzeScan. Use the UPDATE_WITH_IMAGE option instead.
*Run Pre Upload Application * Run Post Upload Application	This will run an application and can be configured to run prior to the Upload of the document or after or can run both. Placeholder values can be used: To pass the output file path use <<FILE>> To pass index file values use <<IF1>> <<IF2>> e.g. IF1 = First field in output file IF2 = Second field in output file Please remember to use double quotes if the application or output values are to contain spaces. e.g. "C:\my app\run.exe" "<<FILE>>" "<<IF1>>" The application must be completed (closed) before the ODBC command runs.
Application State	This can be set to Show or Hide. Show will display the application to the operator. Hide will run the application as a hidden process.

Other Upload Properties

Please refer to previous sections.

SMTP (Simple Mail Transfer Protocol)

SMTP (pronounced as separate letters) is short for Simple Mail Transfer Protocol, a protocol for sending e-mail messages between servers.
Most e-mail systems that send mail over the Internet use SMTP to send messages from one server to another; the messages can then be retrieved with an e-mail client using either POP or IMAP

• The SMTP function provided by EzeScan Upload process allows for sending an email to an SMTP recipient.
• Generally used as a 2^nd Upload process.
• Once the 1^st Upload is processed the 2^nd Upload (set in the "pass to Upload" setting) runs and sends an email.
• It could be an email advising that the document has been processed.

1. The SMTP Mail Settings must be configured when generating emails from an Upload in either the EzeScan workstation options (SMTP tab)

Upload Properties

Other Upload Properties

Please refer to these previous sections… Run Command  page ; Index File  page ; Document  page ; Log  page ; Markup - page .

Target Fields

The SMTP Upload configuration is detailed further in the "Setting up an SMTP Email Notification Upload" section on page .

Creating an Upload

EDRMS Upload

Below we will show an example of creating an Upload into the HPE Content Manager EDRMS.

1. The same order of instructions can be applied when using any of the other ERDMS connectors. Specific details may be found in the relevant Connector user guides found under the EzeScan Help Menus

Pre requisites

Create a Job and KFI

1. Create a Job, KFI and Upload
   1. Open the jobs screen (press F6) and click on the new button
   2. Give the job a name e.g. HPE Content Manager Upload Test
2. When prompted; select Yes to create a KFI
3. When prompted; select No to create the Upload (we will do this later)
4. Leave the job with the standard defaults and take note of the output folder's path

Edit the KFI - Add Fields

1. Create three fields - Title, Date Received and Folder using the standard processes as set out in the EzeScan KFI and HPE Content Manager User Guides (available via the Help menu)
2. The folder should be a valid container in your HPE Content Manager. e.g. 08/6

Run the job and process the KFI

1. Either scan a document or import one using the (above) job
2. Complete the 3 fields; for example…
   1. Title Parking Fine INF00001
   2. Date 06/02/2017
   3. Folder PROP/12345
3. Click submit
4. Make sure that you have an output image and index file created from your Job / KFI.For example - Image_1.tif and Image_1.txt

Create the Upload

Name

1. Start the Upload Admin form by pressing F8 whilst in the EzeScan viewer window.
2. Following the steps outlined in the Create New Upload section on page
3. Press the Add button to create a new Upload Type
4. if you use the same name for the Upload Type, the KFI Type and the Job Type, it will make it much easier for you to manage the linkage between the these 3 types.
   1. We have called our new Upload - HPE Content Manager Upload Test.

Select the EDRMS to Upload to

1. Then from the Upload Admin form choose HPE Content Manager from the list of destination types.

1. The next step is to select your HPE Content Manager Database.
   1. Ticking the "Use Global Settings" box will use the default EDRMS as set in the Workstation Options. Generally the "Production" environment
   2. If you wish to use another environment (e.g. Test) then leave the box unticked and click in the Database ID field then click the browse button … and when prompted select your HPE Content Manager dataset.

Select KFI Output File to test against

1. We need a KFI output index file test file (e.g. Image_1.txt) to use when testing the Upload
   1. Browse and find the KFI output index file that you want to use with this Upload type.
      • The file is required because it is going to contain the KFI index field data that is going to be mapped across to HPE Content Manager properties as the file is Uploaded to HPE Content Manager.
   2. Click on the browse button … and browse to the file…

1. 1. The KFI output should show in the pane below.

Column Names from

1. The next step is to select the KFI that was used.
   1. In this instance the KFI is called HPE Content Manager KFI Test
   2. Select your respective KFI option from the "Column names from" pulldown

1. If your KFI is using a custom output your KFI will not show here. Therefore this option should be ignored. When a custom KFI output has been used the operator will be required to reference the index file to map to the respective EDRMS fields.
2. There are several key points to remember when choosing the Input Fields list box values that you want to map across to an Upload.
3. Each KFI output index file contains comma separated index field values.
4. When the KFI is using a Default CSV Output format…
   1. the first 5 list fields (Field #1 to Field #5 - as shown in Figure 21) are system generated by the KFI processing code itself and contain the following…
      • filename field #1 e.g. image1_tif
      • scanned by field #2 e.g. n.alexander
      • date field #3 e.g. 20170206
      • time field #4 e.g. 101620
      • N° of pages in document field #5 e.g. 1
   2. The following fields (Field #6 onwards) are the user defined KFI fields. For example (as shown in Figure 21)…
      • Title field #6 e.g. Parking Fine INF00001
      • Date Received field #7 e.g. 06-02-2017
      • Folder field #8 e.g. PROP/12345
5. The Document Path is default set to the File Path as this contains the filename.
6. If a custom KFI output is used this would need to be set to field #1.

Mapping the KFI fields

The next steps are to match the KFI fields against the HPE Content Manager Upload fields.

1. The mandatory Record Type should default to an existing record type.
   1. To change this, click in the Database ID field then click the browse button … and select the required record type for the document
2. Match the Title Source (KFI) field to the corresponding mandatory (Title)Target field
3. Match the Folder Source (KFI) field to the corresponding (Container)Target field
4. Match the Date Received Source (KFI) field to the corresponding (Date Created) Target field

1. Configuration of the job type is complete.
2. Press the APPLY button to save the changes.

1. You may now press the Run button to manually test the Upload type mapping that you have just setup.

1. EzeScan should display an Upload Completed message, and the document is saved into HPE Content Manager.

1. 1. If the Upload shows a message Upload completed with errors.
      • This will usually mean that there is a mapping problem.
      • Click the View Log button to view more information on the error
2. Record in HPE Content Manager

EzeScan Archiver Upload

EzeScan Archiver is a simple web retrieval tool for storing documents and metadata. It provides a web interface to allow an operator to search and retrieve documents.

1. Please read the following…

• EzeScan ARCHIVER does not replace an existing EDRMS (Electronic Document Records Management System).
  • It is designed for back scanning projects or low volume storage of documents.
  • The EzeScan Archiver is designed for up to 50,000 documents (with 5 metadata fields).
    • Anything over this will incur a decrease of performance.
  • It is also recommended to use the Firefox web browser for search and retrieval of documents.

Configuring EzeScan Archiver Properties

The properties for the EzeScan Archiver Database are required to be configured. When the first document is Uploaded, the database and supporting files are created in the Disc Path folder.

Upload to	This is required to be set to EzeScan Archiver
Archive Path	The path of where the archive database is saved to. When first run EzeScan will create the database, it's supporting files and a documents folder. The Archive Path also supports placeholders. For example… if the requirement is to create a new archiver database automatically at the start of every year the value could be something like C:\EzeScan\Archive\General<<S3(MMYYYY)>>
Use original filenames	If set to Yes (default), will use the filename created from the JOB/KFI. If set to No, EzeScan Archiver will use its own file numbering method which is sequentially generated from the number 1. Cannot be changed after archive creation
Store index files	If set to Yes (default), will save a copy of the index file with the scanned document into the documents folder. It is recommended to have this setting set to Yes. i.e. if required, it provides an easy way to upgrade or migrate the data at a later time
Custom HTML path	This option allows for the creation of a customized index.html search page. If set to yes the operator needs to supply the custom files into "C:\ProgramData\Outback Imaging\EzeScan\Archiver" Only available when creating a new archive
Maximum archive size (MB)	This option allows the operator to set a maximum size (MB) of the documents store in the Archiver database. When the document limit is met the operator will be prompted with the following message…
Max file count	Limits the number of files in a single document directory and create new directories as required. Choose from… 1000 (Default) 5000 10000 This is recommended for larger size Archive stores as it will provide a small improvement on searching.

Configuring EzeScan Archiver Upload Field Mappings

By default there are no target fields as there is no database to browse.
When the first document is Uploaded to EzeScan Archiver the database gets created.

1. Once the EzeScan database is created the operator cannot make any changes to it (i.e. add or remove fields). If fields are required to be changed, a new database needs to be created.
2. To create the field mappings click the  button.
   1. The following will display…

1. The Target Field is the name of the field that will appear in the web retrieval screen.
   1. Click on where it says "Custom Field 1" and rename it to respective name that is required to be viewed by the search operator. (e.g. Title)
2. Use the Column Names From setting to set the name of the KFI that the Upload will be using. E.g. the KFI source field value Is Title so the Target Field will also be Title.
   1. Refer to the Index File section on page for more information on these settings.

1. Click Apply to save the changes.
2. Repeat steps 1 to 4 for any additional Fields (e.g. Date Received, From etc)
3. When complete, click OK to close the Upload screen.
4. Refer to the Configuring a Job Type to use an Upload Type section on page for details on how to configure a job to use the Upload.

Viewing an EzeScan Archiver database

When a document is Uploaded into the Archive Path (e.g. C:\EzeScan\Archive\General) the following files are created…

• Resources Folder
  • archiver.js
  • ezescan_logo.png
  • jquery.js
  • progress.gif
  • styles.css
• Documents Folder
  • The Output images (e.g. Image_1.tif)
  • The Output text file (e.g. Image_1.txt)
• index.html
• store.xml
• \Documents (folder) (if specified in the Upload set-up

The operator can double click on index.html and the following will appear in the browser (if asked to run an ActiveX control select Yes).

1. The Archive database can be viewed as an http:// web link. This would require an administrator to host the above files on a web server. Please refer to your local administrator for more information.

The operator can then perform a search by selecting a metadata field and enter a value.

ODBC Upload

1. It is assumed that the operator undertaking the tasks below has access to an SQL database. An SQL database running in something like Microsoft SQL Server Management Studio will suffice. The operator must also have full rights in order the create and write to the database.

Pre requisites

Create an SQL Database to use

In order to facilitate an ODBC Upload we need to have an SQL database in which to Upload to
We will need the database to include the following:

• Database name e.g. ezescandb
• Table name e.g. suppliers
• Table fields supplier_name; invoice_number & file_path
• SQL login credentials. Username (e.g. sa) & Password (e.g. password)

SQL to create table in ezescandb

<span style="color: #0000ff">CREATE</span> <span style="color: #0000ff">TABLE</span> [ezescandb].[dbo]<span style="color: #808080">.</span>[Suppliers]<span style="color: #808080">(</span>
[supplier_name] [varchar]<span style="color: #808080">(</span>100<span style="color: #808080">)</span> <span style="color: #808080">NULL,</span>
[invoice_number] [varchar]<span style="color: #808080">(</span>100<span style="color: #808080">)</span> <span style="color: #808080">NULL,</span>
[file_path] [varchar]<span style="color: #808080">(</span>100<span style="color: #808080">)</span> <span style="color: #808080">NULL</span>
<span style="color: #808080">)</span> <span style="color: #0000ff">ON</span> [PRIMARY]
Finally create an ODBC Connection (e.g. System DSN = Suppliers) to the database from the ODBC Data Source Administrator in the Control Panel. Note the Data source name.

Create a Job and KFI

1. Create a Job, KFI and Upload
   1. Open the jobs screen (press F6) and click on the new button
   2. Give the job a name e.g. ODBC Upload Test
2. When prompted; select Yes to create a KFI
3. When prompted; select No to create the Upload (we will do this later)
4. Leave the job with the standard defaults and take note of the output folder's path

Edit the KFI - Add Fields

1. Create two fields - Supplier and Invoice Number using the standard processes as set out in the EzeScan KFI (available via the Help menu)

Run the job and process the KFI

1. Either scan a document or import one using the (above) job
2. Complete the 2 fields; for example…
   1. Supplier Outback Imaging Pty Ltd
   2. Invoice Number 123456
3. Click submit
4. Make sure that you have an output image and index file created from your Job / KFI.For example - Image_1.tif and Image_1.txt

Create the Upload

Name

1. Start the Upload Admin form by pressing F8 whilst in the EzeScan viewer window.
2. Following the steps outlined in the Create New Upload section on page
3. Press the Add button to create a new Upload Type
4. if you use the same name for the Upload Type, the KFI Type and the Job Type, it will make it much easier for you to manage the linkage between the these 3 types.
   1. We have called our new Upload - ODBC Upload Test.

Select KFI Output File to test against

1. We need a KFI output index file test file (e.g. Image_1.txt) to use when testing the Upload
   1. Browse and find the KFI output index file that you want to use with this Upload type.
      • The file is required because it is going to contain the KFI index field data that is going to be mapped across to the SQL database properties as the file is Uploaded.
   2. Click on the browse button … and browse to the file…

1. 1. The KFI output should show in the pane below.

Column Names from

1. The next step is to select the KFI that was used.
   1. In this instance the KFI is called ODBC Upload Test
   2. Select your respective KFI option from the "Column names from" pulldown

1. If your KFI is using a custom output your KFI will not show here. Therefore this option should be ignored.
2. There are several key points to remember when choosing the Input Fields list box values that you want to map across to an Upload.
3. Each KFI output index file contains comma separated index field values.
4. When the KFI is using a Default CSV Output format…
   1. the first 5 list fields (Field #1 to Field #5 - as shown in Figure 36) are system generated by the KFI processing code itself and contain the following…
      • filename field #1 e.g. image1_tif
      • scanned by field #2 e.g. n.alexander
      • date field #3 e.g. 20170206
      • time field #4 e.g. 042554
      • N° of pages in document field #5 e.g. 1
   2. The following fields (Field #6 onwards) are the user defined KFI fields. For example (as shown in Figure 36)…
      • Supplier field #6 e.g. Outback Imaging Pty Ltd
      • Invoice Number field #7 e.g. 123456
5. The Document Path is default set to the File Path as this contains the filename.
6. If a custom KFI output is used this would need to be set to field #1.

Set-up the Upload Properties section

Complete the setting as set-out below…

About the SQL Statement

The SQL Statement shown in the above table can be broken down to two components

1. The SQL commands:

insert into suppliers (supplier_name, invoice_number, file_path) values

1. The KFI fields:

('<<Supplier Name>>','<<Invoice Number>>','C:\ProgramData\Outback Imaging\EzeScan\Output\ODBC Upload Test\<<Supplier Name>>\<<(File Path)>>')

Creating the SQL Statement

1. The SQL Statement can be generated by clicking into the field and then the browse button … to display the screen shown in Figure 39.

1. The end result we know want to achieve is this…
   1. the Supplier Name KFI field gets Uploaded to the supplier_name SQL field.
   2. the Invoice Number KFI field gets Uploaded to the invoice_number SQL field.
   3. the output file path gets Uploaded to the file_path SQL field.
      • A sample result is shown above in Figure 39.
2. Click OK to save and close the SQL Statement screen
3. Click Apply.

Run a Test Upload

You may now press the Run button to manually test the Upload that you have just setup.

Appendices

Configuring a Job Type to use an Upload Type

The Job Type used in this example is available for Download on the EzeScan web site.

• Login to the EzeScan web site (www.ezescan.com.au) and navigate to…
• Downloads > Software Downloads > Sample Jobs > EzeScan Archiver Jobs > Archiver - Zone OCR Job
• Download the EzeScan Archive - Zone OCR Demo.zip file.

1. Unzip the downloaded file and import the EzeScan Archiver - Zone OCR demo.cfg file into EzeScan.
2. In EzeScan press F6 to launch the Jobs Form
3. Select the EzeScan Archiver - Zone OCR demo job type which we use in this use Upload
4. Select the Output tab

1. From the Other Destination list choose KFI.
2. From the Available KFI Types choose the EzeScan Archiver - Zone OCR demo type.
3. From the Available Upload Types choose the EzeScan Archiver - Zone OCR demo type.
4. Click the Save button to complete the setup. You are now ready to run the job.

Running the EzeScan KFI & Upload job

1. In EzeScan press F2 to launch the Operator Actions form.
2. Then select the job type that you have configured for use with KFI. In this case it's the EzeScan Archiver - Zone OCR demo job type.
3. Then press the File Import button to acquire a batch of documents for KFI processing.
4. In this example you need to select the file called EzeScan Archiver - Zone OCR demo.tif.
5. Open the selected file and it is displayed in the viewer.
   1. This example consists of a batch of 3 documents.
6. Press the F4 button (or press

   

   )to profile the document, the KFI form is loaded into the viewer window panel as shown in Figure 45 below.
7. As the name indicates; this is an OCR job and EzeScan will use a KFI template to capture the fields from specific areas on each of the "structured" documents.

1. In this example the OCR has picked up the Supplier Name ACME Corp Ltd as the value.
2. Hit the Enter key and the Work Order Number 2201 will be captured
3. Hit the Enter key and the Date 08/07/2010 will be captured
4. Then the operator can either press Enter twice or click the Submit button.

• In this example EzeScan converts the file from TIF to PDF and then writes the indexes out to the KFI output index file.
• KFI then calls Upload which opens the KFI output index file and proceeds to connect to the Upload destination transferring the file and index fields as required.
• If the transfer to the Upload destination worked okay, the document is removed from the viewer and the next document in the batch (if any) will be selected for processing.
• If the Upload fails for any reason, the current document will remain selected in the viewer and an error message will be displayed to the operator.
• The process is repeated for each document in the batch.

Running an Upload as a batch task

The Upload can be run as a separate task.
This is usually done if there is a bottleneck in the PDF OCR or Upload process.
Setting the Upload to be run as a separate task means that the PDF OCR and Uploading to the respective system can be scheduled to run outside of the operator scanning / index times. (e.g. outside of business hours)

1. To run an Upload as a batch task it is recommend that the KFI output setting Use a single index file for all documents is enabled.

If the Upload module is planned to perform the OCR,

• the job needs to be set to TIF
• the Upload setting Convert File Format To needs to be set.
  • Please refer to the Run Command section on page for more information.

Split the JOB / KFI and Upload

To split the JOB / KFI and Upload job so Upload becomes it's own task is easily done.
Is it shown below in our example job type EzeScan Invoice - Zone OCR

1. Firstly we select the Upload Type on the Output Tab.

1. Then we set the Upload Type to None.

1. Click Save then Close.

Now when this job type is run, the output index file and images will be queued up in the job type output directory.
In the Upload module, the operator needs to set the index file to be used.

1. Select Admin then Upload and browse the output index file.

e.g. this is the Input File setting.

1. Manually by running from the File Menu
   1. Select File, Run Upload and then click the Run button.

OR

1. 1. Select Admin, Upload, select the Upload job from the dropdown list and click the Run button.
2. Run as a scheduled task
   1. The task could also be automated by running as a scheduled task.

   2. A batch file needs to be created and the following commands can be used in it.

      Command	Usage
      -Upload	The Upload job name
      -Uploadindex (single index file)	This is the name of the index file. This setting would need to have the Upload Source Type is set to file.
      -Uploadindex (index file per document)	This is the name of the folder of where the documents and index files reside. This setting would need to have the Upload Source Type is set to folder and the Source Folder set to the same folder path.
      -closeafter	This will close EzeScan after the Uploading has completed.
      -closeotherinstances	This will close all other instances of EzeScan (if open) before the Upload task begins to run.

      This is a sample command with all the options used (for a single index file).

      C:\Program Files\Outback Imaging\EzeScan 4.2\ezescan.exe -Upload "Upload Job Name" -Uploadindex "C:\folderpath\indexoutput.txt" -closeafter -closeotherinstances

3. Setting up an SMTP Email Notification Upload

The processes and examples documented here have been provided to act as a guide only for setting up your own SMTP email notification Uploads.

If there is a requirement to send notification emails as part of the Upload process then the steps below need to be followed.
The first requirement is to have the SMTP component set-up on the EzeScan client and/or Server; depending on where the Uploads have been set to run.

SMTP mail settings on EzeScan Client

1. Select Admin > Workstation Options and click on the Email tab
2. Enter the hostname or IP address of the SMTP server
3. Enter the server port (default is 25)
4. Enter the login/username and password to access your SMTP mail server account
5. Select the Security Type to use when connecting to the SMTP server, default is None
6. Enter the "Senders (From)" name you want to use in the emails (e.g. John Smith)
7. Enter the "Reply" email address you want to use in the emails

Add the SMTP Email fields to your KFI

The email addresses used by the Upload to SMTP process can be configured in either the Upload or the associated KFI

• Adding it to the Upload means that all processed documents will always be sent to the same email address
• Adding it to the KFI means that the operator then has the flexibility to select who should receive the email - recommended option
  • There are 3 different methods which could be used for the operator to add/select an email address in the KFI field…
    • Operator manually types the email address into the field - can be an onerous task if this functionality is to be used a lot
    • A list of email addresses are added into the Display a list of values > List field of the Format tab (refer to the KFI User Guide for process to create a list)
    • Set up an "LDAP" connection on the KFI field which will provide the operator with a search function to select email addresses from your corporate email system.

1. Suggest using the LDAP function as there will be no ongoing maintenance required of the KFI field. This is the option used in the example below.
2. Please refer to the "Use an LDAP Lookup Form" section in the KFI User Guide for details on how to create an LDAP Lookup Form in your associated KFI.

Add the following fields into your KFI…

Creating the SMTP Upload

Email body created using "Plain Text"

1. Create a new Upload (in this example it's called Sample SMTP Emails)
2. Select Upload to > SMTP
3. Select the KFI which the column names will get their "Source Field" values from

4. Map the Source Fields to the Target Fields (using either static or KFI field values):

   Source Field	Field Value	Target Field	Comments
   (static value)	New Correspondence - FYI	Subject	See a) below
   Select Send Email To address		To	See b) below
   Select Send Email To address		CC	See b) below
   (static value)	The attached corresponde…	Message Body Text	See c) below
   Select from Email Address		From	See b) below
   (static value)	<<S1>>	Attachments	See d) below

   
   

   1. This text is what will appear in the email "Subject" line.
      • You could use free text as shown above or you could select a KFI field (e.g. Title)
      • You could also use multiple fields such as Title and Date Received (set as static value)
        • For example based on the KFI shown in Figure 50 it would be <<IF7>> received <<IF9>>
   2. This will take the value from the KFI field.
      • If the KFI field is blank (e.g. "Select Send Email To address" and/or "Select from Email Address") then the Upload will then skip this part of the Upload.
   3. The message body needs to be constructed so it is easy to understand therefore consideration needs to be given in its development. It should be clear, concise and easy to understand (refer to Figure 52 for an example of the email).
5. It probably easier to create the email in MS Word or Notepad then paste it into the Upload field when finished editing.
6. This example is using the "Message Body Text" option which will create the email body with plain text. If you need to "format" the body with coloured fonts, document links, tables etc then you will need to use the "Message Body HTML" option as outlined on page .
   • • To create a line break (new paragraph) you must use this value at the end of the line <<BR>>
       • Using 2 of these will give 2 line breaks <<BR>><<BR>> which was used in Figure 52.
     • To use a KFI field you must add 5 to the field number and use <<IFn>> instead of <<Fn>>
       • In this example
         • Date Received <<F4>> is <<IF9>>
         • Authors Name <<F6>> is <<IF11>>
         • Additional Information <<F12>> is <<IF17>>
       • The text used in the example used in Figure 52 is shown below

         • It is important that the text is one continuous string as shown in the 2^nd box below…

           How it looks in the editor (MS Word/Notepad)… The attached correspondence was received on <<IF9>> from <<IF11>> and processed by the Information Management Team.<<IF17>> <<br>><<br>> This email has been sent to you as the correspondence may be of interest to you. <<br>><<br>> The correspondence has also been forwarded to the appropriate department for action. <<br>><<br>> regards, <<br>> Information Management <<br>><<br>> There is no need to reply to this email

           
           

           How it needs to look before copy & paste into the Upload field… The attached correspondence was received on <<IF9>> from <<IF11>> and processed by the Information Management Team.<<IF17>><<br>><<br>>This email has been sent to you as the correspondence may be of interest to you.<<br>><<br>>The correspondence has also been forwarded to the appropriate department for action.<<br>><<br>>regards,<<br>>Information Management<<br>><<br>>There is no need to reply to this email

           
           

   1. <<S1>> is the filename created by the process and will attach it to the email.
      • As this email body is "plain text" you cannot use document (hyper)links but you can if using the Message Body HTML option (see below) instead of Message Body HTML as used in this example

Email body created using "HTML"

The process for creating the Upload is exactly the same as outlined in the previous section but the Upload Target field will be Email Body HTML instead of Email Body Text

1. Even though it may be nice to use the HTML option for the email body text you must have someone within your organisation who knows how to create and manage the HTML code.

In this example we will use the same email body as used in the previous example but we will send the email with some formatting along with a document hyperlink and no attachment.

• This would need to rely on the "output location" of the document
  • i.e. it is saved to a location where the receiver will also be able to access it
    • they have read access (at minimum) to the network folder where it is saved)
• If the document is Uploaded to an EDRMS then a hyperlink to the document in the EDRMS could be sent - only if the EDRMS supports that functionality

The same KFI may be used but the Regex on the Output tab of the "Any additional email comments?" field must be changed to "^(.+)$","<p>Additional information - $1"</p>
HTML (Hypertext Markup Language) uses tags as a means to "mark-up" a web page. This example is using very basic HTML to create the text for the email body and has not used a CSS (Cascading Style Sheet). The HTML tags used in this example are:

1. Using an HTML editor to create your email body will make it easier to build and format the text to meet your corporate design standards but you cannot just copy and paste it into the Upload field you will need to do a bit more editing just like shown Table 4 on page (below).

   How it looks in the editor … <body> <span style="font-family:Arial"> <span style="color:#0000ff"> <p>New correspondence has been received and processed by the Information Management Team and this email has been sent to you as the correspondence may be of interest to you.</p><<IF17>> <p>Access the correspondence using this <a href="<<S1>>"><strong>link</strong></a>.</p> <p>The correspondence has also been forwarded to the appropriate department for action.</p><p>regards,<br><strong>Information Management</strong></p> <p><i><span style="color:#ff0000">There is no need to reply to this email</i></span></p> </span> </span> </body>

   
   

   How it needs to look before copy & paste into the Upload field… <body><span style="font-family:Arial"><span style="color:#0000ff"><p>New correspondence has been received and processed by the Information Management Team and this email has been sent to you as the correspondence may be of interest to you.</p><<IF17>><p>Access the correspondence using this <a href="<<S1>>"><strong>link</strong></a>.</p><p>The correspondence has also been forwarded to the appropriate department for action.</p><p>regards,<br><strong>Information Management</strong></p><p><i><span style="color:#ff0000">There is no need to reply to this email</i></span></p></span></span></body>

2. The hyperlink shown in this example is using the file name & filepath <<S1>> of the processed document. This will naturally change if using a hyperlink to a document saved to an EDRMS (if the EDRMS has this functionality.

Upload Placeholders

An EzeScan Upload Placeholder is a value that is temporarily stored when EzeScan is processing a document.

Standard Placeholders

Below are the Placeholders that can be used in the Upload module.

Calculated Placeholders

To add two numeric fields in Upload.
<span style="color: #0070c0"><strong><<=IF6+IF7>></strong></span>
Subtract , Multiply (×), and divide are also supported.
Prefix calculations with [0.00] to ensure always 2 decimal places.
<span style="color: #0070c0"><ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e2366e2d-9ef0-423c-ba03-549fcb5825f4"><ac:plain-text-body><![CDATA[<<=[0.00]F1*F2>>

]]>

1. Only numeric field values are supported and empty field values are treated as 0 in equations.
2. System placeholders can also be used. Please refer to the System Placeholders section in the Appendices of the EzeScan User Guide