eFLOW Run Time Modules PDF

eFLOW Run Time Modules
Reference Manual
eFlow 4.5
Top Image Systems Training Department
© Top Image Systems
www.TopImageSystems.com
Copyright Integra Run Time User Guide
© 2009 Top Image Systems Ltd.
Top Image Systems eFLOW Run Time Modules Reference Manual
This manual and the software described in it are furnished under license, and may be used or copied only
in accordance with the terms of such license. The content of this manual is provided for informational
use only, and is subject to change without notice. It should not in and of itself be construed as a
commitment by Top Image Systems Ltd, which assumes no responsibility of liability for any errors or
inaccuracies that may appear in this book.
The software that accompanies this manual is licensed for use by the Licensee only in strict accordance
with the software license agreement, which the Licensee should read carefully before commencing use of
the software. Except as permitted by the license, no part of this publication may be reproduced, stored in
retrieval system, or transmitted in any form of by any means, electronic, mechanical, recording, or
otherwise, without the prior written permission of Top Image Systems Ltd.
ii
eFLOW Run Time Modules Manual
Table of Contents
Chapter 1 Overview of eFLOW.................................................................................................... 1
The eFLOW System .................................................................................................................... 1
Chapter 2 Enterprise Manager .................................................................................................. 10
Overview................................................................................................................................... 10
Invoking and Using the Enterprise Manager ............................................................................ 11
Site Management....................................................................................................................... 12
Applications Management ........................................................................................................ 14
Security Management ............................................................................................................... 23
Statistics Settings ...................................................................................................................... 28
Licensing and Version Information .......................................................................................... 30
Chapter 3 Introduction to Module Activator............................................................................ 33
Overview................................................................................................................................... 33
Invoking the Controller............................................................................................................. 34
Chapter 4 The Controller ........................................................................................................... 35
About the Controller ................................................................................................................. 35
Controller Desktop Layout........................................................................................................ 36
Using the Menu Bar .................................................................................................................. 36
Using the Tool Bar.................................................................................................................... 39
Controller Options..................................................................................................................... 40
Mode Selection ......................................................................................................................... 42
Workload Mode ........................................................................................................................ 43
Workload Run-Time Module Information................................................................................ 43
Collections Mode ...................................................................................................................... 49
Stations Mode ........................................................................................................................... 52
Viewer Mode ............................................................................................................................ 53
Domain Mode ........................................................................................................................... 54
The Collection Viewer .............................................................................................................. 55
Using the Menu Bar .................................................................................................................. 55
Chapter 5 Input - Getting Started ............................................................................................. 59
Overview................................................................................................................................... 59
Features ..................................................................................................................................... 59
Activating the Portal Modules .................................................................................................. 59
Chapter 6 Scan Portal ................................................................................................................. 60
Chapter 7 File Portal................................................................................................................... 61
Overview................................................................................................................................... 61
Chapter 8 Page OCR................................................................................................................... 62
Overview................................................................................................................................... 62
Getting Started .......................................................................................................................... 62
Manual or Standby Processing.................................................................................................. 65
Chapter 9 Content Recognition - Processing ............................................................................ 66
Overview................................................................................................................................... 66
The Processing module ............................................................................................................. 66
Getting Started .......................................................................................................................... 67
Initiating the OCR Process........................................................................................................ 70
Chapter 10 Content Recognition - Form ID ............................................................................... 71
Overview................................................................................................................................... 71
Getting Started .......................................................................................................................... 72
FormID Toolbar ........................................................................................................................ 74
Initiating the Form Recognition Process................................................................................... 74
Chapter 11 Content Recognition - Manual Form ID ................................................................. 75
Overview................................................................................................................................... 75
Getting Started .......................................................................................................................... 76
iii
Manual FormID Toolbar........................................................................................................... 79

Initiating the Manual ID Process .............................................................................................. 79
Chapter 12 Free Match................................................................................................................. 87
Overview................................................................................................................................... 87
Getting Started .......................................................................................................................... 88
Free Match Toolbar................................................................................................................... 90
Initiating the Form Recognition Process................................................................................... 90
Chapter 13 Manual Match ........................................................................................................... 91
Overview................................................................................................................................... 91
Getting Started .......................................................................................................................... 92
Manual Match Menu Bar .......................................................................................................... 92
Manual Match Toolbar.............................................................................................................. 94
Initiating the Manual Match Process......................................................................................... 95
Chapter 14 Tile Module .............................................................................................................. 102
Overview................................................................................................................................. 102
Getting Started ........................................................................................................................ 103
Tile Menu Bar ......................................................................................................................... 104
Tile Toolbar ............................................................................................................................ 105
Initiating the Tile Process ....................................................................................................... 106
Chapter 15 Content Validation in Completion......................................................................... 109
Overview................................................................................................................................. 109
Getting Started ........................................................................................................................ 110
The Completion Process ......................................................................................................... 111
Using the Completion Module................................................................................................ 112
View ................................................................................................................................... 112
Data Manipulation................................................................................................................... 114
Document Merge..................................................................................................................... 118
Batch Manipulations ............................................................................................................... 118
Navigation............................................................................................................................... 118
Customization ......................................................................................................................... 121
Menus and Toolbars................................................................................................................ 122
Chapter 16 The FreeCollect Station .......................................................................................... 124
Chapter 17 Content Delivery - Export ...................................................................................... 125
Overview................................................................................................................................. 125
Installation............................................................................................................................... 126
Invoking and Using the Export Module.................................................................................. 126
Export File Types and File Storage Overview........................................................................ 127
Export Configuration .............................................................................................................. 130
Graphical Overview of Export SystemMonitoring the Export Module.................................. 138
Monitoring the Export Module ............................................................................................... 139
Chapter 18 OCR Analyzer ......................................................................................................... 144
OCR Analyzer Startup ............................................................................................................ 149
Desktop Layout ....................................................................................................................... 150
OCR Analyzer Modes............................................................................................................. 152
Process Mode .......................................................................................................................... 154
Form View Mode.................................................................................................................... 158
Field Statistics Mode............................................................................................................... 164
Chapter 19 Debug Logger........................................................................................................... 171
Chapter 20 Utility Kit ................................................................................................................. 174
Index ................................................................................................................................... 175
iv
Chapter 1 Overview of eFLOW

This manual describes the Run Time modules of eFLOW. The first part of this introduction
deals with eFLOW as a whole, illustrating the part that the Run Time modules play in the
system. The second part of this introduction takes a look at the steps involved in the design
procedure.
The eFLOW System
TiS have developed the eFLOW Unified Content Platform, to deliver the solutions
customers require. Whether information enters an organization via predefined forms from
clients, internet-based e-forms from customers, incoming supplier invoices, or employees in
the field with mobile devices, eFLOW digitally captures and manages the enterprise’s
content from the source through to delivery to ERP, CRM, and financial or other systems.
All TiS product solutions plug into the eFLOW Unified Content Platform and take
advantages of the common services the platform provides.
Figure: eFLOW Unified Content Platform
1
TiS products include:
Integra™
Captures data from all types of structured forms including paper, fax, image files, the
Internet and mobile devices. Integra automatically validates and delivers the data to the
target enterprise application. Integra’s exclusive advanced features deliver:
Greater operator productivity
Unprecedented character recognition and error detection
Powerful engines with an exclusive voting algorithm to achieve the most accurate
results
Faster and more efficient forms processing
Quick and simple “point and click” application design
Minimum human intervention means reduced labor costs and higher data integrity.
Freedom™
Reads, understands and processes semi-structured forms, such as incoming supplier
invoices, without the need to predefine the structure of all of the various forms. Freedom
captures, validates and delivers the data from the semi-structured form to the required
applications.
Freedom handles any type of semi-structured forms, including forms with
complicated tables and multi-page invoices
Freedom’s high-speed content recognition replaces the expensive manual process of
keying in data from the invoice
Freedom recognizes the semi-structured form and the fields according to keywords
and key terms situated anywhere on the page, such as Payment Date, Sum, Name
Offers unprecedented character recognition and error detection
Offers powerful “super engines” that vote to achieve the most accurate results
Offers faster and more efficient invoice processing
Delivers minimum human intervention to reduce labor costs and increased data
integrity:
Completion station for manually identifying field locations and field content
FreeCollect station for analyzing Completion data in order to update the
learning database.
Smart™
Smart performs fully-automatic classification of documents flowing into an organization.
Smart acts as a mailroom application, deciding which department, business unit or subject
each document belongs to, and subsequently, to whom the document should be directed.
Smart can classify incoming documents as invoices, change-of-address letters, and
purchase orders, or it can classify into more general categories, such as documents
belonging to the sales, finance or customer service department. These categories are called
classes.
2
Smart uses a technique called supervised learning to classify documents with little or no
prior knowledge about them. The software examines a limited sample of documents from
each class, and automatically learns the unique characteristics of that class. This process is
called training. From that point onwards, Smart can classify any incoming document into
the trained classes, with a high level of accuracy, and with no human intervention.
eFLOW Configuration and Architecture

The system architecture is based on a 3-tier architecture for capturing, processing, and
storing the forms. The network structure facilitates adaptation to changing workloads and
functionality by enabling the addition/removal of system components from the network
with minimal software modifications (configuration definitions).
Once a decision is made to add stations to the system (for example, more content
recognition or content validation stations), the architectural design facilitates an increase in
computing and processing power. eFLOW and its products are fully scalable.
eFLOW’s flexible configuration and design allows for easy adaptation to the rapidly
changing needs of the computer market.
eFLOW Visual Designer

The Visual Designer, which serves all products, provides the ability to set up
Applications, define OCR engines and setup workflows using the following
components:
The Application Visual Designer

Using the Application Visual Designer module of the eFLOW
platform package, you can create multiple form-processing
applications in just a few hours. Here you define the application’s
building blocks: flows, forms, fields, and exceptions.
The OCR Visual Designer

Use the OCR Visual Designer of the eFLOW platform package to
quickly build OCR virtual engines and perform in depth, rapid
engine testing and fine-tuning. Here you can quickly redefine,
perfect and test engine parameters to get the best recognition
results.
The Workflow Visual Designer

Use the Workflow Visual Designer to construct sequence of
activity in the run time stage. Templates and custom design are
both available for much greater flexibility, allowing you to
choose a Workflow most suitable to your processing needs.
3
Integra Run-Time Modules
eFLOW platform modules consists of the: Controller, Designer and Statistics.

The Module Activator is used to run the modules.
Through the Module Activator, you operate the Integra’s modules: the
Enterprise Portal, Content Recognition, Content Validation, and Content
Delivery modules, which comprise the full data-capture process. The number
of instances of each module that can be utilized in run time is limited only by
the number of relevant licenses, ensuring full system scalability for future
needs.
Enterprise Portal Modules
Scan Portal
Use the Scan Portal module to supply scanned forms to the
system. This application supports a wide range of scanners.
File Portal
Use the File Portal module to supply image files of previously
scanned forms to the system
Content Recognition Modules

FormID
The FormID module receives data from the Enterprise Portal
Modules for FormID identification. It automatically identifies a
form using Empty Form Images supplied during the design stage.
Manual FormID
When the FormID module cannot identify the form due to poor
scanning resolution or other difficulties, the user can manually
match a scanned image of the form with the proper Empty Form
Image.
Processing
The Processing receives batches created by the Enterprise Portal
module (or from the FormId or the ManualFormId stations). This
station is one of the most important parts of Integra; it is
responsible for recognizing as much data as possible. The images
undergo image enhancement, automatic form recognition, form
removal, and optical character recognition.
Among the many unique features of this module, in conjunction

with the optional Full-Page OCR module, are separate
enhancement algorithms that can be applied to each field, and
powerful character recognition (OCR and ICR) that is achieved
by a sophisticated combination of recognition engines.
4
Content Validation
Completion
The Completion module receives data from the Processing
station. The exact data it receives depends upon the Visual
Designer definitions, but typically is invalid or unrecognizable
data. Unrecognized data is completed manually, with or without
the help of data dictionaries. The entire layout of the screen can
be customized for one or more stations.
Exceptions
Most forms have rules governing how various fields are filled in.
For example, one field may require digits only, while another
may require a valid address. Once these rules have been defined,
the operator cannot leave the data completion process until they
are obeyed. This can be a problem if an entry is illegible or
incomprehensible. The Exceptions module is designed to deal
with these cases. An Exception is a mark on the batch that allows
the operator to leave invalid data and advance to the next form.
The exceptions are reported later in the Exception Report. Batches
marked with exceptions will be sent to the Exceptions module.
Tile Validation
The Tile Validation module is used for mass validation and
decreasing the substitution errors of the recognition engines. The
module allows for the immediate viewing of recognition engine
results grouped in order by numeric and/or alpha characters. The
Tile module usually receives data produced by the Recognition
module, but can be applied anywhere in the system (using
Dynamic Workflow) according to the specific needs of each
project. Grouping the results by fields within flows, for example
by grouping machine-type and handprint fields separately, makes
it easier to spot false results and send them for correction in the
Completion module. Thus substitutions can be more quickly
eliminated.
Content Delivery
The Export module exports data to XML and to the common and
standard format, ASCII, and additionally exports both B/W and
color images. During run time, the Export module receives the
data, converts it to the defined format, and transfers it to the
export directory.
OCR Analyzer
The OCR Analyzer module calculates statistical data for Integra
form recognition. The statistics are prepared by comparing the
batch state after the Processing station phase (i.e. following
automatic recognition) with the batch state after the Export phase
(i.e. following human corrections). These statistics reflect the
success of the recognition (rejects and false positives) in terms of
several levels of recognition:
Form identification – FormOut! FeaturesID
Field recognition - the success of OCR per field
Character recognition - the success of OCR per character
5
eFLOW Enterprise Manager

The Enterprise Manager manages all the top level actions of the eFLOW
systems. Use the Enterprise Manager to create, copy and delete entire
applications, to set user security and monitor login permissions, and obtain
licensing and version information for eFLOW products.
Integra Component Breakdown

The input images are captured by the scanner interface and transferred to the
Content Recognition module. This consists of a general-purpose image-
processing module and an interface to multiple OCR, ICR, and OMR engines.
The results of these engines are processed by a voting mechanism. The final
results of the image processing and recognition process are sent, if necessary,
to data completion. The full results (recognized and completed) are then sent
to the Exceptions module, and then to Export directories. The stored data and
images can be retrieved at any time.
Figure: Integra Modules
6
Let us now look at a table with the basic objects and concepts of the design process:
Object/Concept Used for

Form A logical form is a structured document that includes one
or more pages to be filled with data.
Each logical form itself is a set of fields - the “blanks” in
which the information must be filled. Name, address, and
date are examples of such fields.
The term form in the Integra is a logical definition.
Empty Form Image, or Physically, a form can have several variations - a

EFI different logo, differences in the exact location or size of
the fields on the page, and so on.
While you might consider all these variations to be the
same physical form, the automatic imaging system does
not, and you therefore need to explicitly define all the
possible physical appearances of a specific form.
In Integra each physically distinct empty form is called
an Empty Form Image, or EFI.
Separator Batch separators divide scanned physical forms into

batches. Each is a distinct set of forms. Form separators
divide scanned pages into individual physical forms.
Separators can be either blank pages, TiS separator
forms, or can be set to a particular count of pages.
Application An application is a collection of flows, forms, fields,

exceptions, and so on that comprise a complete Integra
application. It includes electronic or scanned or filed
forms, OCR engines and virtual engines, rules and
validation functions, exceptions, EFI’s, user definitions,
and more.
Sometimes a single user site requires more than one
Integra application. This is no problem for eFLOW
platform - you simply define several applications in the
same installation. Each application contains its own
flows, forms, users, exceptions, etc.
7
The following diagram demonstrates the concepts of the logical parts (flows and forms) and
physical (EFI’s) parts of an Integra application. Notice that Flow 1 and Flow 3 use two
forms, while Flow 2 uses only a single form. Notice also that Form 2 is used in two flows,
both Flow 1 and Flow 3, and that Form 1 is associated with more than one EFI.
E F I1
E F I2 F o rm 1 F lo w 1
E F I4 F o rm 2
E F I4 F o rm 2
F lo w 2
E F I5 F o rm 3
E F I6 F o rm 4 F lo w 3
Figure: A Logical Application

In an Integra application, you define how many forms and flows you want, which EFIs you
want to attach to them, and how you want the data processed. You define which OCR
engines will be used to interpret the form entries, and what type of image enhancement and
form-removal parameters to apply to achieve the best results. You can group data items and
apply logical and arithmetic rules to ensure data correctness and quality, and to reduce the
number of exceptions that are returned to the operator for manual data completion.
The form documents to be processed may be obtained from a number of different sources:
they may be scanned, faxed, or taken from computer image files.
Sample applications have been supplied with the system in the directory “…\sample
Applications”, for use as reference applications. For your own work and tests, however, you
should create other applications.
Forms can be organized in several ways.
A batch is a set of forms (single or multiple pages) that are separated by a separator (a
specially designed page or a blank page). For example, if you want to group sets of 100
forms during input, then inserting a batch separator after such group will mark it as a batch.
A collection is the work unit, which is passed on to any station. A collection can be a batch
or subset of a batch and is defined in each station definition (in the DW designer).
8
Another way to understand the concepts of batches and separators is in terms of how they
are scanned in, as shown in the following diagram.
page
page
form
separator
page
page
form
form
separator
form batch
separator
form
form
form
separator
Figure: The Structure of a Scanned Batch
9
Chapter 2 Enterprise Manager
Overview
The Enterprise Manager manages all the top-level actions of the eFlow systems. Use the
Enterprise Manager to create, copy and delete entire applications, to set NT group and
user security, obtain licensing and version information or to simply switch between
applications. In the Visual Designer, the system integrator can define but not create an
application.
The Enterprise Manager performs several main tasks:
Allows you to create, copy, delete, duplicate and export applications
Sets the default application
Allows you to create and delete eFlow sites
Sets NT group and user security
Provides licensing information
Provides version information
Provides statistics setting per application
Sets autorun stations
The eFlow Domain Controller

The eFlow Domain Controller (EDC) contains a central database for an eFlow installation.
It functions similarly to the Windows Domain Server, as the designated server for the entire
application.
The EDC provides the ability to manage any workflow from any location, as long as that
workflow’s application is contained within the same domain. Previously, remote access to a
local workflow was conditioned on specific security clearance to the server.
The eFlow domain has three tiers. At the top level is the EDC, which is defined during the
installation.
The second tier in the eFlow domain is the local eFlow application server. Because the
EDC functions as a universal domain server, it has the ability to distribute and synchronize
tasks to its subservient servers. For example, let’s assume an EDC is located the United
States, while the company receives TIFFs from its branch servers in India, Britain and,
South America. If the US and Britain receive and process the most data, while India and
South America receive significantly less, then the EDC will reroute and redistribute the
flow so that the US and Britain receive a greater portion of cache memory. At the same
time, the processing of tasks at all stations is seamlessly synchronized, meaning that the
eFlow domain appears to complete all eFlow tasks simultaneously.
The lowest and final tier in the domain is the client or worker level. Any operator, with
sufficient security permissions, may access the Enterprise Manager locally and receive
node updates in real time. This operator-admistrator can view the status of all nodes in the
eFlow domain, including the EDC itself.
10
eFLOW Run Time Modules Manual Chapter 2 Enterprise Manager
Invoking and Using the Enterprise Manager

