2023:Review Designer Guide

WIP	This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly. This tag will be removed upon draft completion.

The Grooper Web Client allows users to connect to a Grooper dashboard over the internet via a web server. This allows end-users to process review based steps in a Batch Process in a web browser, without the need to install Grooper on their own machine.

Designer Guide

Setting Up Review Views

In Grooper 2022, there is a single Activity for any human-attended review step in a Batch Process. This is the Review activity.

Whether your users are doing classification review, data review, image review or scanning, you're going to use the Review activity to do it all. Depending on what you want the user to do in that step, you will add one (or more) "Review Views". For example, if the step is intended to allow users to review Grooper's document classification, you'll add a Classification View. Then, the user will have access to the Classification Viewer when they process the Review task.

The following "Review Views" can be added to a Review step and executed in the Grooper Web Client:

• Classification View
• Data View
• Thumbnail View
• Folder View
• Scan View

General Information & Best PracticesAdding a Review ViewClassification ViewData ViewFolder ViewThumbnail Viewer

General Information & Best Practices

User-attended steps are added to a Batch Process by adding a Review step. We're going to look at the Batch Process we used to process invoice documents in the User Guide portion of the course. I have unconfigured the two Review steps in this process. Next, I will show you how they were configured from scratch. We will demonstrate the basics of adding a Review step first.

Select the Batch Process to which you want to add a Review Step. We have an unconfigured step added after the "Classify" step of this Batch Process, which we have selected. This will be our first Review step. In the Step Properties panel, select the Activity Type property. Select Review from the dropdown list.
After assigning the Activity Type, the very first thing you should do is change the name of your Review step. "Review" is a really general word. Do your reviewers a favor and name the step something more specific. It's best practice to rename the Review step according to the type of review work the user is going to be doing. You don't have to rename it, but you should. For example, we're using this Review step to review document classification. So we renamed it "Classification Review".
Next, we need to configure the Review activity, by adding the Review View (or Views) we want our users to operate. Right? WRONG First, it is also best practice to configure the Content Scope property for a Review step. The Content Scope property limits what Content Types a user has access to in the review module, such as when manually assigning a document folder a Document Type. Technically speaking, the Review step will work without this property configured. However, it is considered best practice to always assign a Content Scope regardless of the Review View you're configuring. Generally speaking, there's only one Content Model used throughout the Batch Process. In most cases, you will scope the Content Scope to that Content Model. In this Batch Process, we use the Content Model named "Invoices Model". So we've selected it for the 'Content Scope. Put another way, we don't want the users to have access to other models in the Project. "Invoices Model OLD" is an older, testing version of the production "Invoices Model" Content Model. "Purchase Orders" is a Content Model that pertains to processing purchase order documents, not invoices and is therefore outside of the scope of work for this Batch Process. Neither contain valid Document Types for the kind of work our Batch Process is doing. Configuring the Content Scope property is particularly relevant when configuring a Review step for reviewing document classification, as it will limit the Document Types the user can manually assign to document folders. However, even when configuring Review for other kinds of review work, it is still considered best practice to configure the Content Scope.

Adding a Review View

Depending on what type of review work you intend the user to do during the Review step, you will add and configure one or more Review Views, using the Views property.

To add a Review View: Select the Views property. Press the ellipsis button at the end.
This will bring up the Views collection editor. Press the Add button. Select a Review View from the list. In Grooper 2022, only the following Review Views are accessible through the Grooper Web Client: Classification View Data View Folder View Scan View Thumbnail View
The selected Review View will be added to the list. With the Review View selected, use the right panel to configure its properties, if needed. We will discuss each Review View in more detail next in this tutorial. Press the OK button when finished adding and configuring the Review View(s).
Once added, you'll see the Review View listed in the Views property. In the next tabs of this tutorial, we will talk about each of the Review Views and some common configuration considerations.

Classification View

