Thin Client Verification can replace Verification in a workflow. Configuring Thin Client Verification is the same as configuring Verification. As a result, the following is a list of differences:

• This is a Web-based application so you may need to log on.

• Fields are saved and sent to the Thin Client Server only once all fields are verified by the operator. If there is a problem, users cannot close the batch, and any fields with verification errors need more attention.

• There is no status bar at the bottom of the window. Instead, there is a status footer inside the Web browser window.

• Pressing F1 launches the Web browser Help and not the Thin Client Verification Help. Instead, you need to click the Help option inside the application.

• Panes cannot be floated. Instead, unnecessary frames can be collapsed to maximize the space available to other frames.

• You cannot customize the toolbar, or rearrange the order of the toolbar.

• You cannot toggle automatic focus on and off.

• Script events that are based on focus, selection, and changes in the verification form, such as setting the zoom value for the Document Viewer, are now supported. In most cases the Enable scripted layout changes option needs to be selected in the project settings. For more details refer to the Thin Client Validation or Scripting Help for further information.

• Some script events are not available based on verification events. For more information, refer to the Scripting Help.

• You cannot create a folder by right-clicking on a document. Instead, you must right-click a folder or the root node of the batch.

• Opening batches automatically is done by enabling an option on the Open Batch window.

Configuring Thin Client Verification is very similar to Verification. As a result, this section only refers to the differences and unsupported features of the thin client. You can configure Thin Client Verification by following these steps: