top of page

Perceptive Content – Batch Reindex Form Overview

Main Use

Indexing documents are made easy by entering fields in the form and clicking the ‘complete’ button. This button routes the document to a different queue that runs a script to change the document’s index fields and custom properties to the fields entered by the user on the form. All fields and buttons can be re-named and there can be an unlimited number of fields. These fields can also be built to look up data from an outside source such as from a database or a web service.

The form can also have custom validation where when the user clicks the ‘complete’ button, the form will check all of the fields in the form to determine whether the fields are valid or not before routing the document forward.

An example validation would be checking whether a field is required or not. If the field is blank and required, the validation check will fail and the document will not route forward. The document then shows all of the failed checks on the bottom of the form and highlights the fields in question. The user can hover over the fields to see error messages specific to the field.

Adaptive Custom Properties

This creates the custom property fields related to the document type dynamically when the user changes the document type. This does not include composite custom properties but it does account for different types of custom properties such as date, flags, strings, lists, and numbers.

Date custom properties will allow the user to pick a date with a date picker. List and flag custom properties will be created as a drop down with all of the valid list values or ‘Yes’ / ‘No’ for flag custom properties. Numbers will have a validation rule that only allow users to type in numbers.

The form can also spot whether the custom property is required for the document type and forces the user to add a value for that custom property before the form can be routed forward.


The form has the ability for users to enter the page number(s) that the index applies to. When the form is routed forward, the script splits out the document into separate documents, and then indexes the documents with what the user entered for that document. The user can create as many documents as they want and can quickly pick all pages with the checkbox next to the page field.

This field can recognize ranges and single page numbers such as “1,3-5,7-8,10”.

On the top right corner, the form shows the viewing document number out of number of all documents created. When the user clicks ‘Next’, it creates a new empty document for the user to enter the indexes for the document or if the user is viewing an already created document and the next document is already created, the ‘Next’ button will just open up the next document. The user can also go to the documents already created by clicking ‘Previous’. The ‘Copy’ button will create a new document with the all of the fields from the viewing documents filled out. The user can drop documents by clicking the ‘Delete’ button.

Katherine Wu, Developer



bottom of page