From the Windows Programs > TiS > eFlow menu, click the Enterprise Manager option,
or alternatively you can open the Enterprise Manager through the eFLOW4 system tray
icon.. The Enterprise Manager window appears:
Title Bar
Menu &
Tool Bar
Enterprise
Manager
Scope
Pane
Enterprise
Manager
Result
Pane
Status
Bar
Figure: Enterprise Manager main window
To create or delete a site (location where the application is used e.g. a

company office in a different city), click the eFlow Sites tree node to
display all the sites, which exist in the system. To the right, the Sites
Information Display Area will show the sites in list form. Right-click
on either the eFlow Sites node or on the specific Site to perform various
site-related tasks.
To create, duplicate or perform actions on an Application, click the
Applications tree node to display all the applications that exist in the
system. On the right, the Applications Information Display Area will
show the applications in list form. Right-click on either the Application
tree node or on the specific Application to perform various application-
related tasks. Right click on the Application and from the menu select
either New Application or Duplicate to create or duplicate the
application.
To view Version information, click TiS Files Versions.
11
Site Management
The same application can be used in different locations or sites in the eFlow system. The
Enterprise Manager allows you to add and delete sites.
Click the Sites Explorer tree node to display all the sites that exist in the system. To the
left, the tree will display the sites as tree nodes. To the right, the Enterprise Manager
Information Display Area will show the sites in list form:
To create a new site:

1. Select (click) the eFlow Sites node in the Sites Explorer tree. If you click the +
button to the left of the eFlow Sites node, you will get a listing of all the sites in
the system:
Sites
Explorer
T
Figure: Sites List

2. Right-click the eFlow Sites node and choose New Site from the drop-down menu.
Figure: New Site Installation Window

3. Enter a new name for the eFlow site in the text box.
12
4. Enter a brief description of the eFlow site in the text box.
5. Click OK.
6. A new site will appear in the eFlow Sites Explorer tree and in the Sites
Information Display Area:
Figure: New Site Created
Delete an eFlow Site

Note: This is an irreversible procedure! Make sure that you really want to delete a
site before you take this step.
To delete a site:
1. Right-click the site name in the eFlow Site Explorer.
2. Choose Delete from the drop-down menu.
3. You will be prompted to confirm that you wish to delete the site.
4. Click Yes, and the system will delete the site.
13
Applications Management
The Enterprise Manager allows you to create, delete, duplicate, and export applications. It
also allows you to select which application will be the default application in the eFlow
system.
Note:
eFlow allows for several applications to run in the system at the same time.
However, for the system to work properly, a default application must be selected.
Click the Applications Explorer tree node to display all the applications that exist in the
system. To the left, the tree will display the applications as tree nodes. To the right, the
Enterprise Manager Information Display Area will show the applications in icon or list
form:
Enterprise
Manager
Explorer
Enterprise
Manager
Information
Display Area
Figure: Applications List

To create a new application:
1. Select (click) the Applications node in the Applications Explorer tree.
14
Applications
Explorer
Tree
Figure: Applications List

2. Click the left-mouse button to obtain the application drop-down menu. Select the New
Application option.
OR
Click the Install new application button in the toolbar.
OR
Choose New Application from the File menu.
3. The New application installation window opens
Figure: New application installation window

4. Fill in the options according to the following table:
15
Choose… To…
1. Application Name 1. Enter a name for the application.

2. Overwrite 2. Click to mark this check box if you wish to
application override (write over) an existing application.
3. Keep existing 3. Click to mark this checkbox if you wish to save
collections the existing collections.
4. Set as default 4. Click to mark this check box if you wish to set
application this application as the default application..
5. Select existing 5. You must also provide a name and path for the
archive file .CAB file, a compressed file that contains an
application’s entire schema. Click the
Browse button to select the CAB file.
6.
Figure: Select archive file window
6. Import security info 1. Click to mark this check box if you want to
import all the roles, permissions and system
users’ definitions from the existing CAB file.
5. When you have finished making your selection, click Open. You will return to the New
Application Installation window.
6. Click the Next button to continue.
7. Select the application primary server .
8. Click the Next button to continue. The application is ready to be installed.
16
9. Click the OK button to commence application creation.
Figure: Progress window
A status bar will provide information regarding the current status of the application creation.
17
10. A new application will appear in the Application Explorer tree and in the Applications
Information Display Area:
Figure: New Application Created
18
Select the Default Application

eFlow allows for several applications to run in the system at the same time. You can start or
stop each one separately.
A default application must be selected. The Module Activator and the Controller will open
by default with the default application.
To set an application as the Default application:

1. Select the application in the Application Explorer.
2. Click the right-mouse button to obtain the application drop-down menu.
Select the Set as default application option.
Stop an Application
1. To stop an application, first select the application in the Application Explorer.
.
3. Select the Stop option.
OR
Click the Stop button in the Enterprise Manager toolbar.
OR
Choose Stop from the Application menu.
19
Set Autorun Stations

1. To set an application on autorun, first select the application in the Application
Explorer.
2. Right click on the Autorun Station icon, and select Add Autorun Station.
The New Autorun Station dialog opens:
3. Select the station for autorun.
4. Select the primary node that you want the station to run on.
5. Select the secondary node, if one exists.
6. Set command line parameters, if any.
7. Select the number of instances of the station to be run on the machine.
8. Click OK to record the settings.
9. To run autorun stations, in the Application Tree, select the application in which you
defined the autorun stations, right click and select Enable Autorun. The autorun
stations will begin running in the background.
20
Note: In order to run a station as autorun, you must have selected the following
station properties in the Visual Designer Object Inspector: StandBy and Allow
Unattended (checkboxes must be checked).
Delete an Application
Note: This is an irreversible procedure! Make sure that you really want to delete an
application before you take this step.
1. To delete an application, first select the application in the Application Explorer.
3. Select the Delete option. You will be prompted to confirm that you wish to delete
the application:
4. Click Yes, and the system will delete the application.
Duplicate an Application
1. To duplicate an application, first select the application in the Application Explorer.
3. Select the Duplicate option. The Duplicate Application Wizard will open.
Figure: Duplicate the Application screen

4. Fill in the options according to the following table:
Choose… To…
1. Application Name 1. Enter a name for the application
2. Set as default 2. Click to mark this check box if you
21
Choose… To…
application wish to set this application as the
default application.
3. Duplicate users 3. Click to mark this check box if you
security info want to duplicate all the roles,
permissions and system users’
definitions from the existing CAB file.
5. Click OK.
Export To CAB
1. To export a new application’s definitions to a CAB (compressed) file, first select the
application in the Application Explorer
3. Select the Export option.
OR
Choose Export from the Application menu.
OR
Click the Export current application button on the toolbar.
4. The Export Application window will open. You will be prompted to select a name
for the application’s CAB file:
5. Enter the path and name for the file and click Save. The system will produce a CAB
file for the application.
22
Security Management
eFlow allows you to define exactly which operator workstations, services, and roles will be
accessible throughout the application.
In the Enterprise Manager, you add users or groups from your network. You then use the
Visual Designer to define roles – administrator, supervisor, operator, etc. – and specify
which functions and stations can be accessed by each role. The last stage is to map NT
users from the Enterprise Manager to roles defined in the Visual designer.
By default every user has all permissions. However, as soon as you define an administrator
of a domain or an application, all other users lose all of their permissions. The administrator
must assign permissions to users and groups.
Defining NT Users/Groups in Enterprise Manager

The Enterprise Manager allows you to assign NT Users or Groups per application. You can
assign only one role per NT User or NT Group in the selected application. If no roles are
attached to users, everyone can perform all the actions in the application.
If you want to create a user group, which is different from those that already exist in your
domain or locally, you must first create the group using Windows Administrative Tools.
23
To add NT users/groups to a domain:

1. In the Application Explorer under Domain Configuration, right-click NT
Users/Groups. A drop-down menu is displayed.
2. From the drop-down menu, choose Add NT users/groups. A list of NT groups is

displayed.
Figure: New NT Users/Groups Dialog Box

3. From the drop-down list of network domains labeled Look in select the users or groups
to be initially defined as administrators. (Select the Show users checkbox to view user
names.)
4. Click Add. The name is added to the list in the box at the bottom of the dialog box.
5. Click OK. The new users or groups are added to the workspace.
6. In the drop-down menu on the right of the workspace, select a role for each user or
group listed.
24
7. Click the Apply Changes button.
Only those users defined as domain administrators can perform domain actions.
To add NT users/groups to an application:

1. In the Application Explorer under the application, right-click NT Users/Groups. A
drop-down menu is displayed.
2. Right-click NT Users/Groups. A drop-down menu is displayed.
3. From the drop-down menu, choose Add NT users/groups. A list of NT groups is

displayed. (Click to mark the Show Users check box to display a list of NT users.)
4. Type a name of a user in the text box or select a name from the list.
5. Click Add. The name is added to the list in the box at the bottom of the dialog box.
6. Click OK. The new user with its role is added under the NT Users/groups node.
Figure: New NT User
To delete a NT User or Group:

1. Select the user or group in the Application tree.
2. Right-click the user or group and select Remove selected users from
the drop-down menu.. The User/Group is deleted from the application.
25
Defining Roles and Permissions in Visual Designer

Before performing the procedures below, start the Visual Designer, by right-clicking the
eFlow tray icon and selecting Visual Designer or by selecting Start\Programs\TiS\eFLOW
4\Visual Designer.
The first step is to create a role for each group of users in your project. You can then assign
permissions for different project elements, by adding the relevant roles under the object
representing that element in the Application Tree.
To Create a Role in the Visual Designer:

1. In the tree pane on the left, scroll down to the bottom.
2. In the Security node, right-click the Roles object and select New Role.
3. A new object appears under Roles. Select it and define the relevant properties in
the Object Inspector pane on the right.
4. Add new permissions to the role. For each flow and station the options are Execute,
Read, and Write.
26
To Define New Permissions for a Project Element:

1. In the tree pane on the left, find and select the object for which you want to define
permissions
2. Right-click the object and select New Supported Permission.
3. Define the new permission type.

4. Create a new Role object that will use this permission.
Note: eFlow core checks permissions defined for Flows, Stations and certain eFlow services,
such as the WorkFlow engine.
If it is necessary to check permissions for Forms, Pages, Field Groups, and Fields, these
permissions should be set in the Visual Designer, and the customization code that will check
these permissions should be used.
27
Statistics Settings
Statistics are generated per application. You must first define the statistics settings for the application.
You can then generate and view the statistics using a statistics reporting tool of your choice.
Defining Statistics Parameters

To Define Statistics Parameters:
1. In the application tree pane on the left, find and select the Statistics icon. The
Statistics window opens in the workspace with the Statistics settings tab
selected.
2. Select the Enable Statistics checkbox.

3. Select the Data Storage Type from the drop-down menu of available databases.
4. Define the source and destination of the statistics.
5. Select the type of statistics in DataEntry, ManualFormID, CollectionAudit,
SessionAudit and Compare.
6. Click the Save settings button to save.
28
7. In the Cleanup Settings tab, you can change set the application to purge statistics
data after a given number of days, or perform a manual cleanup of statistics data
immediately.
29
Licensing and Version Information

Viewing Licensing Information
To View the contents of the active license file, or change active license
selection:
1. Right click on the Domain Configuration object, and select the
License > View or change active option.
The contents of the installed license will be displayed in the View License
window. There can be a maximum of two installed licenses on the same
machine: one installed on the HASP device, and one based on the HostId.
Only one of them can be active at any given moment.
2. To change the active selection, click the Set as active button.
Figure: Active License Information
30
The License Id, issue date, expiration date and features (name, quantity allowed and
quantity used) are available for viewing in the list view format.
The License Feature for a station is in the form ef[StationName]. A license is assigned to each
engine with a character-per-second (CPS) limit, so the engine license name contains this acronym.
Engine licenses come in the form OCR_CPS_[EngineName].
To View the contents of any license file:

1. Right click on the Domain Configuration object, select the License > View option.
2. Select a license file. This need not necessarily be the currently-installed license.
3. The contents of selected license file are displayed in the View License window.
Figure: License Information
31
Note: device name and device Id are not filled, as this view is not associated with a
specific device.
There are two types of license currently available: concurrent and total.
The Concurrent Counters value provides the number of simultaneous logins allowed for the particular
module or engine. For example, for efDesigner (the Visual Designer), five different users may
concurrently access the module at different computer stations. This limitation does not refer to the total
number of users, but rather to users simultaneously logged in.
All OCR engine license checking is done using a “supported characters-per-second” value provided for
each engine. The total required license must include a sum of all the CPS-s used by all OCR stations for
each OCR engine type. The OCR engine licenses also use concurrent counters.
Total Usage Counters (sometimes called “per click” counters) refer to the maximum number of actions
allowed. Currently, only the “PageCount” functionality is supported. It represents the number of pages
that may be processed by the system.
Viewing Version Information

To View Version Information:
1. Select (click) the TiS Files Versions object in the Application
Explorer tree.
2. All version information for eFlow products installed locally on the
current computer where the version information display is checked
will be displayed in the working area to the right. Version information
is provided including all the local filenames the version number, the
file creation date and time, and the size of file:
Figure: Version Information
32
Chapter 3 Introduction to Module

Activator
Overview
The Module Activator is eFlow’s central module. It is the interface to the run-time part of
the system and is responsible for linking all its various components. Through the Module
Activator, you can activate several eFlow modules, according to defined permissions, thus
controlling the flow of data in the system.
The module types that you can launch from the Module Activator include all runtime
stations defined in the Workflow Designer. In addition, it is possible to launch the
following modules:
Visual Designer
Freedom Designer
Smart Designer
Controller
These modules are discussed in depth in
From the Windows Programs > TiS > eFlow menu, click the Module Activator option.
The Module Activator window appears:
Figure: eFlow Module Activator window
33
eFLOW Run Time Modules Manual Chapter 3 Introduction to Module Activator
The Module Activator main window features a module panel. The module panel allows
activation of any of the available eFlow modules according to the user’s permissions. Use
the Controller to display information about the current session, and all system information.
Invoking the Controller

From the Windows Programs > TiS > eFlow menu, click the Controller option or
click the Controller button on the Module Activator toolbar. See Chapter 4 , The
Controller chapter for further details about the Controller.
34
Chapter 4 The Controller
About the Controller

While collections of forms await each successive processing step, they are stored
temporarily in lots composed of digital images and accompanying text data. The Controller
enables you to monitor these collections, showing you their status at the various run-time
modules and work-stations. Data can be viewed corresponding to a certain run-time
module, to a particular flow, or to work-stations. The Controller is color-coded to facilitate
identification, and displays information in one window providing an overview of all system
activity.
When you open the Controller and select any of the stations from the workflow, you will
automatically see a display of the list of collections associated with the station, and their
status. This is the Workload display mode. You can also view the status of all the
collections in the system, and the status of active stations.
The Controller is essentially a production line manager. The Controller receives and displays
online information about the status of the system. It can be used not only to monitor system
activity but also to detect problematic bottlenecks, and solve them.
35
eFLOW Run Time Modules Manual Chapter 4 The Controller
Controller Desktop Layout

Menu Bar
Tool Bar
Mode
Selecti
Mode-
Dependent
Display
Collection
or Station
Details
Status
Bar
Figure: eFLOW Controller
Using the Menu Bar

Five menus are accessed from the Controller Menu bar: File, Collection,
View, Options, and Help.
The File Menu

The File menu contains the following options and commands:
Option/Command Choose this to

Export Dynamic to Export dynamic archive (select a .Dynamic
Archive file).
Import Dynamic to Import dynamic archive (select a .Dynamic
Archive file).
Exit Close the application.
The Collection Menu

The Collection menu contains the following options and commands for
managing the forms in the system. Several commands apply to the selected
(highlighted) collection(s):
36
Option/Command Choose this to….

View Collection View a collection.
Hold Pause work on the collection(s). Work will stop on

these collections but the module will continue work
on collections in the queue.
Release Release selected collection(s) in the hold position.
Delete Delete the collection(s).

Delete All Delete all the collections in a particular station or in
the whole the system. Use this command with care!
Note: This command will delete ALL the

collections in all the modules in the system.
Once deleted, the collections cannot be
retrieved.
Prioritize Prioritizes collection(s).

Restore Priority Removes the priority mark and restores the
collection(s) to Normal priority.
Select All Selects all collections
Export to Export dynamic archive per station or per selected
Archive collection(s).
The View Menu

The View menu allows you to change the way that the controller displays
information:
Menu Option Choose this to….

or Command
Workload Show the system view in Workload mode.
The default display mode is the Workload
mode, which offers a general view of the
system. This view allows you to quickly
detect potential problems in the system.
(See the Workload Mode section later in this
chapter for more information about this view.)
Collections Show the system view in Collections mode. The

Collections mode is similar to the Workload
mode, except it shows the entire system from the
perspective of the processed collections. The list
is displayed on the left side of the screen,
showing all the collections in the system.
37

or Command
Stations Shows the system view in the Stations mode.
This mode shows the entire system from the
workers (typists) point-of-view
Viewer Shows the system view in the Viewer mode. This
mode allows the user to view overall system
usage and progress in large display to spot
problems with station thresholds.
Domain Shows the system view in the Domain mode.

This mode provides information for all active
applications under the eFlow domain: the number
of active stations, server status, and collection and
form counts.
Refresh Refresh the status display. Select to obtain current

system status settings.
Full Screen Maximizes the screen display.
The Options Menu

The Options menu allows you to configure the following settings:

or Command
Configure Controller settings define primary module,
station, system and collection workload settings.
See Controller Options for details.
Dynamic Selects a specific flow as the highest priority. All
Priority collections from this flow will then receive the
highest priority.
View Log Displays logger messages.
Information
The Help Menu

The Help menu allows you to display product and version information:

or Command
About eFLOW4 View version information
38
Using the Tool Bar

The tool bar provides tool shortcuts for accessing collection-related commands
and options. These commands can also be accessed from the Menu bar.
To find out the name of the button, place the cursor anywhere on the button. A
tool tip appears below it.
Figure: The Controller Tool Bar

Following is an explanation of the tools available:
Tool Choose this to….

View collection.
Pause work on the collection. Select a collection, then

hold it until further notice. Once you click on this tool,
work will stop on the selected collection(s) but the
module will continue work on other collections in the
queue.
Release a collection in the hold position.
Delete the batch.
Select an application for display using the list box.

This list box contains all the active applications defined
in the Enterprise Manager. You do not have to exit the
Controller and open the Enterprise Manager to move
from application to application. You simply select
another application from the list box.
Tool Choose this to….

Filter flows for display. Select the type of flows shown
using the drop-down list box.
This list-box contains all the types of flows defined in
the Application. It also contains the option to display all
the flows. If you select a specific flow type from this
box, only collections of this flow type will be displayed.
This selection affects all Controller view modes. If you
select “All Flows” – all collections of all types will be
displayed. “All Flows” is the first entry in the list-box,
and also the default setting.
Refreshes your screen to display updated workload.

Controller settings define primary module, station,
system and collection workload settings. See Controller
Options for more details.
39
Controller Options
Controller settings define primary module, station, system and collection workload
settings. To change the Controller options, select the Options menu > Configure options.
The Controller Options window appears:
Figure: Controller Options window – General Tab

The Controller options window contains three tabs. In the General Tab the following settings
can be defined:
Collection time in the system threshold (hours)