Adding a Classification View allows users to use the Classification Viewer. This allows users to review document classification when processing a Review task. It's configuration is very basic. The only question you really need to ask yourself is "Are there any completion criteria that should be required of the user during review?" You can require any flags on document folders to be removed before completing the Review task. You can require all documents to have a Document Type assigned before completing the Review task.
To configure either or both of these completion criteria, select the Folder Criteria property. Press the ellipsis button at the end.
This will bring up a Folder Criteria list editor. Press the Add button to add a new set of completion criteria. The Level property allows you to choose at which folder level in the Batch heirarchy, the criteria should apply. Most typically, all your documents exist at the same folder level in your Batch (often at level 1). In most cases, you'll only need one folder criteria configuration added at a single folder level. The Resolve Flags property determines whether or not error flags will prevent the Review task from being completed. Turn this to True if you want to force users to clear any document flags before the task can be completed. The Require Content Type' property determines whether or not unclassified documents will prevent the Review task from being completed. Turn this to True if you want to force users to assign a Document Type to all document folders before the task can be completed.

Data View

Adding a Data View allows users to use the Data Viewer. This allows users to review data extracted during the Extract step of a Batch Process and manually enter field values for Data Elements in the document's Data Model. Your primary considerations when configuring the Data View will be two-fold. You should ask yourself the following questions: At what folder level in the Batch do the document folders exist? Do you want users to complete the Review task with invalid documents present in the Batch? If you do want the user to complete the Review task with invalid documents, do you want to throw an error flag on the document after the task is completed?
The Processing Level property determines the subfolder level at which documents should be reviewed. PLEASE NOTE: This is relative to the Scope configuration specified on the Review step. For example: If your Review step is scoped to the Batch level, and your documents exit at the first folder level below the root folder, you would set this property to Level1 (This is also the most common/default configuration). If your Review step is scoped to Folder and level 1, and your documents exist at the first folder level below the root folder, you would set this property to Level0 (This is effectively no different from the previous example. It would perform the same way, just with extra clicks on your part). If your Review step is scoped to the Batch level, and your documents exist at the second folder level below the root folder, you would set this property to Level2 (This is a common configuration when reviewing documents split from larger parent files). The Allow Invalid Documents property determines if the Review task can be completed when invalid documents with data validation errors still present in the Batch. The default here is False because most typically organizations want to ensure all data errors have been reviewed and corrected. However, there are situations where you have to complete the task with errors in order to move on to the next step. For example, if a reviewer can't verify a highly sensitive field, an invalid document might be moved into a new Batch for a higher level secondary review by an activity called Spawn Batch. In order to move to the next activity (Spawn Batch in this example) you'd need to turn this property to True. The Flag Invalid Documents property will throw an error flag on any document folder with invalid data. This is False by default, meaning if a document folder has one or more field with a validation error, the folder itself will not be flagged. If set to True it will be flagged. This can be useful in situations where you do need to complete the Review task with invalid documents. The flags will clearly indicate which documents are invalid after the task is completed.
FYI The Data Viewer behaves differently in the Grooper Web Client than in the thick client in one major way. The Auto-Load Next Invalid Document feature does not work in the Grooper Web Client. In the thick client, if this is set to True, when the user tabs out of the last field of a document, the next invalid document will be loaded in the review screen. Otherwise, the next available document in sequence is loaded. At the time of writing this article, the Data Viewer in the Grooper Web Client will always behave as if this property is False.

Folder View

Adding a Folder View allows users to use the Folder Viewer. This gives users a simple Batch viewer in the Review step.
Most commonly, designers will add a Folder View as a secondary Review View, as certain views obscure the traditional folder hierarchy of the Batch. For example, many users find it helpful to have a Folder View added with a Data View. The Folder View has the same set of configurable properties as the Classification View.

Thumbnail Viewer

