10.0
Table Of Contents
- Installing ABBYY FlexiCapture 10
- Standalone Installation
- Distributed Installation
- System Requirements
- General information
- Preparing the Application Server for installation on Windows 2012
- Preparing the Application Server for installation on Windows Server 2008 R2
- Preparing the Application Server for installation on Windows 2003
- Installing the servers
- External components required for the correct operation of the system
- System components in IIS and their configuration
- This section describes the IIS configuration which is necessary for the operation of FlexiCapture. This configuration is configured automatically during installation and required no manual configuration. However, in case of errors this section can help you to check the settings specified in IIS.
- Application pools
- Authentication settings for FlexiCapture 10 Web Applications
- Handler Mappings
- ISAPI and CGI Restrictions
- Checking the operation of IIS
- Switching system components to 64-bit mode
- Database server
- Interaction of the system components
- Installing the stations
- Using Active Directory
- Using SMS
- Installing Remote Stations
- Updating your earlier ABBYY FlexiCapture 10 releases to Release 6
- Upgrading from ABBYY FlexiCapture 9.0
- Upgrading from ABBYY FlexiCapture 8.0 Professional
- Upgrading from ABBYY FormReader 6.5
- Managing Your Licenses
- Setting Up FlexiCapture 10 Distributed Installation
- Logging
- Working with Clusters
- Technical Support
© 2011 ABBYY. All rights reserved.
50
If the element had a name which was
allowed in version 8.0 but prohibited in
ABBYY FlexiLayout Studio 10, and
there was a reference to this element
using a short name in the AdvancedCode,
this element will be re-named during
conversion, but the short name in the
AdvancedCode is not changed. So, in the
advanced code, there will be a reference
to the element which doesn’t exist.
In AdvancedCode, the element
should be re-named manually.
The structure like this is now prohibited:
Let e = SearchElements.StaticText1;
e = SearchElements.StaticText2;
As the elements now have user-defined
properties, the elements of the same type are
not considered identical.
Change the mentioned structure as
follows:
Hypothesis e;
e = SearchElements.StaticText1;
e = SearchElements.StaticText2;
Incorrect usage of elements’ short names.
Example:
There are elements: SearchEle-
ments.A.A, SearchElements.A.B,
SearchElements.A.C.
In previous versions, it was possible to
use the following structure in the code of
element C: A.B
In ABBYY FlexiLayout Studio 10, such
a structure cannot be compiled. A is con-
sidered SearchElements.A.A, but this
element has not a B field.
A conflict may arise when short names are
used. In version 8.0, in case of conflict, the
high-level element was selected. In ABBYY
FlexiLayout Studio 10, the low-level ele-
ment is selected.
Use the full names of elements.
The following errors may occur during layout matching:
Error in element "SearchEle-
ments.StaticText", Pre-search relations
section: D:\Tests\ForConversion\1.txt
was not found.
In ABBYY FlexiLayout Studio 10, a refer-
ence folder for relative paths to the text files
used in the StaticText element was changed.
In version 8.0 the relative path began from
the batch’s folder (where the images are
stored). In ABBYY FlexiLayout Studio 10,
they begin from the project’s folder (the
folder which contains the .fsp file).
Place the mentioned text file to the
folder indicated in the message (for
this example, you should put the file
“1.txt” to the following folder:
D:\Tests\ForConversion\). You can
also change the path to the file.
Upgrading from ABBYY FormReader 6.5
In ABBYY FlexiCapture 10, the structure of projects is different, so the old projects cannot be used as they are. To be able to use
your templates and flexible descriptions created in ABBYY FormReader 6.5, please read the instructions below and take all pos-
sible issues and limitations into consideration.
Using ABBYY FlexiCapture Studio 1.5 projects (*.fsp) in ABBYY FlexiLayout 10
ABBYY FlexiCapture Studio 1.5 projects can be opened in ABBYY FlexiLayout Studio 10 – no conversion is needed. Please
note the following:
- Once the project is opened in ABBYY FlexiLayout Studio 10, it is permanently converted into FlexiLayout Studio 10 format
and can no longer be opened in ABBYY FlexiCapture Studio 1.5 after this point. Please make sure you create a backup copy
of all projects for ABBYY FlexiCapture Studio 1.5 before opening them in ABBYY FlexiLayout Studio 10. This is a safety
measure useful in the event you still need to open the projects in ABBYY FlexiCapture Studio 1.5.
- After opening a FlexiCapture Studio 1.5 project in ABBYY FlexiLayout Studio 10, you need to delete all processing results
and analyze all pages once again in order to finish converting the project.
Due to the changes in FlexiLayout language, some compilation errors may occur. In this case, you will need to correct errors and
re-compile FlexiLayouts. Please contact our support team if you need assistance. See Errors which may occur while converting
FlexiLayouts.
Using FlexiLayouts (*.afl) created in ABBYY FlexiCapture Studio 1.5
There are numerous changes in ABBYY FlexiLayout Studio 10 as compared with ABBYY FlexiCapture Studio 1.5. That is why
we recommend opening an *.fsp project in ABBYY FlexiLayout Studio 10 first to check that there are no errors, and re-compile
it, even though FlexiLayouts compiled in ABBYY FlexiCapture Studio 1.5 can be loaded into ABBYY FlexiCapture 10. See
Errors which may occur while converting FlexiLayouts
.










