There are many cases where you might want to force a user to visually validate data, documents, or both in a workflow process.  You may want users to visually validate pages for scan quality before OCR, you may want users to visually validate extracted data, or you may want to set up a double-blind data entry process. No matter the reason, use one or more Validate Nodes in a Workflow whenever you need to confirm or modify a document or its data as part of the capture process.

Validate Nodes are used for:

• Task-based Security on the Workflow – Users may see the documents they need, when they need it, but only for the work assigned to them.
  
  

• Validation Actions –  One or more custom actions can be taken in a validation step, which could require user input or be system driven. Using multi-action Validate Nodes and multiple Validate Nodes in a Workflow GlobalCapture covers even the most complex capture scenarios.
  
  

• How Fields are Viewed  – Maximize efficiency and meet compliance goals by displaying only the Fields needed and in the order needed for each step in the validation process.
  
  

1. Drag the Validate Node from the Nodes Pane to the Design Canvas.
   
   

2. In the Validate Node Settings dialog that appears, enter a unique name and a description for the Node.
   

   
   
   

3. Optionally, enable RapidAdapt to allow any user with permissions to the Workflow the ability to create a RapidAdapt Template from the Validation Station.
   
   

4. With RapidAdapt enabled, you can assign a Template Group for the RapidAdapt Templates that users might create at the validate step.  When using RapidAdapt, always specify a Template Group to ensure the user generated Templates in a process don't mix in with Templates from other processes.  It will be much easier to manage your Forms Learning platform in this way.  Note thats version prior to 2.1 do not support Template Group assignment for RapidAdapt forms.  Customers using RapidAdapt are strongly encouraged to upgrade to take specific advantage of these features.
   
   

   1. Create one or more Template Groups in the Template Designer.
      
      

   2. Ensure that the Apply Only Selected OCR Templates setting in the the Classify Node that proceeds the RapidAdapt-enabled Validate Node is disabled.
      
      

   3. Select from the list of available Template Groups that appears when RapidAdapt is enabled.
      
      

5. From a user perspective, the Validation Station in GlobalCapture always requires valid data to be entered.  When using GlobalForms, there is the potential for data to be provided by the system, via the Resubmission system action.  The Data Validation checkbox is enabled by default to enforce Data Type or Length settings for Fields. This setting only applies to GlobalForms.  When it is unchecked, data provided by GlobalForms is allowed to be invalid for it's fields. It is always recommended you be sure the data provided conforms to the rules of any target fields to prevent errors downstream in the process.  For more information, see the Data Validation page.
   
   

6. Configure Security, Actions, and Fields settings (see below for details).
   
   

7. Click Save.

Set Security

Use the Security tab to define the Read, Write, and Modify permissions granted to GlobalCapture users or groups for each of your Validation Actions.

You can set GlobalCapture Workflow permissions from two places: the Manage Portals interface and individual Validate Nodes. Use the Portals permissions to allow administrative-level permissions for each Portal, including access to Workflows within the Portal. Use the much more granular Validate Node security settings for user permissions for just that one step in the Workflow process. For each validation step, you can assign a combination of Read, Write, and Modify permissions for users.

Some notes about permissions:

• Those with Portal administrative permissions do not need to be expressly secured to a Validate Node to be granted permissions to it.
  
  

• Users do not need to be granted Batch Portal permissions to be granted access to documents that need validation. This Batch Portal access, however, is restricted to the batches for which they have been specifically granted Validate Node security. From the Batch Manager they can view and validate documents, including opening them in the Validation Station for closer inspection. However, only Portal administrators are allowed to delete or remove documents from the process.
  
  

• When you modify user security in the Validate Nodes Settings it is applied to new processes entering the Node, not on-going processes. Any time you modify a Workflow, including when modifing a Validate Node setting, it is a good idea to first unpublish it to halt any new documents from entering, next check Batch Manager to confirm that any remaining documents have been processed through, and then implement your changes.
  
  

1. Select the Security tab and click the Secured Users & Groups Add (+) button.
   

   
   
   The icon to the left indicates a user (
   ), group  (
   ),  Square 9 User (
   ), or a User Notation (
   ).
   
   

2. You can select one or more from the Secured Users & Groups list and click the Delete (

   ) icon to delete them from the list.
   
   

3. In the User Security Settings dialog that appears, select the type of user or group:
   
   

   • Standard User – Click Standard User and select one or more users from the Available Users & Groups list, and then click Add.
     Use the scroolbar and the filter search box to find specific users or groups.
     
     

     
     
     

   • User Notation – Click User Notation. Enter an S9 Notation or type in a single brace ( { ), and choose from the list of available Notations. Click Add.
     At run time the S9 Notation property can be evaluated to apply specific permissions on an individual process basis. When a Workflow process enters the Validate Node, the S9 Notation value is translated. If values change while the process is still in the Validate Node, however, it will not affect the security already set by the S9 Notation. S9 Notations support users, Square 9 Users and groups of users, in that order. This means that it is possible for a group and a user to both be secured with one User Notations setting, if they have the same name.
     
     Please note that multiple users found within a MV Field or Table Field column are not supported for User Notation.
     
     

    

4. Once users or groups have been assigned to the Secured Users & Groups list, choose the document permissions for the Batch Manager and Validation Station.
   If you select more than one user or group and they have conflicting permissions, it is indicated by a dash. Resolve the conflicted settings and then save the configuration.
   
   

   • Read – On by default, select Read to allow users to see documents in the Batch Manager and, from there, launch them to the Validation Station. Field values can be viewed but not modified. The user is also allowed to view form data in GlobalForms, if it is installed. Note that data and documents configured as Hidden Fields will also be available to the user. Read permission is required for Write and Modify permissions.
     
     

   • Write – Leave Read enabled and select Write to allow users to enter or edit Field values in the Validation Station. This includes entering information manually, KeyFree Indexing, Validation Actions, and saving the document without taking any actions. The user is also allowed to enter and edit form data in GlobalForms, if it is installed.
     
     

   • Modify – Leave Read enabled and select Modify to grant users permission to perform document-level operations in the Validation Station. This includes: inserting, reordering, and deleting pages; bursting; deleting the document; and performing image clean up. This setting does not affect GlobalForms permissions.

    

   Remember that these permissions do not restrict users who have been granted administrator-level batch security.

5. Click Add.