Version list

The Version list page lists all saved versions of a Document Processor flow.

To access the version list, click the version count number displayed as a hyperlink under the Versions column.

Version status types

Each version has a status: Draft, Inactive, or Active.

  • You can use only flows marked as Active to perform inference, that is, to automatically process documents using the flow.
  • Only one version of the flow can be Active at a time. When you activate a new flow version, the previous active version becomes inactive automatically.
  • Multiple Draft and Inactive versions can exist simultaneously.
  • You cannot edit Active versions. You can edit the Draft and Inactive versions of a flow.

Activate and delete versions

To activate an inactive or draft version, select the check box in the Version list. The Activate and Delete buttons are displayed in the ribbon. Click Activate to make the version active. Use Delete to remove the version.

If the flow definition is incomplete or invalid, you cannot activate a Draft version from the Version list. To activate a Draft version, open it, verify the document classes, activities and prompts, and save it as Active.

When you activate an inactive version, you can carry forward extensions from the active version to avoid manual configuration.

The carry-forward option appears in the activation modal when the active version has at least one configured extension. Select the inactive or draft version, and then click Activate. In the activation modal, select the Carry forward extensions from the active version check box, and then confirm the action.

These are the carry-forward rules:

  • Extensions are carried forward only if the matching document class exists in the target version. If no match is found, carry forward is skipped entirely.
  • Entity Extensions: The prompt extensions of an entity are carried forward only if the entity name exists in both the current Active and target version. If the entity's name does not match, its prompt extensions are silently skipped.
  • Column Header Extensions: The prompt extensions of a column header are carried forward only if the same column header name exists in the target version. If the column header name does not match, its prompt extensions are silently skipped.
  • Key Identifier: Key Identifiers are carried forward only if the Key Identifier name matches the target version. Unmatched Key Identifiers are silently skipped.
  • Instructions and QA Instructions extensions: Instructions and QA Instructions prompt extensions are carried forward by matching the class name only. Any existing Instructions and QA Instructions prompt extensions in the target version are overwritten by those from the current Active version.
  • If Extensions already exist in the target version, then the newly added extensions from the active version override respective Entity Extensions, Column Header Extensions, Key Identifier, Instructions & QA Instructions extensions.

After activation, the target version becomes Active with the carried-forward extensions applied. The previously active version moves to Inactive.

For more information, see Extensions in Document Processor.