QAID # 17501 Published
Question / Problem:
What are the differences between KTM Validation and KTM Thin Client Validation?
Answer / Solution:
Kofax Transformation - Thin Client modules augment the distributed capture capabilities of Kofax Capture Network Server. They allow data editing and correcting tasks to be performed at Remote Sites, simply using a Web browser. No local software installation is required, so deployment and support costs are low.
Thin Client modules can be rapidly deployed by providing a specific URL and login credentials to the correct set of people, so they can start editing and correcting Batches immediately.
There are several differences between Thin Client modules and their rich client counterparts. The biggest difference is that Thin Client modules run in a Web browser, while rich client modules require software to be installed on the operator's computer. Detailed differences are presented below:
Differences between Validation and Thin Client Validation
- Thin Client Validation is a Web-based application, so users need to log on.
- There is no Status Bar at the bottom of the window in Thin Client Validation. Instead, there is a status footer inside the Web browser window.
- In Thin Client Validation, pressing F1 launches the Web browser Help and not the Thin Client Validation Help. Instead, users must click on the Help option inside the application toolbar or press
- Panels cannot be floated in Thin Client Validation. Instead, unnecessary panels can be collapsed to maximize the space available to other panels.
- Thin Client Validation does not support customization or rearrangement of the Toolbar.
- Thin Client Validation does not have the Confirm Document Toolbar option. All Documents are automatically confirmed when modified during Batch Editing.
- Thin Client Validation does not have the Clear All Fields Toolbar option.
- Rich Client Validation does not have the Show Field Names button. Field names are displayed on the Document image.
- Users cannot toggle automatic focus on and off in Thin Client Validation. There is no InPlace Editor in Thin Client Validation.
- Users cannot double-click on a word in the image to validate a field in Thin Client Validation (clicking will still add the text).
- Scripted buttons and script events that are based on focus, selection, and changes in the validation form are not supported in Thin Client Validation. The field confirmation event is supported, and can be used instead. For more information, refer to the Scripting Help.
- Table sums are not supported in Thin Client Validation.
- Auto-foldering is not supported in Thin Client Validation.
- Page rejection is not supported in Thin Client Validation.
- Character exact editing is not supported in Thin Client Validation.
- Thin Client Validation does not feature a separate Batch Editing mode.
- Instead, all Batch Editing operations that are supported by Thin Client Validation are available in normal operating mode.
|AXPRO||5.5||Thin Client Validation|