Select the maximum time a collection should remain in the system without the user being
alerted. When the collection is in the system more than the allotted time, the collection
entry will turn red in the list view.
Number of collections in system threshold
Select the total number of collections that the system may handle at any time.
Automatic refresh interval (sec)

Select the rate at which the Controller will refresh its information regarding system status.
The Queue Thresholds Tab allows the user to select the maximum number of forms that may
be held “waiting” in the system per station:
40
Figure: Queue Thresholds Tab

Max Forms In Queue
Specify per station how many forms may be held in queue for a specific station.
Min PPM (pages per minute)

Minimum pages processed per minute. If this minimum is not reached, the Controller
will display the problem in the Stations View of the Controller.
The Session Thresholds Tab allows you specify a minimum activity rate for each of the
run-time modules in a session:
Figure: Session Thresholds Tab

Min PPM (pages per minute)
Minimum pages processed per minute in a specific station. If this minimum is not
reached, the Controller will display the problem in the Stations View of the Controller.
41
Min Speed
Use the edit box to specify the minimum activity speed expected for per module (rate units are module-
specific: for example, forms per minute, typed characters per minute). If work proceeds at a rate slower
than the specified threshold rate, the Controller will display the problem in the Stations View of the
Controller.
For example, if the rate is lower than a pre-defined threshold such as the quota of 50 pages scanned per
minute, the rate bar is displayed in red - telling the Controller that there has been a slow-down at one of
the scanning stations. For more information about the Stations View, see page 44.
Mode Selection
The left side of the Controller Desktop contains a display mode selection panel. Select the desired
display mode by clicking one of the icons on this panel. The following five display modes are available:
Workload mode: provides a general overview of the status of all

the stations within the system.
Collections mode: displays the status of all collections within the

system.
Stations mode: displays the status of all Stations/users active in

the system.
Viewer mode: provides a basic workload view in large-scale, used

for distance watching.
Domain mode: provides for each active application the number of

active stations, the status of primary server, and the total number
of collections and forms.
42
Workload Mode
The default display mode is the Workload mode, which offers a general view of the
system. This view allows you to quickly detect potential problems in the system.
The workload view has three components:

System Overview
Work-stations running each run-time module
Collections waiting per work-station
Workflow Diagram
The upper part of the screen provides a general overview of the system in the form of a
graphical chart of the system architecture: the workflow.
Figure: Workflow Diagram

The icon in the upper right hand corner indicates a run-time module’s working/idle status. Working
status is defined as either:
Green – the run-time module is at work.
Yellow – the run-time module is idle.
Red - Not-responding. This indication is typically used in case of a computerized position (not typist), and
indicates a program or computer malfunction.
The number of collections and forms awaiting processing is indicated in numbers beneath the
run-time module. The number of collections appears on the left and the number of forms,
separated by a slash, appears on the right.
Underneath the run-time module, a load bar indicates whether the run-time module is working (white) or
paused (red).
Workload Run-Time Module Information

Select a run-time module by clicking on its tab in the Workflow mode. The bottom half of the Workload
Mode displays information regarding any selected run-time module. Once you select a run-time module, the
information in the bottom part of the window will change to reflect data pertinent to the selected run-time
module.
You may choose from two information display types: Collections and Stations. Select the display type
using the tabs above the table.
The borders between the top graph and the bottom table, are a movable split-bars. You may click and
drag them up or down, to gain more space for the upper or lower working areas.
43
Workload Collections View

The Collections table in Workload mode contains a list of all collections waiting to be processed by the
selected station.
Figure: Workload Collections View

Each line in the table represents one collection waiting to be processed by the station. The collections
are sorted, by default, according to their processing order. You may click on any column to sort the list
by another criteria.
The table contains the following columns:
Priority - a red flag in this column means that this collection has high priority, and will be processed
before non-priority collections.
Collection – Collection ID. This is the unique identification of the collection in the system.
Flow – The name of the flow to which the collection belongs. If a specific flow was selected in the
toolbar Flow Selection list-box, then only this flow will be displayed in the table.
Status – The status of the collection. Status may be one of the following:
Locked: the collection is currently being processed by one of the workstations.
Available: the collection is ready to be processed. It will be processed when some position will pick
it.
On Hold: The collection is placed on hold and must be released before it can be processed further.
A collection’s status may also be Undefined, for rare cases in which the system is not able to determine
the collection’s status.
Time in System – The elapsed time (hours:minutes:seconds)since the collection entered the system.
If this time is larger than a pre-defined threshold, it appears in red, indicating that this collection is
“stuck.” This situation tells the Controller to check why this collection hasn't finished after such a long
time. The time threshold is to be configurable at system setup.
User – for locked collections: which user is running the station on which the collection is locked
Machine – for locked collections: name of machine on which the locking station is running
Meta Tags – Information about the collection and specific fields in the collection; for example,
DateCreated, AnyBadPages, and MissingTotal.
Using the Collections Table

You may click a column title to sort the table by the column. You can also drag and drop individual
collections from the list to one of the modules in the chart, as long as the collection is in a compatible
format. For example, you may drag a collection that has undergone Processing back to the Manual
FormID station, or drag a collection that has reached the Completion station back to the Processing
station. But you cannot drag a collection from the Completion station to the FilePortal station.
44
Note: You cannot drag and drop a collection that has been split to another
module. (When a collection is split, forms are separated into different collections
that are individually processed/undergo separate Completion stages.)
You may not drag and drop a file from the Portals to another module, or from
another module to the Portals. The formats are not compatible. Files must
undergo Portal conversion before they become collections.
You cannot drag and drop locked collections, that is collections that are
currently running.
A drop-down mouse menu is available in the collections table via a right mouse click:
Figure:
Right Mouse Menu
The right-mouse menu allows you to quickly access the following commands: (Note that they are also
available through the toolbar and menu bar.)
Right Mouse Menu Use this menu item to

View Collection View a collection. See the last part of the chapter
regarding the use of the Collection Viewer.
Hold Pause work on the collection. Select a collection,
then hold it until further notice. Once you click on
this tool and then on a collection entry in any list,
work will stop on this collection but the module
will continue work on collections in the queue.
Release Release a collection in the hold position.
Delete Delete the currently selected collection.
Delete All Delete all collections.
Prioritize Prioritizes a collection.

Restore Priority Removes the priority mark and restores the
collection to Normal priority.
Export to Archive Export the list of collections in the queue into a

file for future use.
Select All Select all the items in the list.
Priorities
eFlow allows you to raise/restore the priority level of each collection in the system from the
dialog obtained by right-clicking on the collection or via the menu options.
45
Find Collections
eFlow allows you to search for collections on the system by means of the full or partial
collection name. To find a collection, click on the following icon:
Find Collections Button
Filters
eFlow allows you to define certain parameters for the list of collection items as well as the
meta tags that are to be displayed in the Collections Table. To define these filters, click on
one of the following icons:
Collections Filter Button
The Collection filter allows you to define a filter for the list of collections that are
displayed. If no filter is used, ALL the collections will be displayed. If a filter is used, only
the collections that meet the criteria defined will be displayed.
Figure: Collections Filter Dialog Box
In the Collection Filter dialog box, you can define the filter using an expression with the
following syntax: <name of the meta-tag> <logical operator> <value>. For example:
NumberOfForms = 4.
If more than one condition is required, each of them should be enclosed in parentheses and
AND or OR should be used to connect them. For example: (NumberOfForms> = 4) AND
(AnyBadPageOrForm = 0).
Notes:
Press CTRL + Space to open the drop-down list of meta-tags instead of
entering them manually. After selecting an item, press ENTER.
String values should be double quoted.
Boolean values should be 1 or 0 (1=true; 0=false)
Clear Filters Button
Use this button to delete all active filters from the system.
46
Modify Collection Columns Button
You can define which meta tag column will be displayed in the Collections table. The
default mode is when ALL meta tags are displayed. Meta tags that are removed will not be
visible in the table.
To modify the meta tag column, click on the Modify Collection Columns button.
The following dialog box is displayed:
Figure: Modify Collection Columns Dialog Box

To remove a meta tag from the list, select the meta-tag from the Visible MetaTags list and
then click the button. The meta tag now appears on the Available MetaTags list. Click
OK. The meta tag is no longer displayed in the Collection table.
To add a meta tag from the list, select the meta-tag from the Available Meta tags list and
then click the Add button. The meta tag now appears on the Visible Meta tags list. Click
OK. The meta tag is now displayed in the Collection table.
You may change the sequencing of visible meta tags in the collections table by selecting
from the Visible MetaTags list and using the up and down arrow buttons (to the right of the
list) to move the selected MetaTag to the desired position.
Click the Reset button to revert back to the original lists before changes were made.
47
Workload Stations View

This view provides you with concentrated information regarding of all the workstations running the selected
run-time module. It is typically used to monitor the performance of the different stations, particularly of
Completion station typists or Processing station progress.
Figure: Workload Stations View
Each line in the Stations View represents one logged-in instance of the selected run-time module. The
table contains the following columns:
Status - The status of the current station. The status icon may be one of the following:
Green - this position is currently working.
Yellow - this position is currently idle. In case of a manual (typist) position, this status tells the
Controller that this typist is not working.
Red - Not-responding. This indication is typically used in case of a computerized position (not
typist), and indicates a program or computer malfunction.
User – The name of the user logged-in on this station.
Machine Name - The name of the computer.
Station Name - eFlow station name.
Quality – The quality of work in the station. For example: quality of recognition in Processing station
(recognized pages percentage).
Speed – The speed of the collection at the station.
Current PPM – Current rate of pages per minute at the station.
Average PPM – Average rate of pages per minute at the station.
You may click on a column title to sort the table by this column.
48
Collections Mode
This mode shows the entire system from the perspective of the processed collections. It
shows all the collections currently in the system, and allows the Controller to check the
status of each collection.
Figure: Collections Mode
You can filter the collection data by specific values via the drop-down list in each column heading, and
using the (Custom) option in the drop-down list you can define a customized filter for the data:
Figure: Custom Autofilter
49
Collection Parameters
Priority - a red flag in this column means that this collection has high priority, and will be processed
before non-priority collections.
Collection – Unique ID of the collection.
Flow - Name and icon of the flow to which the collection belongs. If a specific flow was selected in the
Flow Selection combo-box, then only this flow will be displayed in the table.
Status - The status of the collection. May be one of the following:
In process: the collection is currently being processed by one of the workstations. The name of the
workstation appears next to the icon.
Ready: the collection is ready to be processed. It will be processed when some position will pick it.
On Hold: The collection is placed on hold and must be released before it can be processed further.
Status may also be undetermined.
Time in System - the elapsed time since this collection entered the system. If this time is larger than a
pre-defined threshold, this number is displayed in red.
Meta Tags – Information about the collection and specific fields in the collection; for example,
DateCreated, AnyBadPages, and MissingTotal.
50
Collection Mode (Chart View)

This representation shows the same information as the Collection Status table, displayed on top of a
chart graph of the system architecture. This representation also allows you to see where specific
collections are currently located in the eFlow system. Simply click any collection in the collection list,
and an icon signifying the working status of the collection will appear under the module where the
collection is located.
User clicks on a batch The location of the batch (the module

number to select it. at which the batch is located) is
shown in the chart.
Figure: Collection Mode Chart View
51
Stations Mode
This mode shows the entire system from the workers (typists) point-of-view. It allows the Controller to
monitor the performance of all typists.
Figure: Station Mode

The table offers a list of all typists logged in at each of the stations. Each line in the table contains the
following information:
Status - Name of the current work station and its working status, which is one of the following:
Green - this position is currently working.
Yellow - this position is currently idle. In case of a manual (typist) position, this status tells the
Controller that this typist is not working.
Red - Not-responding. This indication is typically used in case of a computerized position (not
typist), and indicates a program or computer malfunction.
User - Name of typist logged-in to the work station.
Machine Name – Name of the computer running at the station.
Station Name – Name of the eFlow station.
Quality – The quality of work in the station. For example: quality of recognition in a Processing station
(percentage of recognized pages).
Speed – The speed of the collection at the station.
Current PPM – Current rate of pages per minute at the station.
Average PPM – Average rate of pages per minute at the station.
You may sort the table by each of the columns by clicking on the column header.
Note: It is possible to kill the process/logout of a station that is having trouble

processing or is not responding at all. This would be signified by a Rate that
appears in the red zone, alerting the user that the station is performing under the
minimum threshold rate. To logout of a station, select the station that you would like
to close. Use the drop-down right mouse menu to select the Logout Station
command. The station will log out and close.
52
A drop-down mouse menu is available in the collections table via a right mouse
click:
The right-mouse menu allows you to quickly access the following commands:
Right Mouse Menu Use this menu item to

Logout Station Request a station logout, or disconnect it from
server.
Logout may be done orderly or immediately, or in
case of a station that is not responding at all, it may
be disconnected from server at once.
Send Message Send a textual message to the station. The station
will receive the request and display the message to
the user.
Properties Display the station’s properties: station name,

station type, machine and user information, login
time and process id.
Viewer Mode
Viewer Mode allows the user to view overall system usage and progress in large display. You can use
this view to immediately spot problems with station thresholds. For example, if not enough stations are
working to perform FormID and Processing, the Viewer Mode display will indicate this.
Figure: Viewer Mode
This mode shows the following information:

Name - station name
Status – station status (Working/Idle)
53
No. of Instances – number of current runs of the module

No. of Forms – total number of forms over all instances
Current PPM – average pages per minute
Time Left (min.) – the estimated time left for the station to finish processing the collections
Station Load Bar

Where the Load exceeds the threshold, the un-handled collection load is displayed in red.
This is an indication of an over-load situation, which may result in clogging of the system.
This indication signals the System Administrator to add more workstations to the over-
loaded station.
Domain Mode
Domain Mode allows the user to view overall status of the applications on the eFLOW
domain:
Figure: Domain Mode
54
The Collection Viewer

The Controller tool bar provides a shortcut for viewing the collection images. In the
Collection list, right-click the collection you wish to display. The Collection Viewer
window opens and displays the image of the first form’s image in the collection:
Figure: The Collection Viewer
Using the Menu Bar

Five menus are accessed from the Collection Viewer Menu bar: File, Page, Zoom,
Window, and Help.
The File Menu

The File menu contains the following options and commands:
Option/Command Choose this to…

Open Open (view) a collection’s image file.
Print Print the image file.
Printer Setup Adjust printer settings.
Exit Exit the Collection Viewer.
The Page Menu

The Page menu contains the following options and commands for paging
through the collection:

Move one page forward in collection.
Move one page back in collection.
Jump to the beginning of the collection.
Jump to the end of the collection.
55
Rotate right.
Rotate left.
Reconstruct Reconstruct the original scanned image.
Options Use a browser to search for an EFI.
The Zoom Menu

The Zoom menu allows you to change the way that you view the image:
Option/ Choose this to….

Command
Zoom In Shrink/enlarge the image display by 10%.
Zoom Out
Fit to Height Shrink/enlarge the image to fit to the dimensions
Fit to Width of the viewer.
Default Size Restore the default size.
The Window Menu

The Window menu contains the following options and commands:

Tile Tile the open image files in the
viewing area.
Cascade Cascade the open image files in the

viewing area.
Arrange All Arrange the open image files in the

viewing area.
Hide Hide the open image files.
56
The Toolbar
You can locate collection images, enlarge or shrink an image for viewing efficiency,
and print the image by using the following buttons.
Tools This tool is used to/as…

Open an image collection file.
Print the current image file.
Use these buttons to page through the form.

Click the left most button to return to the first page.
Click the right most button to jump to the last page in
the form.
The two middle buttons are used to move one page
backwards or forwards, respectively. The page location
in the form is displayed in the central display box.
Zoom Out tool. Shrink the image display by 10%.
Actual Size tool. Return the image display to 50%

display.
Zoom In tool. Enlarge the image display by 10%.
Rotate Image tool. Rotates the image. Each click

rotates the image clockwise by 90°. Note that this
rotation is not retained in the image file.
Reconstruct Form tool. Reconstructs the original

scanned image.
The ROI Menu Bar

Examine the ROI’s that are attached to the image that you are
studying using the ROI menu bar options.
ROI Menu Use this menu item to…

Bar
All Show all ROI’s in the image.
None Do not show any of the ROI’s in the image.
Removal Show all the Removal ROI’s in the image.
OCR Show all the OCR ROI’s in the image.
FormID Show all the FormID ROI’s in the image.
57
58
Chapter 5 Input - Getting Started
Overview
eFLOW Portals provide data input to the system from two possible sources. Using the
Scan Portal, you can scan forms. Use the File Portal to select previously scanned forms
from existing image files.
Note: If you choose Scan Portal input, make sure you are connected to a scanner
before you begin.
Features
eFlow Scan Portal module supports all ISIS-standard scanner types. It also supports
multipage TIF files, color scanning, grey scale scanning, and black and white.
Activating the Portal Modules

The Portal modules can be activated through the Module Activator, by a user who has
permission to access the Enterprise Portal modules. For more information on the eFlow
Module Activator, refer to Chapter 2 Enterprise Manager of this manual.
The Module Activator icons indicate the type of input you can select:
Scanning
Automatic gathering from prepared image files
Select the desired input type and click the appropriate icon.
59
Chapter 6 Scan Portal

The main purpose of the Scan Portal module is to scan collections, which are then entered
into the system.
For full details on using the Scan Portal see the online Help for the Scan Portal. (The Scan
Portal has yet to be documented.)
60
Chapter 7 File Portal
Overview
The File Portal allows you to select existing image files as your input data. The process
involves choosing one or more files from the list of available image files in a directory and
sending them onwards to the next queue.
For full details on using the File Portal see the online Help for the File Portal. (The File
Portal has yet to be documented.)
61
Chapter 8 Page OCR
Overview
The Page OCR station receives Collections and creates a PRD (page-recognition data) file
for each page in the TIF.
By using this station the user can separate the two processes done by the FreeMatch station:
creating PRD files and running Freedom scripts. When the PageOCR station is run before
the FreeMatch station, FreeMatch will not create PRDs for the collections, and will run the
Freedom script(s) immediately, using the PRDs created in the PageOCR station.
Getting Started
Activating the Page OCR module Main Window
The Page OCR station can be activated through the Module Activator only by a user who has
permission to access the Page OCR module. For more information on the Module Activator,
refer to Chapter 2 Enterprise Manager of this manual.
It can also run in Unattended mode.
To invoke the Page OCR module:
From the Module Activator, click the Page OCR module icon. The following window
appears:
Menu
Bar
Toolbar
Page OCR
Progress
Log
Original
Image
Viewer
Status
Bar
Figure: Page OCR Main Window

When you click the Run button, the Page OCR module retrieves a set of collections and
automatically starts to process the first collection that has “waiting” status in the Page OCR
queue.
62
eFLOW Run Time Modules Manual Chapter 8 Page OCR
The maxworkunits parameter defined in the Design stage (Visual Designer) determines
how many collections are retrieved for processing in each “Run”.
During processing, the page undergoing processing in the TIF file is displayed (by default,
on the right side of the screen). In addition, you can navigate via the interactive progress
log on the left which is created during processing, by clicking on the desired page. (Clicking
on the entry for the entire collection causes the first page in the collection to be displayed.)
During a run, the Progress Log first indicates that “Collections were locked”, and displays
the current collection number and, for each page, the page number and recognition rate:
average of confidence level of all words in the PRD.
If there is an error, the Progress Log displays an error message in red. If a run is aborted,
the log displays “Collections were discarded”.
After processing of the last collection (as specified in MaxWorkUnits) is complete, the
Progress Log indicates that collections have been freed for subsequent processing
(“Collections were sent to next station”). The log is cleared for every new Run.
The Status Panel

