Configure Record Type(s)

Now that the triggers are in place we can focus on the record type. The record type allows us to have preset variables so the people performing the indexing won't have to remember what variables to set. We will be using the record type fields in conjunction with the work triggers to push data through the system to perform all the required steps.


Basic Fields

There are 3 basic fields that we can use that will determine what to do with the data. They are @OCR, @SPLIT and @INDEX. 


@OCR - If we set this field to YES then the work trigger we defined earlier will act on this record and will OCR the documents. If we do not have this variable or we have it set to anything other than YES then the system will skip the OCR step.


@SPLIT - If we set this field to YES then the work trigger we defined earlier will act on this record and will cause the document splitting phase to occur. If we do not have this variable or we have it set to anything other than YES then the system will skip the split step.


@INDEX - If we set this field to YES then the work trigger we defined earlier will act on this record and will cause the indexing phase to occur. If we do not have this variable or we have it set to anything other than YES then the system will skip the indexing step.


@CLASSIFY - If we set this field to YES then the work trigger we defined earlier will act on this record and will cause the classification phase to occur. If we do not have this variable or we have it set to anything other than YES then the system will skip the classification step.


Optional Fields

Here are several optional fields that we can use that will determine what to do with the data.


@SPLIT_PageCount - This variable will be used by the auto-split process to automatically split the incoming documents by the number which is placed in the variable value. If it is absent or set to <=0 then this will be ignored.


@SPLIT_BreakCode - This variable will be used by the auto-split process to automatically split the incoming documents whenever the system finds a value on a page that matches this break code. This is handy when looking for bar codes or certain key words that are on the first or last pages of invoices. It can also be used with bar code separator sheets that will be discarded.


@SPLIT_KeepBreakPage - This variable will be used by the auto-split process to determine what to do with the pages where the split code or page count has triggered a split. We can keep or discard the break page and if we keep it we can specify whether the break page was on the first or last page of the document. Possible values are:

    • FIRST - This will tell the system that the break page is actually the first page of the document and it will be kept intact
    • LAST - This will tell the system that the break page is actually the last page of the document and it will be kept intact
    • Anything Else or absent - Any other value or the absence of a value or variable will cause the system to discard the break pages



Since we have 2 basic split methods, we actually have 2 options as to how to set up the record type. Choose the correct method below to continue.


Option 1: Page Count Document Breaking


Option 2: Break Code Document Breaking