Skip to main content

Workflow History

Workflow history shows which steps were completed, who acted, and when decisions were made.

Use workflow history to understand the current status, identify blockers, and reconstruct approval paths.

What Workflow History Shows​

Workflow history can include:

  • task creation,
  • assignment changes,
  • status changes,
  • approvals,
  • rejections,
  • correction requests,
  • forwards,
  • comments,
  • automated processing steps,
  • export or completion events.

The exact detail level depends on the module and configuration.

Reading a Workflow​

To understand a workflow, read it from oldest to newest:

  1. How was the document created?
  2. Which status did it enter first?
  3. Who received the first task?
  4. Which decisions were made?
  5. Was the document forwarded or corrected?
  6. Which step is currently open?
  7. Who is expected to act next?

Identifying Blockers​

A workflow is often blocked when:

  • the current assignee is inactive,
  • the task is assigned to the wrong group,
  • mandatory metadata is missing,
  • a required approval is still open,
  • the document is in an error state,
  • a previous export or automation failed,
  • permissions do not match the current workflow step.

Audit Trail vs. Workflow History​

Workflow history focuses on process steps. The audit trail may contain broader technical and business events, such as imports, metadata changes, AI rules, warnings, exports, and system errors.

For support cases, both views can be useful:

  • workflow history explains the process path,
  • audit trail explains object events and automation.

Support Reconstruction​

When a workflow behaves unexpectedly, capture:

  • document ID,
  • current status,
  • current assignee,
  • last workflow action,
  • last audit trail entry,
  • expected next action,
  • user who expected to see or process the task.

This makes it easier to distinguish workflow configuration problems from permission or data issues.