Notes for Reuse
If you rotate a page, all recognition results and extraction field data for that page is lost.
If your project has foldering enabled, the best practice is to use batch routing instead of the Tungsten Capture Partial Batch Export feature. This ensures that any rejected documents are sent to Tungsten Capture Quality Control, and that existing empty folders do not cause problems with the partial batch export.
Some of the following menu settings are only available in Edit Batch mode.
Your solution integrator may have disabled this setting.
Almost all editing functions that change a document are disabled for PDF documents. Therefore, you cannot delete pages, split a PDF document, or merge two PDF documents. However, you can rotate pages and reject, move, delete, or add sticky notes to PDF documents.
The KADMOS ICR recognition engine is no longer supported and available only when licensed for projects from an earlier Tungsten TotalAgility version.
The Edit Document window does not support to lasso data that expands beyond a single line of text.
The batch based samples are the only samples that support JPEG and PNG images. This sample only supports *.tif, *.txt, and *.pdf file formats.
It is important that you do not leave both settings enabled. This can cause unpredictable behavior.
In addition to a search string, you can also enter standard operators such as <>, <=, <=, <, <, and =, when querying a numeric or date field.
For example, if you enter a value of <10 into a numeric or date field, the search finds all records that have a value of less than 10. Any values in a string column that contain the search string, are returned as well. Using the same example, "House <1023>" is also found in a string field.
For database columns with the" string" type, it is also possible to use wildcards as part of the search text. If your solution integrator has already configured wild cards for this lookup, that behavior is overridden. For example, if you search for "%No," the wild card character is the start of the search, and the search returns "November," "Note," "Notice," etc.
This automatic update feature works slightly different for the Thin Clients. To ensure that combo boxes populated by dictionaries are regularly synchronized, an additional Thin Clients web.config setting is required to replicate the above behavior. Without this setting, a combo box is filled once and used as long as that project is cashed. This means that combo boxes are updated once for multiple batches using the same project. For more information on the new ForceDictionaryUpdate web.config setting, see the Thin Client Server Installation Guide.
Dictionaries referenced by validation rules are successfully updated, regardless of the web.config setting.
You cannot call page recognition from script using the Tungsten Clarity recognition engine.
If you edit the default configuration set, the corresponding settings in any configuration sets that inherit the default values may be overwritten. If you do edit the default configuration set ensure that any dependent configuration sets are still consistent.
The FineReader recognition engine will be deprecated in the next release of Tungsten TotalAgility. As a result, Tungsten Automation recommends that you use the OmniPage recognition profile for both page and zone recognition for all new projects. If you have existing projects that use one or more FineReader profiles, it is also recommended that you modify those projects to use a comparable OmniPage profile.
Associative Search Databases will be deprecated in a future release of Tungsten TotalAgility. As a result, Tungsten Automation recommends that you switch to a local fuzzy database or a remote fuzzy database via Tungsten Search and Matching Server.
The A2iA Zone Locator is now deprecated and no longer supported. The A2iA Zone Locator and the Check and Cursive Recognition engine remain for reference purposes only and are not meant for use in production. However, if you have used an A2iA Zone Locator in a previous release, it is possible to continue to use these locators at your own risk.
Ideally, migrate these locators to a supported locator method. Before migrating an A2iA Zone Locator it is necessary to install the Check and Cursive Recognition Add-On.
When you migrate an A2iA Zone Locator, the following behavior occurs:
-
If an A2iA Zone Locator is configured to use the CheckReader functionality, then it is migrated to a Check Locator.
-
If an A2iA Zone Locator is configured to use the FieldReader functionality, it is migrated to an Advanced Zone Locator that uses the FormXtra recognition engine . If a single A2iA Zone Locator has multiple zones then multiple FormXtra zone profiles are created, one for each zone. This enables you to configure unique settings for each zone.
See the Tungsten TotalAgility Installation Guide for more information on installing the Check and Cursive Recognition Add-On.
When opening a project created in Tungsten TotalAgility 7.0 or earlier, the encryption for the currently active configuration set is updated automatically.
If there are other configuration sets in a project it is necessary to update their encryption manually. To do this, open the Edit Configuration Sets window and set one of the inactive configuration sets to active and then save the project. Repeat this until all configuration sets in a project are updated and then select the original configuration set.
The ODBC 32-bit drivers are supported only. The 32-bit driver is found in the following location:
C:\Windows\SysWOW64\odbcad32.exe.
Statistics Viewer will be deprecated and no longer available in a future version of Tungsten TotalAgility.