• At the left, a rectangle displays Processing status.
• At the right, the following is displayed:
o PPM rate (pages per minute)
o Currently-processed page number and total page count
o Time of day.
The Menu Bar

The Page OCR menu bar contains the following options:
Button Purpose
File Use the File menu to
Run: get the next set of available collections for processing
Pause/Resume: Temporarily stop processing of the current
collection, and resume a paused session
Abort: Stop processing of the current set of collections and discard
any changes
Exit: exit the Page OCR module.
Edit Use the Edit menu – Clear Log Messages – to clear the Progress Log.
View Use the View menu to select which information is displayed in the
central working area. You may toggle display of the Report of the
Processing progress, which will appear to the left, and the Image
File being processed, which will appear to the right.
63
Button Purpose
Options Use the Options menu to:
Standby – enter/leave stand-by mode

Reset Statistics - reset the statistics displayed
View Log Information – opens the logger window
Disable Events - prevent triggering of CSM events
Zoom Use the Zoom menu to zoom in or out in 10% increments, or to

select the clarification level at which you will see images files
displayed (20%, 50%, 70%, 100%, or 200%).
Help Use this command to open online help for the station.
Zooming Into/Out of an Image

The page image can be zoomed into/out of in several ways:
• Slider in toolbar: 20% to 200%
• Toolbar buttons: In, Out
• Menu bar options: In, Out, specific increments.
Page OCR Toolbar

To find out the function of the button, place the cursor anywhere on the button; a tool tip
appears below it.
The Page OCR module toolbar contains the following buttons:
Button What it does

|
Use this option to initiate the Page OCR process. The log of
the previous Run is cleared before this process starts.
Use this option if you want to temporarily stop OCR

processing. The process is stopped only after it finishes a
page. After Pause is pressed, the Pause button becomes
depressed, and pressing Restart resumes processing from the
page where it was stopped.
Use this option to return the set of collections to the Page OCR
queue untouched. As in Pause, the process is stopped only
after it finishes a page.
Use this option to zoom in, using 10% increments.
Use this option to zoom out, using 10% increments.
64
Manual or Standby Processing

This station can be run in manual or Standby mode.
Manual Operation
If the Options > StandBy menu option is not checked, the OCR process can be initiated
manually in one of two ways:
From the Page OCR toolbar, click the Run button

OR
Select Run in the File menu.
After the set of collections is processed, the station is idle until you issue a new Run
command to request a new set from the station queue.
Automatic Operation
Processing can also be invoked automatically.
If you set the Process > StandBy menu option, Page OCR continually polls to see if there are
collections in the queue, and will fetch a set of collections and start processing it as soon as
it detects it in the station’s queue. See the StandByInterval propery specified in Visual
Designer regarding how often the queue is polled.
65
Chapter 9 Content Recognition -

Processing
Overview
The Processing module can perform both form identification and field content Processing.
Although separate Integra modules exist to perform form identification, it is not necessary
to run them previous to imputing image files to the Processing module.
Image files may be received from an Enterprise Portal module, the FormID module, or the
Manual FormID module. After receiving the image files, the Processing module processes
them and then sends them together with the text results to the Completion queue or any other
queue specified in the workflow.
The Processing module

This run time module is one of the most important parts of Integra, since this process is
responsible for recognizing as much data as possible, leaving unrecognizable data for the
much slower, manual Completion process.
Processing Stages
Processing involves the following stages:
Form image enhancement
Form identification and removal
Field image enhancement
Field segmentation
Optical character recognition (OCR) and/or intelligent character recognition (ICR)
Voting for optimal results
66
eFLOW Run Time Modules Manual Chapter 9 Content Recognition - Processing
Getting Started
Activating the Processing module Main Window
The Processing window controls the operation of the image Processing engine. It can be
activated through the Module Activator only by a user who has permission to access the
Processing module. For more information on the Module Activator, refer to Chapter 3 of this
manual.
To invoke the Processing module:
From the Module Activator, click the Process module icon. The following window appears:
Menu
Bar
Toolbar
Recognition
Progress
Report
Original
Image
Viewer
Status
Bar
Figure: Processing Module Window
When you click the Run button, the Processing module automatically starts to process the first
batch that has “waiting” status in the Processing queue.
The Status panel
Left rectangle - Processing status.
Right rectangle –Time of day displayed (from the last time that the CPU was available).
The Menu bar

The menu bar contains the following options:
Button Purpose
File Use the File menu to exit the Processing module.
Edit Use the Edit menu to Copy report information, Select All the report
information, or Clear the report information. These commands also
can be activated using standard Windows keyboard shortcuts.
Search Use the Search menu to Find specific information in the report, Find
Next (find the next identical piece of information in the report), or
Go to line (jump to a particular line in the log). These commands
also can be activated using standard Windows keyboard shortcuts.
67
Button Purpose
View Use the View menu to select which information is displayed in the
central working area. You may toggle display of the report of the
Processing progress, which will appear to the left, and the image
file being processed, which will appear to the right part.
You may also choose to display the debug log, which appears in a
separate window.
Further, it is possible to select which report items will be shown:
Show All
Show Pages and Final Results
Show Pages only
Button Purpose
Process Use the Process menu to initiate the OCR process. Select Go to
start, Pause, Abort or Standby. These commands can also be
activated using the toolbar buttons.
The command Run can also be activated using the keyboard
shortcut F5. Pause is activated using the keyboard shortcut Shift-
F5.
Zoom Use the Zoom menu to select the clarification level at which you
will see images files displayed.
Options
Use the Option to:
Standby – enter/leave stand-by mode
Report font – select the report font
Reconstruct image – reconstruct the image file
Reset Statistics - reset the statistics displayed
View Log Information – opens the logger window
Debug Script - use this option to debug custom events
Help Use this command to open the Integra Processing online help.
68
Processing Toolbar
To find out the function of the button, place the cursor anywhere on the button; a tool tip
appears below it.
The Processing module toolbar contains the following buttons:
Button What it does

Use this option to initiate the OCR process.

depressed, and pressing it again resumes the Processing from
the page where it was stopped.
Use this option to return the batch to the Processing queue

untouched. As in Pause, the process is stopped only after it
finishes a page.
Use this option to zoom image display in increments.
69
Initiating the OCR Process

Manual Operation
You can initiate the OCR process manually in one of three ways:
From the Integra Processing window, click the Run button

OR
Press the keyboard shortcut F5.
If the default workflow configuration is used, and there are no errors and no data needs to
be filled in manually, the batch continues on to the next queue, for example, the Export
queue. Otherwise (if some data needs to be filled in manually), the batch is sent to the
Completion queue.
If there is an error, the report and Status Bar display an error message. If you try to reprocess
the batch without correcting the error, the report will repeatedly display an error message
until the error is corrected.
Automatic Operation
Processing is also invoked automatically by making the appropriate definition in the Options
menu. If you set the Process menu, StandBy option,” Integra will fetch a batch and start the
Processing process for the batch as soon as it appears in the Content Processing queue.
70
Chapter 10 Content Recognition - Form ID
Overview
The FormID module performs form identification only. It is not necessary to run the FormID
module separately, as form identification can also be accomplished by the Processing
module. However, in the case of extremely heavy work load or many problematic forms
which are difficult to identify, it may be useful to have forms identified first through the
FormID module, with unrecognized forms processed through the Manual FormID module, and
field contents then recognized through the Processing module.
Image files may be directly received from an Enterprise Portal module. After receiving the
image files, the FormID module rapidly identifies them and then sends them to the Processing
queue, or any other queue specified in the workflow.
The FormID module

This run time module is one of the most efficiency-improving parts of Integra, since this
module is responsible for identifying forms as quickly as possible, leaving unrecognizable
forms for the slower, manual Manual FormID process.
FormID involves the following stages:

71
eFLOW Run Time Modules Manual Chapter 10 Content Recognition - Form ID
Getting Started
Activating FormID
The FormID window controls the operation of the FormID module. It is activated through the
Module Activator only by a user who has permission to access the FormID module. For more
information about the Module Activator, refer to Chapter 3 of this manual.
To invoke the FormID module:

From the Module Activator, click the FormID module icon. The following window appears:
Menu
Bar
Toolbar
Recognition
Progress
Report
Original
Image
Viewer
Status
Bar
Figure: FormID Module Window
72
When you click the Run button, the FormID module automatically starts to process the
first batch that has “waiting” status in the FormID queue.
The Status panel

Left rectangle - FormID status.
The Menu bar

Button Purpose
File Same as for Processing module.
Edit Same as for Processing module.
Search Same as for Processing module.
View Same as for Processing module.
Zoom Same as for Processing module.
Options Same as for Processing module.
Help Use this command to open the Integra FormID online help.
For information about the Debug Logger, see Chapter 19 .
73
FormID Toolbar
The FormID module toolbar contains the following buttons:
Button What it does

Use this option to initiate the FormId process.
Use this option if you want to temporarily stop FormId

highlighted, and pressing it again resumes the FormID
from the page where it was stopped.
Use this option to return the batch to the FormID queue

finishes a page.
Initiating the Form Recognition Process

Manual Operation
You can initiate the FormId process manually in one of three ways:
From the Integra FormID window, click the Run button

OR
From the menu bar, select File > Run.
OR
be filled in manually, the batch continues on to the Processing queue. Otherwise (if some
data needs to be filled in manually), the batch is sent to the Manual FormID queue.
Automatic Operation
FormID is also invoked automatically by making the appropriate definition in the Options
menu. If you set the Options menu StandBy option, eFlow will start FormID a batch as soon as
it appears in the FormID queue.
74
Chapter 11 Content Recognition - Manual

Form ID
Overview
The Manual FormID module is used to manually perform form identification for those forms
whose scanned images may be difficult to read or cut off, and cannot be identified
automatically.
Forms may fail to be identified for a number of reasons. A particular form may have been
scanned slightly to the left or right, meaning that the placement of identifying fields is in
the wrong space. Or, one or more pages in a form may have poor scanning resolution.
The Manual FormID module offers useful tools to resolve these difficulties, quickly and
simply. Using the Manual FormID module, it is possible to in fact shift the location of all
identifying fields to compensate for shifted scanning. Or, if only one or more pages in a
form have scanned poorly, it is possible simply to associate a page correctly with the form
that it belongs to.
Image files are received from FormID module, or even the Processing module. After
receiving the image files, the Manual FormID module allows the user to use different tools
and viewers to identify the pages and forms. Identified forms may then be sent to the
Processing queue or any other queue specified in the workflow.
The Manual FormID Module

This run time module is responsible for providing a manual option for recognizing
unrecognizable forms so that they may be processed appropriately.
Manual FormID involves the following stages:

75
eFLOW Run Time Modules Manual Chapter 11 Content Recognition - Manual Form ID
Getting Started
Activating the Manual FormID module Main Window
The Manual FormID window controls the operation of the image Manual FormID module. It is
activated only through the Integra Module Activator by a user who has permission to access
the Manual FormID module. For more information on the Module Activator, refer to Chapter 3
of this manual.
To invoke the Manual FormID module:

From the Module Activator, click the Manual FormID module icon. The following window
appears:
Menu
Bar
Tool
Bar
Page
Information
Area
Default
Action
Button
Status
Bar
Figure: Manual FormID Module Window
The Status panel

Left rectangle – Manual FormID status.
76
Manual FormID Menu Bar

Five menus are accessed from the Menu Bar: File, View, Actions, Navigate and Image.
The File Menu

The File menu contains the following commands. Most of these commands can also be
activated using the toolbar.

Get Fetch unidentified forms.
Unlock Return the batch to the Manual FormID queue untouched.
Send After you have identified the form, send the form back to
the next queue.
Save all Save the changes to the form.
Undo all Undo last action.
Reject Reject the Manual FormID module.
Exit Exit the Manual FormID module.
The View Menu

The View menu contains the following commands:
Option/Command Subcommand Choose this to…

TIFF Windows Tile Horizontally Toggles the view of the TIFF
page at work horizontally.
Tile Vertically Toggles the view of the TIFF

page at work vertically.
Full Screen Toggle to open the Manual

FormID module to a full-screen
desktop.
The Actions Menu

The Actions menu contains the following command:

Accept the default EFI Accepts the default electronic form image.
77
The Navigate Menu

Use the Navigate menu to select the following options:

Select bad page Select a bad page. Jump from bad page to bad page.
Next problematic Jump to the next bad form.

form
Previous Form Jump to the previous form viewed.
Next Form Jump to the next form you wish to view.
The Image Menu

The Image menu contains the following commands:

Zoom In Use these options to zoom the viewer of the original
Zoom Out image. The Zoom In and Out options are also available
through the toolbar.
Zoom Default
Zoom Best Fit
Rotate Left Rotate the image to the left or the right.

Rotate Right
Flip Flips the image.
The Options Menu


Enable Modifying See the section entitled Overriding FormID identification
Auto-Ided pages later in this chapter.
View Log Specifies when custom Scripts should be debugged. It can

Information be opened to track any problems with the Manual FormID
module performance or Integra Content Processing.
Debug Events Use the Debug Events option to debug custom Events.
Disable Events Use the Disable Events option to disable all the custom
events
The Help Menu

Use this command to open the Integra Manual FormID online help.
78
Manual FormID Toolbar

The Manual FormID module toolbar contains the following buttons:
Button What it does
Fetch unidentified forms.
After you have identified the form, send the form back to the next
queue.
Return the batch to the Manual FormID queue untouched.
Save the changes to the form.
Undo last action.
Select a bad page. Jump from bad page to bad page.
Jump to the next bad form.
If a station discards any batch or form it will be sent to the rejected

collections queue. It is possible to drag it from the rejected
collections queue to one of the stations and try to process/run the
collection again. Or, it is possible to delete the rejected collection
completely from the Integra system.
Initiating the Manual ID Process

Forms may fail to be identified for a number of reasons. A particular form may have been
scanned slightly to the left or right, meaning that the placement of identifying fields is in
the wrong space. Or, one or more pages in a form may have poor scanning resolution.
Initiate the FormID process as follows:
1. From the toolbar click the File Get collections button,

OR
Click the Get button in the information area.
Note: This button will automatically change its functionality to provide the
appropriate next step for each procedure in the manual form-ID process.
79
Page
Information
Get/Send
Button
Figure: Current Form Pages Information Area
2. The first batch waiting in the queue will be fetched. In the Page Information area, a
listing of the pages in the first form in the sequence will appear.
3. The original image will appear in the window to the right, as in the following figure:
Original
Image
Viewer
Figure: Unidentified Form

4. Using the Original Image Viewer at the right you may identify the form. See the next
section for further information.
5. Using the information in the Page Processing Information Area, you can solve a
number of different problems. You may select the form to which the page belongs,
correct the page order, and specify the correct EFI or status for the page. See the
following sections for further information.
80
Using the Original Image Viewer to Identify a Form

The original image of the first page of the form will be displayed in the Original Image Viewer
at the right. You may use the zoom and pan keys to look at the image more closely to help
you identify which form it belongs to.
To pan the image:

Either use the scroll bars OR place the cursor on the image and hold the mouse button
down. The cursor turns into a hand. Drag the hand in the desired direction.
The Zoom Controls

The View > Zoom In/Zoom Out options and the Toolbar zoom commands allow you to control
the size of the original form image in the Original Image Viewer. The Toolbar contains the
following options:
Button What it does
Magnifies the image
Shrinks the image
81
Identify the Form

Specify the Form
Examine the image in the Original Image Viewer to identify the form. Once you have
identified the form correctly, you must specify to Integra which Form the Page belongs to.
1. Select a form from the Form List, at the top of the Page Processing Information
Area.
2. Click any form to select it.
3. If there is only one form in the flow, only one choice will be available, as in the
following figure:
Figure: Form List
Identify the Page

Once you have associated the form correctly, you must specify to Integra which EFI
(empty form image) each Page should be associated with.
You may move between pages by selecting them in the Page Processing Information Area
Page column. Simply click a page row to select it.
Page Page Master

Colum Order Form
Figure: Page Information Area

Page Selection Arrows
The Page Selection arrows on the toolbar allow you to:
Go to the next bad page.

Go to the next bad form.
Page Processing Information Area Information
The Page Processing Information Area provides information about the pages in the form,
their order, and whether or not they have been identified.
82
In the Page column, the image order of the pages within the current form’s image file is
provided.
In the Order column, the logical Integra order of the pages within the form is specified.
In the Master column, the EFI with which the page is identified is specified.
Change Incorrect Page Order

Pages may have been scanned in the wrong order. For example, pages two and three of a
particular form may be switched. Using the Original Image Viewer you may notice that the
pages are listed in an incorrect order. Change the ordering as follows:
1. In the Page Processing Information Area, click the page entry that you want to
change.
2. Click once in the Order column to reveal the drop-down list box.
3. Select the correct page number for the page.
Note: If only the number 1 is displayed in the Page Order Column, there is only
one page in that form.
Identifying the Correct Page EFI

If any of the pages have already passed through the FormID successfully, the EFI will be
identified in the Master Form column.
Although a form may be correctly identified, one or more of the form pages may have
failed identification. For example, pages 1 and 3 of a particular form may be identified
correctly, and associated with the right EFI. But page 2 may remain unidentified. Using
the Original Image Viewer you may determine which EFI is the correct one for the
unidentified page.
To select the correct EFI:
change.
2. Click once in the Master Form column to reveal the drop-down list box.
3. Select the appropriate EFI for the page.
83
4. The EFI will be displayed in the EFI Viewer in the bottom left. If you have made an
incorrect EFI selection, simply reselect the appropriate EFI from the Master Form
drop-down list box.
Figure: EFI viewer
84
Errors
If there is an error in activity, the Status Bar displays an error message. If you try to
reprocess the batch without correcting the error, the report will repeatedly display an error
message until the error is corrected.
Correcting Field ROI Placement
When you examine the image of a page/form in the Original Image Viewer, you may find that
the image is right- or left-shifted, or that the fields and OCR field regions (ROI’s) are
misaligned. (For more information about ROI’s, please see the Application Visual Designer
manual). During scanning, it may be that the form was misplaced to the left or right of
center into the scanner feeder tray. This may be why the form could not be identified, and
could also cause problems later in identifying the contents of various fields, as the ROI’s
may not be correctly located.
The Manual FormID module offers an important feature to correct field placement errors.
If the form has unsuccessfully undergone automatic FormID identification (otherwise

called AutoID), correcting ROI’s is a very simple procedure, and you may adjust ROI
placement as necessary:
1. Scroll through the image by using the scroll bars or place the cursor on the image
and hold the mouse button down. The cursor turns into a hand. Drag the hand in the
desired direction.
2. Select a field and move it to the correct location. All other fields will be moved at
the same time to the new location.
If the form’s ROI placement cannot be changed, than it probably has successfully been
AutoIDed. In this case, see the next section for information on how to override the
automatic identification settings.
Overriding FormID identification

