Comparing configuration versions

A version comparison shows how the orchestrator configuration a document was processed with differs from the version live now. It compares configuration only — not the document's own values, and not two sets of results.

What you'll need

• The IntelieDocs module visible in your left-hand navigation.
• A finished document whose orchestrator configuration has changed since it was processed.

If IntelieDocs isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.

Steps

1. Open the orchestrator’s Documents tab and select the document.

2. Select Update Available in the header to open Update to Latest Version. On an Exception document, Retry Submit opens the same comparison, titled Reprocess Document.

3. Differences are listed under Item, Old Version and New Version; a — marks an item on one side only. Smart Extract shows Field Details and Special Instructions; Smart Classes Class Details and Special Instructions; Smart Queue Classifier Details.

4. Select Use new version to reprocess on the newer configuration. To stay on the pinned one, select Keep old version, which changes nothing, or — from Reprocess Document — Retry with old version.

What success looks like

• Update started appears — or Reprocessing started, if you came in through Retry Submit.
• A retry sends the status badge back to Processing, and the page then refreshes itself until processing settles.

What the comparison leaves out

Name and description changes are deliberately not listed — only structural differences are. A version differing in nothing else reads No structural changes — only the version number changed. Added, updated and removed items are tinted green, orange and red, and each is labelled in text too, so nothing depends on colour.

If something goes wrong

Symptom	Likely cause	What to do
No Update Available in the header.	The configuration has not changed since, or the document has not finished.	Nothing to compare. On an Exception document, use Retry Submit.
Couldn't load version information. You can still retry with the current version.	The comparison could not be fetched.	Use new version is unavailable — retry on the pinned version, or reopen the document.
Retry Submit reprocessed with no comparison.	No newer configuration version exists.	Expected: the pinned version was reused.
Failed to update the document or Failed to retry the document.	The request was refused.	Check the status badge, then try again.

Next

• Re-running a document — the other header actions.
• Exceptions — when Retry Submit is what you need.
• Document statuses — what each badge means.