Re-key Indexing

Do not allow the same user to perform Re-key indexing on a Batch if they performed Standard Indexing on the Batch: This setting is for double-blind and otherwise similar workflows employed by businesses requiring validation by two separate individuals for indexing data. For example, the first user would key in data to an index field in the first workflow step configured, and in the second workflow step, with this setting enabled, a second PSIcapture user would need to re-key the index data to ensure validation by a secondary user.

Decide what should happen if the batch contains re-key validation errors:

• Send items with errors to Exceptions Batch for data verification in Re-key Validation step. Original Batch will skip Re-Key Validation step: This option splits documents with validation errors into their own batch and removes them from the original batch. The original batch, now free of any documents with validation errors, then skips the re-key validation step and proceeds with the workflow.

• Send items with errors to Exceptions Batch for data verification in Re-key Validation step. Original Batch will not skip Re-Key Validation step: This option splits documents with validation errors into their own batch and removes them from the original batch. The original batch then still undergoes the re-key validation step regardless of the fact that there were no validation errors up to this point. This step can be used to adhere to company policies that require review by a third-party or additional individual within the organization regardless of the state of the data.

• Keep Batch together for data verification in Re-key Validation step: This option keeps the original batch together and does not split off documents with validation errors into their own batch. This function can be important for some company policies that require batches to be viewed only by specific individuals, or when administrators wish to avoid confusion with users by splitting batches. The original batch proceeds through all Index workflow steps regardless of the state of the data, unless the option Skip Re-key Validation step is enabled below.

Decide what should happen if the batch does not contain re-key validation errors:

• Skip Re-key Validation step: Moves the batch passed the re-key validation step since there is no data that needs to be re-validated.

• Do not skip Re-key Validation step: Forces the batch to undergo a re-key validation step regardless of whether there are validation errors or not.

Display re-key validation alerts in Re-key Indexing step: As detailed above, when this option is selected, the user is notified when the re-key value does not match the original value by an alert being set on that field. The user is not able to see the original value or verify which value to use.

Allow verification in Re-key Indexing step: As detailed above, if this option is selected, the user is notified of discrepancies between the original and re-keyed value and is prompted with the Re-key Indexing Validation Error dialog box to select which value to use.

Allow indexing in Re-key Validation step: By default, users can only input data into re-key fields during a re-key validation step, and even then, only if they have permission to do so (as detailed in the next topic). This option lets users enter indexing data in a re-key validation step and override this default setting.