If the form has passed through the Processing or FormID module, it may have
successfully undergone automatic FormID identification (AutoID). However, in spite of
being correctly identified, you may still find that the image form is shifted right or left, or
that the fields and ROI’s are not precisely aligned. This may cause problems later in
identifying the contents of various fields, so it is important to change the AutoID results.
In order to move the ROI’s you must first enable Integra to override the automatic
identification results. Then you may adjust ROI placement as necessary. To do this:
1. Select the Options menu > Enable Modifying AutoID Pages selection.
2. You will be prompted to confirm that you wish to override the automatic
identification system.
3. You may scroll through the image by using the scroll bars or place the cursor on the
image and hold the mouse button down. The cursor turns into a hand. Drag the hand
in the desired direction.
4. Select a field and move it to the correct location. All other fields will be moved at
the same time to the new location.
5. To disable any further changes, select the Options menu > Enable Modifying AutoID
Pages selection again.
85
Send
When you have finished identifying the pages, click the Send button, or select the File
menu > Send selection, to return the identified form to the next queue.
Save
Click the Save button, or select the File menu > Save selection, to save the identified
form.
Discard
Click the Discard button, or select the File menu > Discard selection, to return the form to
the Manual FormID queue.
86
Chapter 12 Free Match
Overview
The Free Match module performs form identification only. Image files may be directly
received from an Enterprise Portal modules or from the OCRPage station. After receiving the
image files, the Free Match module rapidly identifies them and then sends them to the
Recognition queue, or to the Manual Match station if fields are incomplete.
The Free Match Module

Free Match involves the following stages:
Structured form identification and removal
Full Page OCR
Unstructured form recognition
87
eFLOW Run Time Modules Manual Chapter 12 Free Match
Getting Started
Activating Free Match
The Free Match window controls the operation of the Free Match module. It is activated
through the Module Activator only by a user who has permission to access the Free Match
module.
To invoke the Free Match module:
From the Module Activator, click the Free Match module icon. The following window appears:
Menu
Toolbar
Bar
Recognition
Progress
Report
Original
Image
Viewer
Status
Bar
Figure: Free Match Module Window
88
When you click the Run button, the Free Match module automatically starts to process
the first batch that has “waiting” status in the Free Match queue.
The Status panel

Left rectangle – Free Match status.
The Menu bar

Button Purpose
File Use the File menu to initiate the OCR process. Select Run to
start, Pause or Abort the OCR process. These commands can
also be activated using the toolbar buttons.
The command Run can also be activated using the keyboard
shortcut F5. Pause is activated using the keyboard shortcut
Shift-F5.
Edit Use the Edit menu to Copy report information, Select All the
report information, or Clear Log the report information. These
commands also can be activated using standard Windows
keyboard shortcuts.
Search Use the Search menu to Find specific information in the
report, Find Next (find the next identical piece of information
in the report), or Go to line (jump to a particular line in the
log). These commands also can be activated using standard
Windows keyboard shortcuts.
View Use the View menu to select which information is displayed
in the central working area. You may toggle display of the
report of the Processing progress, which will appear to the
left, and the image file being processed, which will appear to
the right part.
Further, it is possible to select which report items will be
shown:
Show All
Show Pages and Final Results
Show Pages only
Zoom Use the Zoom menu to select the clarification level at which
you will see images files displayed.
Options Use the Option to select standby, the report font, reconstruct
an image file, reset the statistics displayed, view log
information, or display the Debug Script.
Debug Script
To invoke the Debug Script function, open the Options menu. This debugging option allows you to track
problems in Scripts attached to the Free Match module during the run time stage.
89
Free Match Toolbar

The Free Match module toolbar contains the following buttons:
Button What it does

Use this option to initiate the OCR process.

highlighted, and pressing it again resumes the Free Match
from the page where it was stopped.
Use this option to return the batch to the Free Match queue
finishes a page.
Initiating the Form Recognition Process

Manual Operation
You can initiate the OCR process manually in one of three ways:
From the Integra Free Match window, click the Run button
OR
From the menu bar, select File > Run.
OR
be filled in manually, the batch continues on to the Recognition queue. Otherwise (if some
data needs to be filled in manually), the batch is sent to the Manual Match queue.
Automatic Operation
Free Match is also invoked automatically by making the appropriate definition in the Options
menu. If you set the Options menu StandBy option, the Free Match will start processing a
batch as soon as it appears in the Free Match queue.
90
Chapter 13 Manual Match
Overview
The Manual Match module is used to manually find different scripts that will match different
types of documents.
Documents will reach this station for a number of reasons. A particular document may have
been scanned slightly to the left or right, meaning that the Free Match could not identify
any of the fields on this image. Or, some mandatory fields were not recognized.
The Manual Match module offers useful tools to resolve these difficulties, quickly and
simply. Using the Manual Match module, it is possible to in fact relocate all identified fields
and locate unidentified fields. Or, if some mandatory fields were not identified, it is
possible to set these fields and let Freedom calculate the rest of the fields.
Image files are received from Free Match module. After receiving the image files, the Manual
Match module allows the user to use different tools and viewers to identify the pages and
forms. Identified forms may then be sent to the Recognition queue or any other queue
specified in the workflow.
The Manual Match Module

unrecognizable forms so that they may be processed appropriately.
Manual Match involves the following stages:
Manual document identification
Manual location of fields in a document
91
eFLOW Run Time Modules Manual Chapter 13 Manual Match
Getting Started
Activating the Manual Match Module Main Window
The Manual Match window controls the operation of the image Manual Match module. It is
activated only through the eFLOW Module Activator by a user who has permission to access
the Manual Match module.
To invoke the Manual Match module:
From the Module Activator, click the Manual Match module icon. The following window
appears:
Menu Bar
Toolbar
Page
Information
Area
Defau
lt
Actio
Status
Bar
Figure: Manual Match Module Window
The Status panel
Left rectangle – Manual Match status.
Manual Match Menu Bar
Seven menus are accessed from the Menu Bar: File, View, Actions, Navigate, Image,
Options and Help.
The File Menu

activated using the toolbar.

Get Fetch unidentified documents.
Send After you have identified the document, send the form
back to the next queue.
Unlock Return the document to the Manual Match queue untouched.
Save all Save the changes to the document.
92

Undo all Undo last action.
Reject Reject the Manual Match module.
Exit Exit the Manual Match module.
The View Menu

The View menu contains the following commands:
Option/Command Subcommand Choose this to…

TIFF Windows Tile Horizontally Toggles the view of the TIFF
page at work horizontally.
Tile Vertically Toggles the view of the TIFF
page at work vertically.
Full Screen Toggle to open the Manual
Match module to a full-screen
desktop.
The Actions Menu

The Actions menu contains the following command:

Accept the default EFI Accepts the default empty form image (EFI) – when
available
The Navigate Menu

Use the Navigate menu to select the following options:

Select bad page Select an unidentified page. Jump from one unidentified
page to another
Next problematic Jump to the next unidentified document.
form
Previous Form Jump to the previous document viewed.
Next Form Jump to the next document you wish to view.
The Image Menu

The Image menu contains the following commands:

Zoom In Use these options to zoom the viewer of the original
Zoom Out image. The Zoom In and Out options are also available
Zoom Default through the toolbar.
Zoom Best Fit
Rotate Left Rotate the image to the left or the right.
Rotate Right
Flip Flips the image.
93
The Options Menu


Enable Modifying See the section entitled Overriding FormID identification
Auto-Ided pages later in this chapter.
Information be opened to track any problems with the Manual Match
module performance or eFLOW content processing.
events
Manual Match Toolbar

The Manual Match module toolbar contains the following buttons:
Button What it does
Fetch unidentified documents.

Save the changes to the document.
After you have identified the document, send it back to the next
queue.
Return the batch to the Manual Match queue untouched.
Undo last action.
Select a bad page. Jump from one bad page to another.
Jump to the next bad document.
collections queue to one of the stations and try to process/run the
collection again. Or, it is possible to delete the rejected collection
completely from the eFLOW Platform system.
94
Initiating the Manual Match Process

Documents may fail to be identified for a number of reasons. A particular document may
have been scanned slightly to the left or right, meaning that the Free Match could not
identify any of the fields on this image. Or, some mandatory fields were not recognized.
Initiate the Manual Match process as follows:
1. From the toolbar click the File Get collections button,
OR
Click the Get button in the information area.
Note: This button will automatically change its functionality to provide the
appropriate next step for each procedure in the Manual Match process.
Page
Information
Get/Send
Button
Figure: Current Document Pages Information Area
2. The first batch waiting in the queue will be fetched. In the Page Information area, a
listing of the pages in the first document in the sequence will appear.
95
3. The original image will appear in the window to the left, as in the following figure:
Figure: Unidentified Document
4. Using the Matching Fields Viewer at the right you may manually locate fields on the
document. See the next section for further information.
5. Using the information in the Page Processing Information Area, you can solve a
number of different problems. You may select the script to which the page belongs
to, correct the page order, and position fields on the image. See the following
sections for further information.
96
Using the Original Image Viewer to Identify a Document

The original image of the first page of the form will be displayed in the Original Image Viewer
at the right. You may use the zoom and pan keys to look at the image more closely to help
you identify which form it belongs to.
The Zoom Controls
The View > Zoom In/Zoom Out options and the Toolbar zoom commands allow you to control
the size of the original document image in the Original Image Viewer. The Toolbar
contains the following options:
Button What it does
Magnifies the image

Shrinks the image
Identifying the Document

Specify the Document
Examine the image in the Original Image Viewer to classify the document. Once you have
classified the document correctly, you must specify to Freedom what type of document it
is.
1. Select a form from the Form List, at the top of the Page Processing Information
Area.
2. Click any form to select it.
3. If there is only one form in the flow, only one choice will be available, as in the
following figure:
Figure: Form List
97
Identify the Page

Once you have associated the form correctly, you must specify to Freedom what type of
document each Page should be associated with.
You may move between pages by selecting them in the Page Processing Information Area
Page column. Simply click a page row to select it.
Figure: Page Information Area
Page Selection Arrows

The Page Selection arrows on the toolbar allow you to:
Go to the next bad page.

Go to the next bad form.
Page Processing Information Area Information
The Page Processing Information Area provides information about the pages in the
document, their order, and whether or not they have been identified.
In the Page column, the image order of the pages within the current document’s image file
is provided.
In the Order column, the logical Freedom order of the pages within the document is
specified.
In the Master column, the Freedom script with which the page is specified.
98
Change Incorrect Page Order

Pages may have been scanned in the wrong order. For example, pages two and three of a
particular form may be switched. Using the Original Image Viewer you may notice that the
pages are listed in an incorrect order. Change the ordering as follows:
change.
2. Click once in the Order column to reveal the drop-down list box.
3. Select the correct page number for the page.
Note: If only the number 1 is displayed in the Page Order Column, there is only
one page in that document.
Identifying the Correct Freedom Script

If any of the pages have already passed through the Manual Match successfully, the
script will be identified in the Master Form column.
Although a page may be correctly identified, one or more of the form pages may have
failed identification. For example, pages 1 and 3 of a particular document may be
identified correctly, and associated with the right script. But page 2 may remain
unidentified. Using the Original Image Viewer you may determine which script is the correct
one for the unidentified page.
To select the correct document type:
change.
2. Click once in the Master Form column to reveal the drop-down list box.
3. The drop down list contains several options, as shown below:
Figure: Master Form Column
4. Select the appropriate type of document for the page.

5. If the document type is a script, a list of fields that are defined in the script, will be
displayed in the Matching Fields Viewer on the right. If you have made an incorrect
selection, simply reselect the appropriate document type from the Master Form drop-
down list box.
99
Figure: Matching Fields Viewer

Errors
If there is an error in activity, the Status Bar displays an error message. If you try to
reprocess the batch without correcting the error, the report will repeatedly display an error
message until the error is corrected.
Correcting Field ROI Placement
When you examine the image of a page/document in the Original Image Viewer, you may
find that several fields were not identified correctly. During the Free Match process, it
may be that required fields were not found in the document. This may be why the
document could not be identified, and could also cause problems later in identifying the
contents of various fields, that may be related to the required fields.
The Manual Match module offers an important feature to correct field placement errors.
If the field has unsuccessfully undergone Free Match identification, re-placement of the
field on the image is a very simple procedure, and you may adjust ROI placement as
necessary:
1. Focus on the field

2. Scroll through the image by using the scroll bars and find the correct location of the
field.
3. Using the mouse, mark the area on the image.
4. Manual Match will automatically run an OCR engine to recognize the value in the
marked area. This value is then placed in the selected field.
5. Manual Match will trye to recognize all other fields
a. You can control the time out Freedom will try to recognize the rest of
the fields
Send
When you have finished identifying the pages, click the Send button, or select the File
menu > Send selection, to return the identified form to the next queue.
100
Save
document.
Discard
Click the Discard button, or select the File menu > Discard selection, to return the
document to the Manual Match queue.
101
Chapter 14 Tile Module
Overview
The Tile module is usually the station used before the Completion module to make the
Completion module more efficient. The Tile module collects all the characters that were
recognized by the system and offers useful tools to determine which characters were falsely
recognized, quickly and simply. Using the Tile module, it is possible to identify, which
characters are correct and which are not. The Tile module displays the characters in a tile
format, which allows the user to browse through each character and accept it or reject it. All
characters are grouped together to allow for easy identification.
The Tile Module

unrecognizable characters so that they may be processed appropriately.
Tile involves the following stages:

Identifying the character
Accepting or rejecting it
102
eFLOW Run Time Modules Manual Chapter 14 Tile Module
Getting Started
Activating the Tile Module Main Window
The Tile window controls the operation of the image Tile module. It is activated only through
the Integra Module Activator by a user who has permission to access the Tile module. For
more information on the Module Activator, refer to of this manual.
To invoke the Tile module:

From the Module Activator, click the Tile module icon. The following window appears:
Menu
Tool
Page
Information
Area
Status
Figure: Tile Module Window
103
Tile Menu Bar

Four menus are accessed from the Menu Bar: File, View, Options and Help.
The File Menu

activated using the tool bar.

Get Fetch batches.
Put Put the batch back.
Save Save the batch.
Discard Discard the batch.
Exit Exit the Tile module.
The View Menu

The View menu contains the following command:

Full Screen Toggle to expand the Tile module to a full-screen desktop.
The Options Menu


Auto Advance Automatically advances to the next character at a set time
interval.
Information be opened to track any problems with the Tile processing.
events
The Help Menu

Use this command to open the Integra Tile online help and display shortcut keys.
104
Tile Toolbar
The Tile module tool bar contains the following buttons:
Button What it does
Fetch unidentified batches.
After you have identified the batch, send the batch back to the next
queue.
Save the changes to the batch.

collections queue to one of the previous stations and try to
process/run the collection again. Or, it is possible to delete the
rejected collection completely from the Integra system.
Switch to View mode.
Edit the current character. Choose to accept or reject it.
Return to the previous batch of characters.
Return to the previous page of characters.
Jump to the next page of characters.
Jump to the next batch of characters.
Tells you which character you are currently viewing and which
page you are on.
105
Initiating the Tile Process

Initiate the Tile process as follows:
1. From the toolbar click the Get batches button,

OR
From the Menu Bar click File > Get.
NOTE: Once you have gotten a batch the button becomes inactive.
Get
Butt
Figure: Character Page Information Area

2. The first batch waiting in the queue will be fetched. In the Page Information area,
the first batch of characters in the sequence will appear.
3. Tiles of the characters appear, as in the following figure:
Chara
cter
Figure: Recognized characters
106
4. Navigation is also possible using the arrow keys on the keyboard. Use the Enter
button to left click and type any character to right click. Left click the character and
the background turns red. It is now marked so instead of a falsely recognized
character it will appear as an * (asterisk). This character is not connected to the
recognized character and will override recognition results.
Right click the character to edit it. See the section
5. Editing the Characters for more information.
Editing the Characters

1. Right click the character. The Edit dialog box opens:
Figure: Edit dialog box

2. If the character is recognizable click OK. The character background
changes to yellow.
3. If the character is unrecognizable click Reject. The background remains
red.
The screen displays the accepted and rejected characters as shown below:
Rejected
Character
Accepted
Character
Figure: Accepted and Rejected Characters
107
Viewing the Characters

The View mode allows you to see the character in the form and shrink/enlarge the image
display by 10%. Using the Zoom In button and the Zoom Out button in the
tool bar. Click the View button, then right click the character. The Image Viewer
window opens as shown below:
Image
Viewer
T
Character o
o
Character
In Form
Figure: Image Viewer window

Save
form.
Discard
Click the Discard button, or select the File menu > Discard selection, to discard the
batch.
108
Chapter 15 Content Validation in

Completion
Overview
The Completion module receives data produced by the Processing module. The
unrecognized data are then corrected and completed manually. The forms are displayed in
page mode only, where the typist sees a full page and can move from field to field in the
page.
This station is used in cases where the processing (and the operator) can anticipate which
data will be on a form, but the exact location on a page is not known. The input can then be
used for Learning in order to improve subsequent processing.
The administrator or application designer uses the Visual Designer’s Screen Builder to define
what data is brought to the user’s attention and how it is displayed.
The Completion process consists of sequential stages:

Retrieval of recognized collection data
Manual correction of data that was not automatically recognized, or re-checking of
recognized characters
Manual demarcation of ROIs (regions of interest)
Marking of unresolved problems as exceptions for later handling in the other modules
Saving or discarding data.
109
eFLOW Run Time Modules Manual Chapter 15 Content Validation in Completion
Getting Started
Invoking the Completion Application

The Completion module can only be invoked through the Module Activator, by a user who has
permission to access the Completion module.
From the Module Activator, click the Completion module icon.
The Completion window appears:
Figure: Completion Initial Window
110
The Completion Process

In the Completion process, the operator traverses the fields one at a time and invalid fields
are displayed with an Error Providor ( ) and a color indication. The user must manually
complete those fields on which the Processing engines were not able to concur, and those
fields whose contents are invalid (due to incorrect Processing or errors/omissions on the
form). If the completion cannot be done, the operator can set an exception for the field or
for a group of fields.
In some cases, the user must correct immediately; in other cases, it is permitted to move
within a defined range of fields and all field in the range must be completed before the user
can leave the range and continue working on other fields.
In the data completion screen, the operator is shown all or part of the form and is given text
boxes in which to enter all or part of the form data, as appropriate.
The user can specify the correct data in several ways: for example, typing, selection from a
lookup table, or demarcation on the page image of a field region containing the required
text.
To start the Completion process:
To start the Completion process on a batch in the Completion queue, click the Get
Batch button. (Alternatively, if the station is running in Automatic mode instead of
Standby mode, the batch is retrieved automatically.)
If the Completion queue is populated, the first page requiring completion appears in the
Completion main window:
Original
Form
Image
Recognized
Field Data
Figure: Completion Main Window
111
Using the Completion Module

When you open the Completion module, the first available batch in the module’s queue is automatically
loaded for your review, and you will see field data; the screen layout shown is as specified in the Screen
Layout created in the Application Visual Designer. The subsequent batch moves into the first spot on the
queue.
Note that in the Integra Completion module, you can work in both Field Group mode and
Page mode. In Completion, all processing is in Page mode only.
The station is designed to allow uninterrupted field completion. In some cases the user is
permitted to move through all fields on a page despite problematic fields, and return to
attempt to resolve the problems at a later time.
When the last field requiring completion has been filled in, the batch is automatically sent
(Put) into the workflow. To cancel a Put operation, click in the bottom right corner of the
station screen on the “Click here” label within several seconds of the action.
Data Indicators
The following summarizes color coding for various types of fields. The selection of specific
colors used is done in the Application Visual Designer.
Note that in this document reference is made to the default set of colors, as well as the
default set of keyboard shortcuts.
Indications on the image include:

