Batch Indexing

1. From the Unity Client home menu select Batch Processing.

2. When using Batch Processing, batches of files that have been scanned or swept into OnBase will appear under Scan Queues or Status Queues.

a. Select the Status Queue or Scan Queue that includes the batch of documents you want to index.

b. If documents have been scanned in the wrong scan queue, this can be fixed by locating the batch, right-clicking on the batch, selecting Send to and choosing the proper scan queue.

3. To begin the Indexing process you will need to find and select the appropriate batch and then click on Start Processing.

a. You can also right-click on the batch and select Index Documents(To select multiple batches hold the CTRL key while clicking the different batches).

4. When Indexing all the documents within the batch:

a. Select a Document Type if one has not already been selected.

b. Fields labeled with red text are required keywords.

c. When assigning the same Keywords to following documents within a batch you can simply click on the lock icon to lock-in the keyword you entered for one of the documents, and once locked-in you can simply move on to the next document and hit Index while keyword is still locked.

d. If a page should be added to the previous document, click the Append.

e. Double-click a keyword field label to add another instance of that keyword value.

5. Once you have completed indexing a batch, you will be prompted to choose one of these options: Save and Close, Review the Last Action or Save and Transition.

a. Choose Review the Last Action to return to the indexing panel, this option will not save any changes made.

b. Choose Save and Close if you are done indexing batches.

c. Choose Save and Transition to transition the batch to the next processing queue, Awaiting Commit.

Awaiting Commit

1. Awaiting Commit includes “all batches where indexing is complete, but the documents have not been committed to OnBase”.

a. Depending on specific system configuration set by your organization, any files moved to the “awaiting commit” queue may be automatically committed without users having to manually commit the files into OnBase.