A successfully executed Auto-Index profile means that any not null data has been returned from a data source. If a value is returned, and the Exit on Success box is checked, Auto-Index will not attempt to execute the next profile.
When multiple profiles are assigned to a document type the order the profiles are executed, and whether Exit on Success has been selected, will have a direct impact on Auto-Index performance and the data that is returned.
Expected Exit on Success behavior:
An invoice document type is configured for the following 5 profiles:
Name |
Database Table |
Expected Results |
Exit on Success |
Profile 1 |
Vendor |
Returns vendor name |
No |
Profile 2 |
Current Vouchers |
PO Number |
Yes |
Profile 3 |
Pending Vouchers |
PO Number |
Yes |
Profile 4 |
Historical Vouchers |
PO Number |
Yes |
Profile 5 |
Posted Checks |
Returns check number |
No |
The first profile is configured to return vendor information and is not flagged to Exit on Success because you want Auto-Index to proceed to the next profile. In the example above, additional voucher information is stored in one of three tables (Current, Pending or Historical), profiles 2 – 4 are configured to exit on success if information is returned. So if information is found in the current voucher table Auto-Index will not attempt to look for information in the Pending or Historical Vouchers tables. Profile 5 represents a profile configured to return a check number. Since check numbers are usually indexed to the invoice at a later date through Retro-Index, Profile 5 is placed last on the list.
![]() |
When configuring multiple profiles, always list Retro-Index profiles at the end of the list. If configuring profiles for both Auto and Retro-Index, configure your last Auto-Index profile to exit on success. |
Triggering the Auto-Index Process