• frames around all fields that have been recognized
• field of current cursor position
• invalid fields that have not been completed
• fields that were originally invalid and have now been completed.
Indications in the data input panel include:

• invalid field: highlighted background/foreground color, as well as Error Provider ( )
icon next to the field
• current field: highlight frame color
• completed field: a second frame color.
View
Table Display
Two display modes are provided for Table data:
• Grid Mode: data is displayed in a standard grid with no direct relation to the dimensions
of the table in the original form
• Table Layout Mode: the locations of the table elements in this mode match the layout of
the table in the original form.
112
Figure: Grid Mode

:
Figure: Table Layout Mode
Layouts
The following screen layouts are available via the pop-up menu on the right bottom of the
Completion screen:
• Tab layout: each group is displayed in a tab
• Other customized layouts as listed in the menu.
To change the screen layout:

In the Status area at the bottom right corner of the window, right-click on Current Layout,
and select from the list of available layouts. A checkmark appears to the left of the layout
currently in use.
Figure: Changing the Layout
113
Data Fields
The following illustrates valid and invalid data fields:
The Page-Map Pane

The page-map pane can be displayed by clicking the magnifying-glass icon on the bottom
right of the screen. Click on the page-map pane to show a small version of the entire page,
with indication of which portion of the page is currently visible in the workspace.
Figure: Completion Page-Map Pane
Data Manipulation
Field Completion
In order to finalize and fill in missing form data, the typist must fill in correct data for any
unrecognized characters. Whenever an unrecognized character (*) appears in the data field,
a character must be filled in to replace it.
Some types of fields have an input mask defined for them: for example, ##.##.#### for a
date field. This mask constrains the format of the data that may be entered in a field.
The original scanned field contents appear in the Form Image in yellow, with a red frame
surrounding the field. The Form Image is provided to ensure that quick reference to the
original data is available.
The typist may use this original form information to read the field contents and fill in the
appropriate missing information.
Note that in this document reference is made to the default set of keyboard shortcuts.
114
To fill in missing data:
1. You will be prompted at each vague/unrecognized character (*) to fill in

the appropriate field value.
2. If you do not fill in data for a particular field, the field will be highlighted
in red to warn you that data is incomplete.
3. To fill in a missing character, simply type over the unrecognized character
(*).
4. You may use keyboard arrow keys to move to other characters. If you do
not use arrow keys, the cursor will automatically jump to the next missing
character.
5. To erase a character, use the <backspace> key.
6. After typing the necessary information from the form image in a given
field, you may proceed to another field. The status and visual indication for
the field may change.
7. In order to skip to the next field that contains unrecognized, invalid or
missing data, you may press Enter.
8. If the program does not allow you to proceed, the reason will be displayed
in the status bar. Correct the typed data, or mark an exception, as
appropriate.
115
ROI Selection
If the data that should be specified in a field can be found on the page, it is possible to
highlight it and eliminate the need for typing it in. This action has two results: (a) populates
the field and (b) creates an ROI (rectangular region-of-interest) that is now associated with
the field, to be used to improve future processing.
To select ROIs:
• click on a specific word, or
• Press/Drag/Release (as text is highlighted in a word-processing application).
Note that when selecting text with the <Ctrl> key pressed, you can select words from
different lines (the default selection selects information from a single line only.)
Marking Exceptions
Refer to the chapter on
116
Content Validation in Completion module for instructions on how to mark exceptions. The exception list
is opened via the icon:
Table Manupulation
The following operations are available for table completion:
• Delete Row – Delete the current row in a data table and its associated row on
the image
• Insert Row Above – Add a new row to a table above the current row
• Insert Row Below – Add a new row to a table below the current row
• Copy Row from Above – Copy the data in the row above to the current row.
Automatic Table Recognition

Tables are not always recognized during the processing stages prior to this station, This
function causes eFLOW to recognize a table, or to recognize additional rows of a partially-
recognized table. The operator may then complete individual fields (table cells) as needed.
To auto-recognize a table: Move focus to a field in the table, and click the tool
button.
Using the Lookup Table
Refer to the chapter on
117
Content Validation in Completion for instructions on using Lookup Tables.
Document Merge
Attachments
An attachment page accompanies a form but it cannot be recognized or modified as can
other pages in the form.
If a page is designated as an attachment, a graphical indication is added to the page in

the navigation pane.
Manual Doc Merge Operations
By pressing the document merge button ( ) you can perform manual document
merging, and mark pages as attachments.
Remove the New Document indication from what is incorrectly considered the first
page in a form, to specify that it should actually be a continuation of the previous form.
Batch Manipulations
After the fields in the batch have been completed, the batch can be returned or “put” to the
server. For this purpose, use the Put Batch button: .
Discarding a batch is also possible, by using the Discard button: .
If you want to cancel a batch-manipulation action before it is committed, click the “Cancel”
button that appears on the right bottom corner of the Completion screen; this must be done
within a few seconds of the action.
Navigation
The operator typically moves sequentially from one field to the next on a page and from
one form to the next in a batch. However, the work mode can vary as well: see Skipping
Level and Special Cases below.
Navigation Operations
The keystrokes specified in this section are based on the default shortcut definitions. See
the end of this chapter for information on customizing the shortcut-key mappings.
To move to the next field (valid or invalid): press Tab.

To move to the next invalid field: press Enter. All valid fields are skipped. Information
about invalid fields will appear in the message area of the status bar.
118
To move back one field: press Shift+Tab.

To move back to the previous invalid field: press Shift+Enter.
You can also use the mouse to navigate within a page.
Skipping Level
The navigation behavior may vary, depending on the definition of a maximum “skipping
level” for your station. The skipping level defines how much freedom you have to navigate
among the fields in a range such as a field group, or an entire batch:
• Field Level: the user may only leave a field once the field contains valid data.
• Group Level: the user may move among the fields in a group but cannot leave the group
until all the fields in the group have been validated.
• Form Level: the user may move among the fields in a form but
cannot leave the form until all the fields in the form have been validated.
• Batch Level: the user may move among all the fields in a batch.
Example:
In the case where Group-level skipping is defined and there is a group containing three
fields – Price, VAT and Total – in this order.
Price and Total are invalid and only VAT is a valid field.
When focus is in Price, pressing Next Invalid Field moves the operator to Total. If Next
Invalid Field is now pressed in the Total field, focus is moved to Price, as this is the next
field requiring attention in the group.
Special Cases of Navigation

Exception: When a field has an exception marked on it, it is considered a valid field, even
though it contains invalid data. (Navigation to the next field will skip it.) If a field group
has an exception on it, the entire group can be skipped.
In several special cases, a field behaves as an invalid field, even though its data is valid and
it does not appear as an invalid field (i.e., there is no Error Provider indication near the
field).
• One-time Stop: this is a field with data that needs to be confirmed, so you must review it
at least once. After you have stopped at the field once, it is no longer considered a one-
time stop field.
• Stop Always: Fields of this type must be stopped at every time you pass them.
Navigation Pane
The forms in a batch, and the pages in each form, must be reviewed and validated in
sequence. Using the Forms Navigation Pane ( ) tool button, you can view and access
specific forms and pages in the batch. In order to navigate to a specific page or form simply
double click on it.
The navigation will be permitted according to the navigation rules and policy in your
application.
119
• Forms and pages that contain invalid fields are marked with
• Forms and pages that contain valid fields are marked with
• Pages that are attachments are marked with .
Figure: Completion Navigation Pane
120
Customization
Keyboard Shortcut Customization
To customize the keyboard shortcut mapping, open the Shortcut Editor via the tool button
( ):
Figure: Completion Shortcut Editor
You can select an entry to modify, specify a new shortcut-key combination, and click
Assign to save the new definition.
Press the Print button to print the full list of current shortcut definitions.
121
Menus and Toolbars

Completion Toolbar Buttons
Tool This means…
Get Batch
Put Batch
Save Batch (without sending it back into the workflow)
Discard Batch
Form Navigation – Opens a read-only navigation pane for viewing the

form/page hierarchy and for moving among the pages
Exception – opens the list of exceptions for setting an exception for the
current field
Shortcut Editor – displays the shortcuts and enables editing of the shortcuts
Fit Width – Fits the image to the image viewer width area.
Fit to Screen – Fits the image to the viewer based on the screens resolution
Fit Page – Fits the image to the viewer area so that the entire image is
displayed without scrolling (see Figure above).
Delete Row – Deletes the current row in a data table and its associated row
on the image
Insert Row Above – adds a new row to a table above the current row
Insert Row Below – adds a new row to a table below the current row
Copy Row from Above – copies the data in the row above to the current row
Zoom Out – zooms to show more of the image less magnified
Zoom In – zooms to show less of the image more magnified
Page Up – Goes to the next page in the image viewer
Page Down - Goes to the previous page in the image viewer
Manual Merge - opens a Set Attachment (form organize) window, so that you
can remove the New Document indication from the second page to include it
in the same form as the first page
Auto Recognize – Recognize the remaining rows of a table automatically,

based on the recognition patterns that have been identified manually in the
first row(s).
122
Tool This means…

Rotate Left – Rotate image counter-clockwise
Rotate Right – Rotate image clockwise
Completion Help Screen

To invoke the Help function, press F1.
123
Chapter 16 The FreeCollect Station

The FreeCollect station analyzes the data entered in the Completion station, in order to
update the Learning database.
The station can be run in one of the following two modes, as specified via Visual Designer:
Mode 1: In this mode, FreeCollect learns only from fully-recognized fields: i.e.,
where both the field data (contents) and the field rectangle (position) have been
determined: either automatically, without user itervention, or where the user has
demarcated the field rectangle and possibly also entered field data.
Mode 2: Here, FreeCollect attempts to learn from fields that are not fully
recognized: i.e., a rectangle was not demarcated for the field.
The station tries to match text from the recognized page image to the completion data
entered by the operator. The algorithm looks for close matchs, and not only a perfect
match, allowing for OCR inaccuracies and possible format variations (i.e Date &
Amount ).
When a single plausible match is identified: the rectangle on the matching word(s)
is added to the Learning database.
If the matching results are not definitive enough: this field is not used for
learning.
The following parameters can be set in Visual Designer for the FreeCollect station:
Parameter Name Description
CommandParams Mode:1
Mode:2
(see above for descriptions)
AllowUnattended Indicates whether the station may be

run unattended
AttachmentType PRD: File produced by OCR
124
Chapter 17 Content Delivery - Export
Overview
The Export module converts captured data into ASCII, XML or database output, and stores
the images and indices in the systems export destinations.
In the Application Visual Designer, the system integrator defined the format that
translates the data from the internal representation used throughout eFlow into the format
required by the client. Settings in the Application Visual Designer delineate the Export
file destinations, Export file formats, and report destinations and types. It is possible to use
or override these settings. During runtime processing, the Export module receives the data,
converts it to the previously defined format, and transfers it for export.
The Export operation performs several main tasks:
Converts and exports data which has finished the Completion and Exception stages
Exports image files
Data export to user-definable ASCII, INI or XML format
Data export to remote database.
125
eFLOW Run Time Modules Manual Chapter 17 Content Delivery - Export
Installation
The Export module is installed automatically during the eFlow installation.
Invoking and Using the Export Module

The Export module can be invoked through the eFlow Module Activator, only by a user
who has permission to access the Export module. For more information on the Module
Activator, refer to Chapter 3 of this manual.
To invoke and use the Export module:

1. Click the Export button in the Module Activator window.
The Export main window appears:
Menu Bar
Tool Bar
Channels
Activity
Area
Export
Status
Display
Status
Bar
Figure: Export main window
2. Set Export Options. To change the export options click the Configure
button or select the Options menu > Configure selection. It is important to set the
export options before running the export processes. For more information about
Export Options, see the next section.
3. Click the Run button on the toolbar to start the Export process, or select the
File menu > Run option, or press F5. The Export module automatically starts to
process the collections waiting in the Export queue.
4. If a channel is exporting, it will display a light-green icon in the Channels Activity
area. If the channel’s icon is a dark green light, the channel is in idle mode or has
finished transmitting. If the channel’s icon is a red light the channel has stopped
working.
5. Information about the export status of the collections appears in the Export Status
Display area.
126
6. To stop the export process, click the Stop button on the toolbar, or select the
File menu > Stop option, or simply press the Esc key.
Export File Types and File Storage Overview

File Names
The Export module stores files using a naming system that is related to the specific flow and batch that
is the source of the material, with an appropriate extension related to the format of the file. All files
within a specified batch are given the same name, but may have different extensions.
The syntax of the name of a file is as follows: FlowName_BatchName
Extensions are:
Extension Format type

XML XML file.
TXT ASCII Delimited file.
INI INI file.
ANO Exception file, ASCII or INI.
GIF Original color image file.
TIF Original TIF (B&W) image file.
REG Registered TIF file.
DIF Removed DIF file.
127
XML Files
The XML file format is designed to offer the maximum amount of information regarding the flow and
batch. The following actual XML file tree-structure outlines of the information available. A table listing
object names and definitions follows.
TisDynamicDatabase
Collection
TIS_00000005
Properties
BatchName
CreationTime
FlowType
FormsInBatch
PagesOfBatch
CollectionSource
ExportPassCount
MTFFile
Form
FormName
Properties
FormType
Page
PageName
Properties
PageId
MatchCode
IdentificationMethod
IsAttachment
Field
FieldName
Properties
Contents
OriginalContentsNumberOfCompletions
FieldTable
TableName
Properties
FieldArray
NewColumn
FieldName
Properties
Contents
OriginalContents
NumberOfCompletions
FileCreationTime
DateTime
GMTOffset
StandardName
128
Most of the XML entry names are self-explanatory. Further definitions for XML entries are listed
below:
Entry Description
CollectionSource One of three types of sources:

scanned forms, electronic forms,
or image files.
IdentificationMethod EFI identification algorithm code:

10 – page identified
automatically
20 – page identified
manually
30 – page received
default ID
IsAttachment Designate if page is an

attachment
MatchCode Specifies level of confidence of

page recognition
PageId EFI name associated with page
NumberOfCompletions How many sessions of

Completion the field underwent
OriginalContents Field value before undergoing

Completion
NOTE: If a field has an exception, it is created as an entry under the field entry.
A field can have more then one exception, but each will be written on a different
line.
ASCII Delimited Files

For ASCII delimited files, the format specifies that each record be written on a different line, with
(default) tab character separations between fields. The default tab separation character may be set to
another character.
Multi line text fields are written as one line, with a space separator character to designate line breaks.
Array fields are written in the same line, as in a one-dimensional array. A tab delimiter separates the
fields.
INI Files
The INI file format specifies that batch information is separated into sections named
[BatchDetails], which contain batch properties.
129
Similarly, form information is contained in separate sections. Each form information section is assigned
the name of the specific form it describes.
ANO (Exception) Files
An ANO exception file contains the following information:

Form name
Field name
Exception description.
File Storage
The Export module creates temporary storage for each flow with a separate directory using the flow
name, created under a directory named “ExportData”. Under each flow name directory a sub
directory is created for each batch with the name of the batch, containing batch-exporting files, waiting
to be launched. After transmission this directory is deleted.
A simulation of the directory tree is as follows.

/ExportData/Flow Name/Batch Name/Batch Files
Permanent storage is designed in exactly the same way. At the destination, the storage tree
structure is identical to temporary storage, except that flow name directories are created
under the directory specified in the options screen. If no path is specified, then the directory
tree structure is created in the TiS temporary directory.
Database Structure
Data can be exported to Microsoft SQL server RDBMS via OLE DB/ADO mechanism.
The schema concept is as follows:

There is a table for each object type that is exported. For example: collection, form, page
etc.
In addition, for each object type (form, page etc.), there is a table that holds the parameters
for that object.
Export Configuration
Export configuration defines export process display, debugging, and working conditions.
They also allow you to change the export destinations, overriding Application Visual
Designer default settings. To change the export configuration, click the

Configure button or select the Options menu > Configure entry. The Export
Configuration window appears:
130
Figure: Export Configuration window – General Tab
Note: To use the definitions set in the Application Visual Designer, click the Load
Defaults button. When finished, click the OK button to apply the default settings.
The Export Configuration window contains two tabs. In the General Tab the following settings
can be defined:
View
Select the number of rows of information to be shown in the status list of the Export main
window.
Export to Database
In order to export data to Ms SQL server, first click the Export to Database check box.
Before activating the export process for the first time, a new database should be created.
First define a connection string to the remote database computer: Click the “…” button to
open the Data Link Properties dialog box and set the connection parameters. We
recommend that you test connection in order to verify connection parameters. Press the
Test Connection button to activate testing.
After connection to the remote database computer was succesfully tested, create the
database by clicking the Create Database button. The following dialog box opens:
131
Figure: Create Database dialog box

Set the following parameters:
Database path – the directory used to store database files.
Note: Database path should be relative to the database server computer.
Initial size – the initial size for the file holding the data.
File growth – the growth increment of the database file.
Click the OK button to create the database and its schema.

The database name format is: Integra + [Flowset Name] + Export.
Enable work in OffLine mode

Select whether exporting is also available in Offline mode, that is, data may be converted to
a particular format without being transmitted to the permanent location. For example, for
FTP servers, batch conversion into files is completed even when, say, the Internet
connection is down or overloaded. When the Internet connection is re-established, all
waiting batches will be launched after starting the Export process again by pressing the
Run button , which will automatically activate a recovery procedure.
132
Flush each form to a file

Select whether to export each form to its own file. This option is only relevant for INI files.
The Export Destinations Tab allows the user to select where data will go to, and how it will be
conveyed:
Flow
Selector
Figure: Setup Sub tab

Flow Selector
Select/change the flow to which the information is to be attached by clicking a flow.
The Export Destinations Tab itself contains two subtabs, the Setup Subtab and Channels
Subtab. In the Setup Tab, select the destination type and path.
Destination
Select the destination architecture, whether LAN or FTP server. Once opened, an FTP
connection remains open as long as the export process is running.
Path
Type in the destination path. Or use the file browser button to open a file browser,
with which you can locate the destination directory.
If you select an FTP server as the export files’ destination, you will be prompted to
provide further information:
133
Figure: TP Options
134
FTP Parameters:
FTP Server
Provide the name or IP address of the host you wish to connect to.
User ID
Specify the user ID to use when logging on to the remote FTP host.
Password
Provide the password you use to connect to the Host specified in HostName with the user name described
in property User ID.
Remote Dir
Provide the full path of the local directory that will be used as the download path.
Port
Specify the FTP connection port. The default setting is 21. If you are not sure, it is recommended that
you not change this setting.
Timeout
Specify the time in seconds to wait for a response from the socket before the raising a system exception
flag, which will timeout the connection.
Connection Retries
Select how many connection retries to perform when a connection cannot be established.
Test FTP
You can immediately test and modify or correct your FTP settings by using the built in testing process
available through eFlow. Simply press the Test FTP button and the Test FTP Connection window opens,
revealing the results of your test:
Figure: Test FTP Connections Window