Adding a Thumbnail View allows users to use the Thumbnail Viewer. This review module focuses on reviewing each individual page, allowing users to select a thumbnail from the review screen to bring up the page in the Document Viewer. Most typically, this interface is used to review the results of an IP Profile. There are two questions you should ask yourself when setting up a Thumbnail View: Are there any completion criteria you want to require? You can require the user to confirm each individual page in the Batch passes muster and/or any error flags on pages be removed prior to completing the review. Do you want to allow users to manually apply an IP Profile to pages during the Review step? And, if so, what IP Profiles do you want them to use?
There are two "completion criteria" properties available to the Thumbnail Viewer. The Resolve Page Flags property determines whether or not the Review step can be completed when pages are flagged in the Batch from a previous step. Turning this to True will require users to remove those flags manually before they can complete their task. The Require Confirmation' property determines whether or not the user must confirm each page before the Review step can be completed. Users can press the Enter key to confirm a page, placing a green checkmark on the page. Turning this to True requires the user to confirm all pages before they can complete their task. FYI: Confirming the page will also remove any flag on the page.
The Allowed IP Profiles property allows you to select one or more IP Profiles the user can apply to a page's image during Review. Use the dropdown list to select IP Profiles from your Project (or any referenced Projects) by checking the box next to the profile's name.

Click here to return to the top

Behavior Properties

Multiline ValuesDefining Required FieldsDefining Fields Requiring ValidationEnabling a Selection ListData Section Captions

Multiline Values

There are certain kinds of values you will want to wrap within a textbox across multiple lines. This will make it easier for a reviewer to view and edit longer entries. You can do this by enabling the Multiline property for string values. For example, we've enabled Multiline for this address value.
To wrap text within a textbox, you will enable its Multiline property. The Multiline property is available to both Data Fields and Data Columns. If configured for a Data Column, for every row collected, the cell will be collected/edited in a multiline textbox. Select either a Data Field or Data Column. Under Behavior, select the Multiline property. Change the property to Enabled.
FYI In the thick client you can choose to enable or disable word wrapping within the multiline textbox using the Word Wrap sub-property. In the Web Client, word wrapping is always enabled, whether or not this property is True or False.

Defining Required Fields

Data can be presented on a document in myriad ways. Sometimes a field may be optional. It will appear filled in on one document, but not on another. Other fields are filled in on every single document every times. In many cases, it wouldn't make sense to not fill these fields in. You would consider the document's data incomplete without it. For these kinds of critical fields, you can force a user to manually enter a value for a field if Grooper's data extraction fails to do so.

You do this by making the field "required". Required fields will alert the user a critical value was not collected in a variety of ways in the Data Viewer. The document will be marked as invalid. A data validation error warning will appear on the document. Upon entering the required field with a missing value a "Value is required" message will appear. If the Data Viewer is configured to only allow completion when all documents are valid, Grooper will not allow the user to complete the Review task until the field's value is filled in.

To make a field required, you will set its Required property to True. The Required property is available to both Data Fields and Data Columns. If configured for a Data Column, for every row collected, there must be a value present. Grooper will throw a data error for any cell not collected. Select either a Data Field or Data Column. Under Behavior, select the Required property. Change the property to True. You should be aware a "required" field only requires a value to be present. That doesn't mean it's the correct value. That's still up to the reviewer to determine if the extracted value matches what's on the document.

Defining Fields Requiring Validation

For extra critical fields, you may consider forcing a reviewer to validate a field, using the Requires Validation property. This will put the field in an error state, regardless of what was extracted, and remain in error until the user confirms the field is valid.

Fields requiring validation will alert the user a critical value was not collected in a variety of ways in the Data Viewer. The document will be marked as invalid. A data validation error warning will appear on the document. Upon entering the field requiring validation a "This field must be reviewed" message will appear. This message and the error will persist until the user manually validates the field by right-clicking it and selecting Confirm or using the F6 hotkey. Even if the collected value is correct, the user must validate the field in order to clear the error. If the Data Viewer is configured to only allow completion when all documents are valid, Grooper will not allow the user to complete the Review task until the field's value is filled in.

To force field validation, you will set its Requires Validation property to True. The Requires Validation property is available to both Data Fields and Data Columns. If configured for a Data Column, for every row collected, the user must validate the column's cell. Grooper will throw a data error for any cell not validated. Select either a Data Field or Data Column. Under Behavior, select the Requires Validation property. Change the property to True.

Enabling a Section List

The List Settings properties allow you to configure a drop-down selection list for the user. This will restrict the user to only fill in values from a pre-populated list. For example, imagine you have a "yes" or "no" checkbox field. The only two options are "yes" or "no". You can enter those values into a selection list so the user doesn't have to type out "yes" or "no" during review. Rather, they'd simply pick "yes" or "no" out of a drop-down list.

