General tab - Extended Synchronization Settings window

Use the General tab to modify the extended synchronization settings.

The following Project settings are available:

Filename

Shows the full name (including the path) of the project file that was used for synchronization.

Description

A description that was set within the Project Builder project properties.

Copy project during publish

This setting is selected by default, causing the project file to be copied to a subdirectory of the Tungsten Capture installation every time the batch class is published. The path of the project file is saved to the custom properties for Server.

For a client/server installation and especially if you are using Tungsten Transformation with KCN Server this setting must be selected, otherwise Server may not have access to the project file.

For testing on a local system, it may be useful to clear this setting. This is especially true if you have a big database and publish the project very often, as a lot of disk space is consumed.

Send data to Tungsten Reporting

Clear this setting so that Tungsten Transformation does NOT collect statistical information for the reporting platform for the current batch class. This is especially useful for a batch class that is created for testing purposes only. However, statistical data for the modules in the workflow, such as when the module is started and closed, is still available and reported. (Default: Selected)

You can define for a field or table field not to gather any statistical data by clearing the Use for statistics setting in the field's properties in Project Builder.

The Send data to Tungsten Reporting does not affect any settings for the Transformation Statistics export connector. When an export connector is defined for a document class statistical data is gathered and can be viewed in the Statistics Viewer.

Statistics Viewer will be deprecated and no longer available in a future version of Tungsten Transformation.

Populate all index fields for read-only access in script

If this setting is selected, you can access all index fields of a Tungsten Capture document class in script during Tungsten Transformation processing. For each index field an XValue, AC_Field_<fieldname>, is created that can be accessed read-only in script. If this setting is cleared, the XValues are not created; however, you can access all mapped fields in script for read and write access. If needed, you can map a field to an index field and hide it from the user by not adding the field to the validation form or by hiding it on the form. For more details about XValues, refer to the Tungsten Transformation Scripting Help. (Default: Cleared)

This setting is enabled only if Tungsten Capture 10.0.2 (service pack 2) or a newer version is installed.

The number of document class index fields is also dependent on how Tungsten Transformation classes are synchronized to Tungsten Capture document classes. For example, if you map two Tungsten Transformation classes that have different fields to the same Tungsten Capture document class and map all fields for those classes, this document class ends up with index fields from both classes. That means that, if the setting above is selected, both Tungsten Transformation classes have XValues for index fields that are not needed for that class. During processing for each document a considerable number of XValues are created, which can cause performance issues when loading a batch. It is best practice in such a case to clear the Populate all index fields for read-only access in script setting.

Expose document UniqueID in script

Select this setting to make the Tungsten Capture UniqueID attribute for documents is available as an XValue on the XDocInfo level. The key is named "AC_UNIQUEID" and its value is read-only. (Default: Cleared)

Selecting this setting may result in some performance issues. Please ensure that you enable this setting only if it is required.

Delete empty batches on batch close

Select this setting to delete an empty batch. This is true for batches that bypass all user modules as well as a batch that is manually closed by a user during any user module.

Selecting this setting can cause problems if you are using partial batch release. A workaround is to use document routing to move all of your documents to other batches and then delete the empty batch that is left over.

Import bar codes as XDocument objects

When selected, this setting imports any bar code information recognized during scan and saves it in the XDocument so that it is available when that document is processed further.

For example, select this setting if you wish to use Enhanced Bar Codes for the Bar Code Locator.

For more information on Enhanced Bar Codes, refer to the Project Builder Help.