If the test is successful, messages will appear in both the Status and Result boxes that the connection was
successfully established. If the connection cannot be made, an error message will appear in the Result
box with an error code or definition, if available.
Load Defaults
Reset the FTP settings to the default settings specified in the Application Visual Designer.
135
In the Channels Tab, select how many channels will be created to launch export
processes.
Figure: Channels Sub tab

The Launching Mechanism
Data transmission to destinations can be executed in threads. This is done to enable parallel
local processing of the next batch along with data transmission of the previous batch, which
increases the Export module’s efficiency.
Launching channels
Define how many concurrent launching channels can be opened for each flow, where each
one may activate in a different thread. Once a batch storage conversion process has finished
the system checks if batch files can be launched. If permitted, files are launched
immediately. If not, batch details are stored, waiting to be launched later, when the file
transmittal of another batch is completed.
Select the number of Launching channels by entering the number in the combo-box, or
clicking the up and down arrows to select a number. Once you select more than one
launching channels, they will automatically run in separate threads. However, you can also
choose to launch a single channel in thread by clicking the Run with Thread checkbox. In that
case, if more than one collection from the same flow is waiting in queue, it can be launched
through the same channel in different threads.
Thread Priority
Choose the thread’s level of Priority by selecting a level from the list box. A thread’s
Priority indicates the Windows CPU schedule priority used when scheduling the thread.
Adjust the priority higher or lower as needed. The Default setting is Normal. Settings are
defined below:
136
Setting Means
Idle The thread executes only when the system is idle-Windows
won't interrupt other threads to execute a thread with tpIdle
priority.
Lowest The thread's priority is two levels below normal.
Lower The thread's priority is one level below normal.
Normal The thread has normal priority.
Higher The thread's priority is one level above normal.
Highest The thread's priority is two levels above normal.
TimeCritical The thread gets highest priority.
Note: Be cautious when selecting a high priority level. Setting a high thread
priority for a CPU intensive operation may “starve” the other threads in the
module. Only apply priority boosts to threads that spend most of their time
waiting for external events.
137
Graphical Overview of Export System
Export Queue
Data Retrieval
Offline
Data Conversion
If there are any

Local Files available objects
If there are no
available objects
Batch stack
Online
Launching
Objects
Multi Tasking Data

Launching
Transmission
Transmission Complete
Complete d
d LAN WAN
Local Server FTP Server
138
Monitoring the Export Module

The Export module is monitored through the status bar, Export Status Display, and the
channels Activity area in the Export module. Once batches start to be processed, the Export
Status Display will contain information regarding when each batch has been processed, and
whether export was successful.
To Monitor Files in Queue to be Exported:

Information regarding the status of channels is available in the channels Activity area, to the
right.
Export
Status
Display
Channels
Activity
Figure: Export main window
139
Export Channels Status Area

The display area provides a list of batches that are ready to undergo export.
To the left of each batch is an icon that shows the exporting progress of a batch as follows:
Icon This means

[Dark Green] Channel is idle.
[Light Green] Channel is processing.
[Red] Channel is not functioning
Monitor Files That Are Being Exported:

Information regarding the status of batches undergoing export is available in the Export
Status Display area, in the main area, on the left side. This area provides the following
information:
Flow & Batch List – Lists the flow and batch number that is undergoing/has
undergone export. To the left is an icon that signifies the step in the
export process that the batch has reached.
Time – Time export took place.
Status – Status/success of export.
Description – More information about the export process. If unsuccessful,
further description appears here.
Flow & Batch List

The display area provides information about export activity. Each export process is signified by a
message on a separate line, which includes an icon to that right that shows the exporting progress of a
batch: The icons and their significance are listed below:
Icon This means

Batch is converting from raw data to flat files.
Batch is waiting in the stack.
Batch is launching files.
Batch has launched successfully.
Batch is exporting to database.
Batch is in Offline mode.
Batch error.
Batch has launched successfully on recovery.
140
Status:
Batch status messages may be one of the following:
Icon This means

Converting Undergoing conversion from XML data to flat files.
Creating XML Creating the XML data from raw data.
Error Error occurred while building files or exporting.
Launching Launched to destination.
OK Data files successfully reached destination.
Processes closed Finished processing the batch.
OK/Recovery Files were sent successfully to destination after

recovery process is activated.
Offline Files could not be sent to destination but were created

and are in offline mode.
Status Bar
The Status Bar provides information about the status of the Export module itself, including icons that
show the whether the Export module is running an Export process, in idle, or closing:
Icon This means

The Export module is in stop mode.
The Export module is in idle mode.
The Export module is fetching collections.
The Export module is closing.
Error, the Export module is not functioning.
141
Export Module File Transmission Failures and Recovery

File transmission failure may occur in one of two cases:
While fetching or converting a collection.
While transmitting files to destination, the network connection fails or is overloaded.
During conversion, if there is a problem with the conversion process, an error message will appear and
the Export module will stop processing.
However, if an error occurs during transmission, the reaction of the Export module will depend on
whether or not you have enabled Offline mode in the Options window.
eFlow uses several procedures to avoid data loss, corruption or duplication due to failures during data
conversion or transmission. When errors occur, processing is stopped gracefully or continued in Offline
mode. When the Run command or button is activated, if the problem is resolved, the Export module
converts any file in queue, and exports any files left in the local, temporary, export directory.
How does this work? Say that a failure occurs during the data conversion to a file format. A batch is
removed only after conversion is finished, and all temporary files are created. That is, only after all the
data is converted to file format is a batch removed from the “conversion” queue. If conversion is not
completed, when you next Run the Export process, the batch will still be in queue so will be re-fetched
and converted again. The old temporary storage files, including the failed data conversion, will be
overwritten with the new, converted files. These files will then be exported.
Say that a failure occurs during transmission. Temporary converted files are removed only after
successful transmission of all the files in a batch. So, if some of the files are not successfully
transmitted, they will not be removed, and therefore are still in the queue to be “exported.” When you
next Run the Export process, the batch will still be in queue so will be re-transmitted, and old permanent
files will be overwritten.
Thus, eFlow ensures that full batch data is always stored and available, in the local storage directories
and/or in the TSD or at the remote site.
Offline Mode
If you do not select the Offline mode in the Options window Export Configurations, when there is a
problem exporting over the LAN or FTP that you have selected, the Export module will stop processing.
An error message will appear, and any conversions or export of batches assigned to export to the failed
LAN/FTP will be suspended.
When you select the Offline mode, in the case of a LAN/FTP failure, data is converted but not
transmitted. Note that this applies to both to local exporting (LAN) and to remote exporting (FTP).
You may decide to enable Offline mode when a network connection is down or overloaded. In this case
files that are waiting to be transmitted will still be converted from raw data, and stored temporarily.
When the network connection is re-established, once the Run command is issued, all the batches
converted to files will be transmitted.
Restart Conversion/Export
When you receive an Error batch status, check if the problem is with a CSM or network connection
failure. This information will be recorded in the Debug Logger. Once you have resolved the problem,
and/or the connection is reestablished, execute the Run command.
Click the Run button on the toolbar to start the Export process, or select the File menu > Run
option, or press F5.
Error Handling
142
If an error occurs during conversion, or during transmission when the Offline mode is not activated, the
error will be logged to the Debug Logger. An error message will appear in the Export Status Display area,
and the Export module will shut down after handling administrative tasks relating to data storage and
conversion.
Errors during conversion will stop the engine and an error message will appear.
The OnError event is triggered when a conversion or launching error occurs. Other conversion errors are:
GetCollection, GetImages, CreateXML, WriteFile, WriteExceptions.
If an error occurs during transmission when Offline mode is activated, the error will be logged to the
Debug Logger, but the Export module will continue processing.
Errors that may occur during transmission are: Connect, MakeDir, ChangeDir, and CopyFile.
143
Chapter 18 OCR Analyzer

It is important to fine-tune the OCR Virtual Engines that you have created to reduce false
positive readings to an absolute minimum. In order to fine-tune the engines, the OCR
Analyzer module is used to provide statistical data on the quality of the OCR engines’
processing capabilities. This analysis tool provides comprehensive processing monitoring.
These results are used to modify engines so that results have minimal false positives.
Use the information in this chapter to examine the statistics for the engines, virtual engines
and voting methods, and determine what fine-tuning is necessary. Use statistics results to
locate segmentation and processing problems to improve how engines handle information.
The OCR Analyzer contains a powerful time-saving option called Refresh. Once you change
engine parameters in the Designer, the user may click the Refresh button to reload the
engine parameters without running all the run-time modules again. This considerably
simplifies testing any changes in the engine parameters, making fine-tuning quicker and
simpler.
This chapter deals with the OCR Analyzer module itself, a product used to test the
effectiveness of the OCR engines. The actual calibration of the engines is done in the Visual
Designer.
144
eFLOW Run Time Modules Manual Chapter 18 OCR Analyzer
The OCR Analyzer Process

The analysis process is comprised of five phases:
Data preparation – A preliminary phase in which raw data is processed and exported into XML and
DIF files.
Engine tuning – The phase in which the user changes engine parameters in the Visual Designer.
Data Query – The phase in which the user selects the data to be processed.
Data Processing – The phase where data processing takes place and raw data results are created. Data
is selected from the OCR Analyzer Process window shown below:
Figure: OCR Analyzer main window

Data Results – A phase in which raw data results are summarized into statistical data.
Figure: Form View Mode
145
Once the initial Processing OCR Analyzer assessment is made, the user may perform engine tuning using
the Visual Designer. Once changes are made to the engines, the user proceeds through the rest of the steps
to analyze the results of these changes, and then performs any further fine-tuning as necessary.
Data Preparation
Before using this module, batches that we want to test must be sent through the entire
run-time process. This starts with the input process using the Scan Portal or File
Portal, and then continues with data Processing, Completion and storage though to the
Processing, Completion and Export steps.
We need the Processing results in order to evaluate engine processing capabilities, and
the Completion results for comparison purposes. Corrected Completion results are
therefore a necessary precondition to producing any assessments of engine results. The
OCR Analyzer module uses these Completion results for comparison purposes, but only
after the results are exported. The Export process prepares many different types of
information about the data processed and the methods (parameters) used to process the
data. The Export process also converts this information into a format, which is
appropriate for OCR Analyzer analysis. All of this information is used by the OCR Analyzer
to perform comparisons and analyze the quality of data Processing.
Once the OCR Analyzer produces information about the accuracy of data Processing, if
engine results are not sufficient, relevant engines may be retuned and the batches may
be processed again for further evaluation.
There are a number of issues to consider when starting the entire procedure. It is
important to determine what sort of testing you would like to do. You should select
whether to test a particular engine’s capabilities, or the recognition accuracy of an
EFI—that is, form recognition, or a particular set of fields. You may select to test whole
batches, or instead, individual forms. In order to perform effective analysis, consider the
recognition issues, which you wish to examine and tailor your analysis process to the
type of data that you wish to test.
146
Data Preparation Steps
The entire OCR Analysis data preparation procedure includes the following steps:
Design Phase
1. Using the Visual Designer, specify that the flow that you wish to test has
Flow Export properties set to produce DIF and REG files.
REG Page
DIF image
Note: It is important to remember to specify in the Visual Designer for the

Flow Export properties that the Export files produce DIF and REG files. The
OCR Analyzer requires these file formats.
2. Next, engine definitions are created with the Visual Designer.

3. Once the design stage is complete, it is time to proceed to the run-time
stage.
4. If you wish to scan in forms that do not exist in the system, use the Scan
Portal modules to input new forms into the system. If you have already
scanned the forms that you wish to test, use the File Portal modules to
input these forms into the workflow. Through either of the Enterprise
Portal modules, a DIF and REG file is created for each input file that
you enter into the system. The DIF file contains the form’s raw data and
information. This raw data and the REG image is the basic building
block of your testing procedure.
5. Finally, process the raw data using the Content Recognition, Completion
and Export stages. You now have processed, converted data, which is
ready for analysis.
147
Data Query - Selecting Data
During the Processing step, you should choose exactly which data you want to analyze,
and at which design level it will be analyzed. For example, do you wish to test engine
processing of particular fields, which is testing at the field level, or do you wish to test
the processing capabilities of actual forms, which involves testing at the form level.
It is possible to process anything from single forms (in a single-form collection) to

entire batches, or to process particular EFI’s, or even to select specific engines for data
processing.
Data Results
Statistics are prepared by comparing a batch’s state after the Processing phase
with the batch state after the Export phase (following human corrections). The
statistics reflect the success of the processing at two levels:
Character recognition – the success of OCR voting per character.
Field recognition – the success of OCR voting per field.
You may display the results in either Field Recognition mode or Character
Recognition mode. Character Recognition mode is the default setting.
Character Recognition Mode
Total – Number of characters processed for each field.
Recognized – Number of characters correctly identified by OCR
voting.
False Recognition – Automatic OCR voting produced a character that
was incorrect, a false positive; requiring override by the typist.
Not Recognized – Characters that were not identified by OCR voting,
e.g. returned as unrecognized character.
148
Field Recognition Mode

If you select the Fields option, the chart will display cumulative engine results
for individual fields and for all fields cumulatively. Results are categorized as
follows:
Total – Total number of fields processed.
Recognized – Number of fields where all characters in a field have been
correctly identified by OCR voting.
Not Recognized – All characters identified by OCR voting (i.e. returned a
character other than an unrecognized character) were correct, but the
automatic OCR voting returned at least one unrecognized character in
the field.
False Recognition – Automatic OCR voting produced a field containing
at least one character that was incorrect, a false positive; requiring
override by the typist.
OCR Analyzer Startup

From the Windows Programs > TiS > eFlow 4 menu, click the OCR Analyzer option.
The OCR Analyzer window appears: Import Export Activate
Query Query Process
Settings Settings Dialog
Box
Menu Bar
Select Flow
Mode
Selector EFI’s available Flow Tree Select Tree
in the flow Viewer display Viewer
mode Buttons
Open
the
Visual
Designer
Refresh
the
Engine
Parame
Status Bar
Figure: OCR Analyzer main window
149
Desktop Layout
Using the Menu Bar
Three menus are accessed from the OCR Analyzer Menu bar: Select, View,
and Help.
The Select Menu

The Select menu contains the following options and commands:
Process Selects the Process Mode, displayed in the main

working area. In this mode the user selects the
parameters for the testing process. The actual
processing is performed.
Form View Selects the Form View Mode, displayed in the

main working area. After the processing is done,
the user uses this mode to view a log of
processing results.
Field Statistics Selects the Field Statistics Mode, displayed in

the main working area. Testing results are
compiled into statistical tables, which are shown
in different views in this mode.
Exit Exit the OCR Analyzer.
150
The View Menu

The View menu contains the following options and commands for managing
the view in the OCR Analyzer:

Full Screen Maximizes the window size.
Engine Display changes made to OCR Engines.
Changes
The OCR Analyzer contains a powerful tool,
which allows you to refresh OCR parameters
once they have been changed in the Visual
Designer. Rather than run all the run time
modules again, the user may click the Refresh
button to reload the engine parameters. When
you click the Refresh button, the system checks if
any changes were made in the engines. If so,
they are written to a text file and can be
displayed using this option.
EFI Recognition The EFI Recognition Statistics window displays

Statistics OCR recognition results, information culled from
Export files. It includes data about the
identification method and match code statistics.
Statistics may be viewed in several ways:
Sorted by form types for each flow.
Sorted by pages per form type.
Sorted by EFIs per page.
Sorted by batches per EFI.
(The EFI Recognition Statistics window is
explained in greater detail later in the chapter.)
Last Process After processing, information is saved to a file

Times about the average length of time for recognition
for all the fields recognized in an EFI. Use this
option to view the information about average
recognition time for the form.

Licensed View a list of engine licenses.
Engines
151
The Options Menu

The Options menu contains the following options and commands:

Export Paths The path from which the data is received.
View Log View the debug logger.

Information
OCR Analyzer Modes

The OCR Analyzer interface offers three modes:
Process Mode
In this mode the user selects the parameters for the testing process. The actual
processing is then performed.
Form View Mode

After the processing is done, the user uses this mode to view a log of processing results.
Field Statistics
Testing results are compiled into statistical tables, which are shown in different
views in this mode.
152
Interacting with the Designer

The two buttons on the bottom of the control panel are used to interact with the Designer program:
Button Choose this to

Activate the Application Visual Designer.
Clicking this button activates the Visual
Designer program. If the program is already
active, clicking the button moves it to the front.
Refresh engine parameters. After changing the

engine parameters in the Designer, rather than
run all the run time modules again, the user may
click the Refresh button to reload the engine
parameters. This considerably simplifies retesting
changes in the engine parameters.
Note: This refresh process only applies to

engine parameter changes. If you make
changes to field parameters or to the EFI or
any other changes in the Designer, you must
erase the Export files that you created, and
go through the entire run time workflow from
start (input) to finish (export). You may then
perform OCR Analyzer analysis.
153
Process Mode
In this mode the user selects the parameters for the testing process. The actual processing is performed.
Using the Process Mode Tools

The tools which appear in different parts of the Process Mode desktop offer tool shortcuts
for accessing area-related commands and options. To find out the name of the button, place
the cursor anywhere on the button. A tool tip appears below it.
Tool Choose this to

Reload list of batches.
Deselect all items (batches or EFI’s, depending on the context).
Select all items (batches or EFI’s, depending on the context).
Once you have configured all the parameters, press the Process
tool to start analysis.
Once you have configured a query, you may save it to a file,

using this export button.
Import query configuration from a file. Once you have saved

query configurations to a file, you may retrieve a previous
setting by using this button.
154
Using the Process Mode

To start the process, choose a flow to be tested from the Flow combo box in the upper left.
The remaining parameters are configured according to the selected

flow.
Once you have selected a flow, the Batches list shows batches associated with the flow. For each batch
the following information is displayed:
A checkbox, via which you specify whether or not to test a specific batch.
The name of the batch.
The number of pages in the batch.
To select all batches
To select all batches, click the Mark Item tool.
To deselect all batches
To deselect all batches, click the Unmark Item tool.
You must then select which EFI’s you wish to process. The EFI list shows EFI’s associated with the
flow. Use the check boxes to the left of the EFI’s to select, which EFI’s will be tested.
To select all EFI’s
To select all EFI’s for testing, click the Mark Item tool.
To deselect all EFI’s
To deselect all EFI’s click the Unmark Item tool.
Selected Fields that you wish to test from the Flow Tree Viewer. The user may choose to view fields by
forms or by engines.
If viewing by forms, the tree contains Form nodes and Field sub-nodes of these Forms (each Form node
in the tree contains a list of relevant fields). Each Form and Field node has a check box. If a form node is
checked, all relevant fields are automatically checked. If some of the fields in a form are checked, then
the parent node (the Form) will be checked and grayed.
If viewing by engines, the tree contains Engine nodes and Fields as sub nodes of these Engines (each
Engine node in the tree contains a list of relevant fields). An OMR node is also displayed in the tree,
containing all OMR fields.
Once you have selected an entire setup for testing using the Process Mode desktop, you may save the
query configuration and reload it at any time.
To save a query:
Click the Export Query to file tool.