For example, the "Type of Report" field for this document, only has two options. It's either "Original" or "Amended" We can create a selection list for the user. That way, they can only pick "Original" or "Amended" for this field.
To enable a selection list, you will configure a field's List Settings properties. The List Settings properties are available to both Data Fields and Data Columns. If configured for a Data Column, for every row collected, the user can use a drop-down list to populate the column's cell. Select either a Data Field or Data Column. Under List Settings, expand the List Values property. Select the Local Entries property. Press the ellipsis button at the end to bring up a list editor.
In the List Editor, enter the selection items you want the user to choose from. Press OK when finished.
FYI The Restrict To List property is currently disabled for Web Review. Regardless whether this property is True or False, the list is always restrictive. This means the user will only be able to select something from the list you provide. They will not be able to free-type a value.

Data Section Captions

Grooper gives you the ability to "caption" your Data Sections. This is an expression based string value to give a section record a dynamically generated custom label. This can be particularly useful for multi-instance sections to better identify which section the reviewer is looking at on the document.

For example, we used a tax reporting form for an oil and gas drilling operation to demonstrate multi-instance section extraction in the Grooper Web Review User Guide. If anything in that section could be called an "id number" or just something that generally identifies the section, it would be the "production unit number" listed in each section. Using a Data Section's Caption property, we could dynamically generate a custom label for the section record, based on the extracted value of one of the fields in the Data Section.

This is controlled by a Data Section's Caption property. Using this property, you can enter an expression to dynamically populate a section record's caption. Select either a Data Section. Under Appearance, select the Caption property. Using the expression editor, enter an expression to generate the caption. In our case, we used the "8 Production Unit Number" Data Field's result to generate the caption for the section record, effectively labeling it "PUN [extracted value]". We used the expression below: "PUN " + _8_Production_Unit_Number

Click here to return to the top

Review Queues

Review Queues allow further control of what Batches and tasks Grooper users have access to. You can control the work presented to users in the "Batches" and "Tasks" pages with Review Queues. This allows you to better filter work to your users by defining ACL settings for Batch Processes and/or steps in a Batch Process.

• Imagine a situation where you have several Batch Processes running in your environment and several users reviewing work in Grooper. You may want to assign certain users to certain Batch Processes based on their experience with the kinds of documents in the document set or quality of their work.
• Imagine another situation where you want restrict the kinds of review your workers do. Maybe one group only performs data review and another only performs classification review. And maybe any of them can do document scanning.

You can also think of this as a "soft security" measure. By filtering out work available to users, the Review Queue acts as a kind of gatekeeper, controlling what comes across a reviewer's desk.

⚠

Please note this is not a "hard security" measure. There are conceivable ways in which a user assigned a certain Review Queue may still be able to access Batch content that is outside of their queue. For true "hard security", the best practice is to isolate that work in a separate Grooper Repository and restrict user access in the Security settings configured on the root node.

The general steps to create a Review Queue are as follows:

1. Add the users to the Users list at the root node of the Grooper Repository.
2. Create a new Review Queue.
3. Select which Grooper Users you wish to add to the Review Queue.
4. Then, the Review Queue can be implemented in one of two ways:
   1. On the Batch Process to restrict work accessed from the "Batches Page" of the Grooper Web Client.
      • Only Grooper Users listed in the Review Queue will be able to access Batches with that Batch Process in the "Batches Page" interface.
      • This will prevent users who are not members of the Review Queue from seeing any Batch using that Batch Process in the "Batches Page" interface.
      • Use this option if you want users to "pull" work from a list of active Batches.
   2. On a Review step of a Batch Process to restrict work accessed from the "Tasks Page" of the Grooper Web Client.
      • Only Grooper Users listed in the Review Queue will be able to start the Review task from the "Tasks Page".
      • This will prevent users who are not members of the Review Queue from seeing the Review task in the "Tasks Page"
      • Use this option if you want to "push" work to users, feeding them the tasks you want instead of allowing them to pick the Batches they want.

For more detailed information on Review Queues, please visit the #Review Queue article.

Scanning With Web Client

‼	COMING SOON!! This portion of the article is under construction.