Workflow Transitions

Workflow Transitions

Workflow Transitions — FinKore specification text, requirements, and related reading.

On this page

Status

FinKore Core 2.0.4 stable.

Purpose

This document defines declared changes between workflow states.

Terminology

Source State is the required current State. Target State is the State after success. A Transition Request asks to perform a declared Transition. A Successful Transition changes current State after validation; a Rejected Transition does not. For a versioned Workflow instance, the declared Transition is selected from the instance's Bound Workflow Definition Version. A Transition Request can also include expected-current-state or expected-revision preconditions.

Requirements

  • WORKFLOW-TRANSITION-001 — A Transition MUST identify one declared Source State and one declared Target State.
  • WORKFLOW-TRANSITION-002 — A Transition is directed; declaring one direction MUST NOT declare or permit its reverse.
  • WORKFLOW-TRANSITION-003 — A Transition Request MUST match a Transition whose Source State is the instance's current State.
  • WORKFLOW-TRANSITION-004 — All applicable Transition Guards MUST pass before the State changes.
  • WORKFLOW-TRANSITION-005 — A Successful Transition MUST change the current State to its Target State exactly once.
  • WORKFLOW-TRANSITION-006 — A Rejected Transition MUST leave current State unchanged.
  • WORKFLOW-TRANSITION-007 — Transition validation and State change MUST be observable as one domain operation, with no intermediate State change exposed.
  • A composing domain should identify the context needed to describe a Successful Transition in an Audit Event.

Invariants

An undeclared Source-State-to-Target-State Transition must not succeed. Validation and State change must behave as one domain operation from the observer's perspective.

Examples

The following concurrency example is non-normative:

Current state: SUBMITTED
Process A requests: SUBMITTED → APPROVED
Process B requests: SUBMITTED → REJECTED

Core 2.0 defines whether each request is valid from SUBMITTED; it does not determine which concurrent request wins. That decision belongs to the application, persistence layer, or a future concurrency specification.

Given DRAFT → SUBMITTED, requesting that transition from DRAFT succeeds if all guards pass.

Invalid Examples

Requesting DRAFT → APPROVED when only DRAFT → SUBMITTED is declared must fail.

Errors

Except for a request from a terminal State, Workflow version mismatch, or Workflow state conflict, an undeclared Transition Request must report FINKORE_WORKFLOW_INVALID_TRANSITION. A request from a terminal State follows Terminal States, a failed Transition Guard follows Guards, a version mismatch reports FINKORE_WORKFLOW_VERSION_MISMATCH, and an expected-current-state or expected-revision conflict reports FINKORE_WORKFLOW_STATE_CONFLICT.

Open Questions

  • Should transitions have stable identifiers distinct from source and target state pairs?
  • What conflict semantics should a future concurrency specification define for simultaneous Transition Requests from the same current State?
Back to the top ↑