To reload a query:
Click the Import Query from file tool.
After defining all the testing parameters, press the Process button to activate the Process
Activity dialog box:
155
Field
Processing
Information
Character
Processing
Information
Progress
Bar
Status Bar
Figure: Process Activity dialog box
156
The Process Dialog Box
In this dialog box, processing is actually activated. Start the processing by clicking the Run
button.
Control Buttons
Control buttons are used to activate and stop processing:
The Run button - This button activates OCR Analyzer processing.
The Stop button - This button stops the process.
Status Bar
The status bar at the bottom offers information about the following:
Indication of the processing stage (Processing, Dumping, etc.).
Information about the current batch number, current page number, and total number of pages in the
batch.
Information Displays
A run-time summary of the number of fields and characters processed are displayed in the Field
Processing Information and Character Processing Information areas. The following information is
displayed:
Total number of processed fields and characters.
Percentage of recognized fields and characters.
Percentage of unrecognized fields and characters.
Percentage of false positive fields and characters.
Exiting the Process Activity dialog box

When the process is finished, the dialog remains open until you press the Close button at the
bottom right.
157
Form View Mode

After the processing is done, the user uses the Form View mode to view the OCR Analyzer’s log of all the
comparison checks and analysis results.
To select this mode on the OCR Analyzer’s desktop, either click the Form View tool on the left side of the
desktop, or from the Select menu choose the Form View option. The Form View desktop appears:
Menu
Bar
Tool
Bar
Log
Viewer
Image
Viewer
Status
Bar
158
Using the Form View Mode Tools

The tools which appear in the top of the Form View Mode desktop offer tool
shortcuts for accessing commands and options. To find out the name of the
button, place the cursor anywhere on the button. A tool tip appears below it.
Tool Choose this to

The Back button displays the previous form in the
log.
The Next button displays the next form in the log.
The Previous Batch button displays the previous

batch in the log.
The Next Batch button displays the next batch in the

log.
The View Field Results button opens the Field

dialog box, allowing you to view detailed information
about the selected field.
The Show Advanced View button opens the

Advanced View window, which allows you to view
the image and manipulate it by rotating it or saving
part of the image to a file.
The Zoom In button is used to view details of the

image by enlarging the image.
The Zoom Out button is used to shrink the image.
159
Using the Form View Mode

The Form View desktop is divided into two areas. On the left side, there is a log of process results. Log
results are color-coded according to result type. Voting and engine results are also displayed. The
number of the batch and form currently in process are shown, including the total number of pages in the
present batch.
On the right side of the desktop, the image of the form currently being evaluated is displayed. The field
currently tested is framed in the form image with color-coding identical to that in the log, indicating
which type of recognition is taking place for each field.
160
List View Items

Following is a brief overview of what you can see in the List View:
Item This represents

The page icon to the left is accompanied
by the page number to the right.
The field symbol to the far left is

followed by the name of the field in bold.
To the right is the recognition result in
bold followed by the number of
characters recognized in [brackets].
The virtual engine symbol far left is

followed by the name of the virtual
engine. To the left is the recognition
result of the particular engine, followed
by the number of characters recognized
in [brackets].
The specific engine symbol far left is

followed by the name of the engine. To
the left is the recognition result of the
particular engine, followed by the
number of characters recognized in
[brackets].
To examine which a field in the image that appears in the log, click that field. Once you
click a field in the log list, this action will highlight the field line, which also highlights a
frame around the same field in the image in a matching color. Any unrecognized characters
are displayed in deep blue. False positive characters are displayed in red.
Similarly, clicking a field in the image will highlight it in the log list. To view the image in
greater detail, use the zoom controls to enlarge or shrink the image.
View Field Details

To see further information about a particular field, select (click) the field, then click the View Field
Results button or double click a field to open the Field Results dialog box. This dialog box offers
detailed information about a selected field:
161
Field/
Region
Identifier
Image
Viewer
Field
information
Status
Bar
Figure: Field Results Window

FieldIdentifier
The name of the field currently being examined is displayed in the top left combo box. (Other general
information pertaining to the field is displayed on the status bar. This includes the batch name, form
name, page number of the field and EFI.)
To navigate to another field in the same form, simply select a different field from the combo box. You
may navigate to the previous/next instance of the same field within the current batch or the following
batch using the blue arrow keys in the tool bar.
Region Selection
The name of the ROI currently being examined is displayed in the number combo box directly to the
right of the Field Identification box. If a field is comprised of multiple regions, you may choose which
region to examine. The region is chosen by its place in the field (1st, 2nd, 3rd, etc.). To choose another
region simply type the appropriate location number in the box, or use the spin-arrows to advance from
region to region, or click on the region. If the field contains only one region, this text box is disabled.
The Image Viewer

The Image Viewer displays information from a scanned form, zoomed to the field currently being
examined. The recognition area of each region appears within a frame, with the selected region
highlighted in gray.
You may select which image information to display by using a right mouse button menu, available by
putting the cursor anywhere within the image and clicking the image. Click the right mouse button to
activate a pop-up menu that contains the image display options. You may select to zoom in on a Field
Frame, Region Frame, Region Number or Character Frame.
Field Results Table

The Field results table shows a wealth of recognition information about the field currently being
displayed, or if the field has multiple regions, about the region, currently displayed.
Each character in the field/region is shown in a different cell in bold style.

This information includes:
Typist results
162
Voting result
Voting results confidence levels (in brackets)
Unrecognized or False Positive characters are marked in blue or red, respectively.
Engine results
Engine results confidence levels (in brackets).
Engine guesses for the selected region
Engine guesses confidence level (in brackets). Up to 3 guesses are displayed.
You may navigate through cells in the table using the scroll bar.
If you select a cell in the table that pertains to a different character than the one highlighted in the image,
the segmentation rectangle changes in the image accordingly.
You may zoom in, zoom out, or use the Show Advanced Viewing button to obtain a more
detailed view of the image. To see the REG version of the image, click the View REG button.
To export results to a text file, use the Export button.
Show Advanced View

Use the Show Advanced View window, to further manipulate the view of the image. Click the Show
Advanced View button, to open the Show Advanced View window:
Figure: Show Advanced View Window
An image can be viewed in the Advanced View screen, allowing advanced actions such as
rotating and saving part of the image to a file. The toolbar features tools widely available in
the Integra system.
163
Field Statistics Mode

Use the Field Statistics mode to view different views of statistical results of the testing process.
To select this mode on the OCR Analyzer’s desktop, either click the Field Statistics tool on the left side of
the desktop, or from the Select menu choose the Field Statistics option. The Field Statistics desktop appears:
Menu Bar
Select
required
results view
Select
required
tab
Log
Viewer
Status
Bar
Figure: Field Statistics Mode
The Tools
Tool Choose this to

Export the statistics to a file.
The View Additional Statistical Details button opens the

Additional Statistical Details dialog box, allowing you to
view detailed statistical information about the selected cell.
The View Field Results button opens the View Field Results
window, which allows you to see more information about the
selected field.
The Last Statistic Result Tab
164
The Last Statistic Result tab allows you to view how many false positive, unrecognized and recognized
results were found for each field.
View Results By
Use the View Results By list-box to select which way you would like to view the statistics:
Percentage and Numbers
Numbers (only)
Percentage (only)
Sort By
Use the Sort By list-box to select how to view the statistics:
Numbers
Percentage
The statistics table can be sorted by any column, using numbers or percentage.
The View Field Results button opens the field window, when the cursor is pointed at a cell within a
field row. Or, simply double clicking on any of the cells opens the field-window of the relevant field.
This opens the View Field Results window, whose functionality has been explained previously in this
chapter.
Clicking the Additional Statistical Details button will activate the Additional Statistical Details window
containing additional statistical details of the selected cell:
Figure: Additional OCR Statistics window
165
This window allows you to see information regarding each field including:
Percent of recognized characters
Percent of unrecognized characters
False positives
Empty results (no OCR results)
Empty export results
Number of unrecognized characters (asterisks) found per field
The total number of updated fields
The total number of fields.
This window allows you to see information regarding each character including:
Percent of recognized characters
Percent of unrecognized characters
False positives
Number of characters that the OCR recognition engine added
Number of characters that the OCR recognition engine deleted
Empty results (no OCR results)
Empty export results
The total number of characters.
To export results to a text file, use the Export button.
The Comparison To Previous Results Tab

The Comparison To Previous Results tab enables the user to see the difference between a previous
processing session and a current one. This important feature allows you to see whether your fine-tuning
is producing better results or not.
Menu Bar
Select
required
Select
required
tab
Statistics
Viewer
Status
B
Figure: Comparison To Previous Results Tab
The statistics table display current and previous results listed by false positives, unrecognized characters,
and recognized characters.
If there is a difference between the last result and the current, the improvement in the results is
represented by a green arrow pointing down.
A worse result is represented by a red arrow pointing up.
166
EFI Recognition Statistics

The EFI statistics screen is activated from the main menu. To view this information, from the View
Menu select the EFI Recognition Statistics option. The EFI Recognition Statistics window opens:
Figure: EFI Recognition Statistics Window

This window displays OCR recognition results. The Identification Method tab includes information
about the algorithm used for identification, i.e., the method used to recognize the batches’ EFIs.
Statistics may be viewed in the following ways:

For form types per flow.
For pages per form type.
For EFI’s per page.
For batches per EFI.
The Match Code tab offers details regarding match code statistics Match codes are internal codes used
to determine the identification method that is used to recognize and EFI. A view of the Match Code tab
is shown in the figure below:
167
Figure: Match Code Tab

The Match Code tab has two main display areas. In this figure, the batch name is listed to the left,
followed by the Match Code number. To the right, a graph shows the success rate of each batch name’s
EFI recognition.
168
Last Processed Time

After processing, information about the length of time for EFI recognition is saved to a file:
Figure: Last Processed Time File

To view this information, from the View Menu select the Last Processed Time option.
The fields that have undergone processing are listed in alphabetical order in the top area.
Following this is information regarding the EFI and EFI processing.
EFI Name lists the name of the EFI processed underneath it.
Total Time shows the processing time for all the fields.
Num of EFIs lists the total number of EFI’s processed in this processing run.
Avg. Process Time is the total processing time for all the fields divided by the number of EFIs
processed (Total Time/Num of EFIs).
Licensed Engines
To view engine licensing information, from the View Menu select the Licensed Engines option. A
window will appear listing the engine licenses currently resident in the Integra system:
169
Figure: Licensed Engines

Engines Changes
To view engine changes information, from the View Menu select the Engines Changes option. A
window will appear listing the engine changes made in the Visual Designer.
Figure: Engines Changes

In the above figure, Virtual engines changes are shown in the top part in detail for the engines named
BCOD, HandAN, and MachNum. Each change appears on a separate line, with engines listed
alphabetically and properties listed in appearance order. All properties, which have been changed, are
shown with original settings (if there was an initial setting) to the left of the arrow, and the new setting
listed to the right.
OCR Engine changes are listed beneath Virtual engine changes. In the figure above, a change has been
made to the Keep Enhancement property of the OCR Engine named OCRBCOD.
170
Chapter 19 Debug Logger

The Debug Logger provides users with a tool for debugging and trouble-shooting all Client Services
components, as well as all DLLs and executables of the product. The debug logger logs messages
generated by selected categories of action, triggered by the various components and system activities.
The logger also allows the user to determine the level of filtering for messages according to message
severity (errors, warnings etc.), category of action, origin, user source and so on.
Messages are transferred to logs that can be displayed in the log-window and/or saved to a log-file. The
Debug Logger window’s main menu bar allows the user to configure the log displays, the filters, and the
logging method (window or file).
The main menu bar drop down menus allows you to perform the following actions:
File Menu
The FIle menu allows you to manipulate the information shown in the debug logger window.
Figure: Debug Logger File Menu
Option What it does

Open Load a log file into the logger.
Save Selected Save the selected messages to a text file.
Save All Save all the messages to a text file.
Exit Exit the logger application.
Messages Menu
The Display menu allows you to manipulate the information shown in the debug logger window.
171
eFLOW Run Time Modules Manual Chapter 19 Debug Logger
Figure: Debug Logger Messages Menu
Use the Messages menu to perform the following actions:
Option What it does

Hold Disables automatic scrolling to the last
displayed messages. It is better not to use
this option, or at least minimize the time the
logger is in this mode. When the logger’s
buffer is full, calling processes will be
suspended.
Clear Clear all lines from the display in the debug

logger window.
Continue Logging Release the logger from hold state.
Minimum Severity Set the message severity threshold for the

filters for debug logger window display, and
which type of compilation unit will trigger
message collection by the filter. There are
six severity levels in ascending order of
severity: detailed debug, debug, informatory,
warning, error and fatal error.
Set max lines Set the maximum number of lines that the
debug logger window buffer can hold.
172
eFLOW Run Time Modules Manual Chapter 19 Debug Logger
Figure: Debug Logger Window Filter and Highlight
Filter and Sorting Options
Use the Filter Text option to select which debug messages to show (Include) or hide (Exclude).
Use the Highlight option to select which messages to highlight.
Click on a column title in order to sort the messages according to this column.
Click on the drop down list of a column in order to filter the messages according to its values.
Drag one of the column titles to the designated area in order to group the messages by this column.
Figure: Debug Logger grouped by Module
173
Chapter 20 Utility Kit

The eFLOW Utility Kit can be accessed through the menu eFLOW icon >
Utility Kit. The eFLOW Utility Kit screen is displayed:
Figure: Utility Kit Screen

Click on the required icon to launch the relevant option.
The following options are available:
CSM View
A utility for viewing/editing raw setup information and viewing collection
data.This utility enables the user to log on to eflow as any defined workflow.
Note: Never modify any parameter using this utility unless you are 100%
sure of what you are doing (or if you are instructed to do so).
Test Debug Logger

Shortcut for launching the eflow debug logger.
Basic Configuration
Launches the Basic Configuration application which allows the user to configure
eflow platform main definitions (paths, communication settings etc.).
eFLOW Folder
The main folder under which all "fixed" eFLOW data is installed (BIN, Help,
OCRs etc.)
eFLOW Data Folder

The main folder under which all "user" (usually modifiable) eFLOW data is
placed.
OCR Viewer
Lannches an application that displays a PRD file.
174
Index
main tasks.................................................10
A
examine ROI’s in batches .............................57
activate Portal module .................................. 59 Exceptions module..........................................5
application ...................................................... 8 Export
Application Visual Designer .......................... 3 main tasks...............................................125
applications management ............................. 14
F
ASCII output .............................................. 125
File Portal
B
Image gathering........................................61
Batch File Portal module...........................................4
adjusting the view .................................... 57 form
batch separators .............................................. 7 capturing.....................................................3
batch status icons.......................................... 35 storing ........................................................3
Batch Viewer................................................... 57 FormID
Examine ROIs.......................................... 57 invoke FormID module ...................... 88 ,72
Open Image ............................................... 55 forms
Print .......................................................... 55 batch ...........................................................8
Printer Setup .............................................. 55 organization of ...........................................8
separator .....................................................8
C
I
calculates statistical data................................. 5
color-code flows ........................................... 35 ICR..................................................................6
Completion interpret form entries.......................................8
Always ................................................... 111
M
data completion process......................... 109
invoking module .................................... 110 Module Activator components......................33
move back a field................................... 119 monitor collections........................................35
Never ..................................................... 111
O
Reject..................................................... 111
skip to next error.................................... 118 OCR ................................................................6
unrecognized data .................................. 109 OCR Analyzer design phase .......................147
Completion module ................................ 109 ,5 OCR Analyzer fine tuning ..........................144
Content Delivery module ....................... 125 ,5 OCR Analyzer menus.....................................150
Controller ....................................................... 4 OCR Analyzer module ....................................5
Delete All Batches .................................. 37 OCR Analyzer process................................145
Delete Batch...................................... 39 ,37 OCR Analyzer steps....................................146
Flow Filter .............................................. 39 OCR engines ...................................................8
Hold Batch.................................. 45 ,39 ,37 OCR Visual Designer .....................................3
Release Batch ....................... 53 ,45 ,39 ,37 OMR ...............................................................6
View Batch........................................ 39 ,37
convert captured data.................................. 125 P
create user groups ................................... 27 ,23 previously scanned forms..............................59
Process
D
default configuration .................... 90 ,74 ,70
data preparation .......................................... 145 FormID stages .................................... 87 ,71
data processing ........................................... 145 invoke processing........... 103 ,92 ,76 ,67 ,62
data query ................................................... 145 ManualFormID stages ................ 102 ,91 ,75
data results.................................................. 145 Recognition stages ...................................66
Design StandBy.................................. 90 ,74 ,70 ,65
basic objects and concepts ......................... 7 Process module...............................................4
digital images ............................................... 35
S
E
sample applications.........................................8
EFI.................................................................. 7 scan forms .....................................................59
Empty Form Image...............................See EFI Scan Portal module .........................................4
engine tuning .............................................. 145 scanner
Enterprise Manager.................................. 10 ,6 ISIS compatible........................................59
175
TIF files ................................................... 59 user management ..........................................23

system hardware architecture ......................... 3
W
T
Workflow Visual Designer .............................3
TIF................................................................ 59
X
U
XML output ................................................125
unrecognized data....................................... 109
176

eFLOW Run Time Modules PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

eFLOW Run Time Modules PDF

Transféré par

Droits d'auteur :

Formats disponibles

eFLOW Run Time Modules

Top Image Systems Training Department

© Top Image Systems

© 2009 Top Image Systems Ltd.

Top Image Systems eFLOW Run Time Modules Reference Manual

Manual FormID Toolbar........................................................................................................... 79

Chapter 1 Overview of eFLOW

Figure: eFLOW Unified Content Platform

TiS products include:

eFLOW Configuration and Architecture

eFLOW Visual Designer

The Application Visual Designer

The OCR Visual Designer

The Workflow Visual Designer

Integra Run-Time Modules

eFLOW platform modules consists of the: Controller, Designer and Statistics.

Content Recognition Modules

Among the many unique features of this module, in conjunction

eFLOW Enterprise Manager

Integra Component Breakdown

Figure: Integra Modules

Object/Concept Used for

Empty Form Image, or Physically, a form can have several variations - a

Separator Batch separators divide scanned physical forms into

Application An application is a collection of flows, forms, fields,

Figure: A Logical Application

Forms can be organized in several ways.

Figure: The Structure of a Scanned Batch

Chapter 2 Enterprise Manager

The eFlow Domain Controller

Invoking and Using the Enterprise Manager

Figure: Enterprise Manager main window

To create or delete a site (location where the application is used e.g. a

To create a new site:

Figure: Sites List

Figure: New Site Installation Window

4. Enter a brief description of the eFlow site in the text box.

Figure: New Site Created

Delete an eFlow Site

2. Choose Delete from the drop-down menu.

4. Click Yes, and the system will delete the site.

Figure: Applications List

Figure: Applications List

3. The New application installation window opens

Figure: New application installation window

1. Application Name 1. Enter a name for the application.

9. Click the OK button to commence application creation.

Figure: Progress window

Figure: New Application Created

Select the Default Application

To set an application as the Default application:

3. Select the Stop option.

Set Autorun Stations

The New Autorun Station dialog opens:

3. Select the station for autorun.

5. Select the secondary node, if one exists.

6. Set command line parameters, if any.

7. Select the number of instances of the station to be run on the machine.

8. Click OK to record the settings.

1. To delete an application, first select the application in the Application Explorer.

2. Click the right-mouse button to obtain the application drop-down menu.

4. Click Yes, and the system will delete the application.

Figure: Duplicate the Application screen