State Machines and Transition Rules

State machines in Corexar elevate standard choice fields into strictly governed processes: entities cannot jump erratically between arbitrary stages, and transitions are protected by validation rules.

Defining Lifecycle States

Each state in the workflow has a unique key, descriptive label, color accent, and lifecycle category:

• Initial State — assigned automatically when a new record is created (e.g., Backlog or Draft).
• Intermediate States — stages of active processing (e.g., In Progress, Under Review, Testing).
• Final States — terminal lifecycle points (e.g., Done, Rejected, Archived).

Directional Transition Matrix

Transitions dictate the permitted paths between states:

1. In the workflow editor, specify the source state (or "*" for any state) and the destination state.
2. Provide an action label (e.g., "Start Progress", "Submit for Review", "Request Changes").
3. Save the rule. Now only authorized transition actions appear on cards and boards.

Transition Guards & Restrictions

Enforce conditions that must be fulfilled before a transition is permitted:

• Allowed Roles — restrict who can trigger the transition (e.g., only QA leads can transition to Done).
• Required Fields — specify fields that must be filled before moving forward (e.g., Resolution Note or Estimate).
• Auto-Assignment — automatically reassign the task to a specific role or user upon entry.

Live Mermaid Diagram Preview

The editor continuously renders a clean visual diagram using standard Mermaid state syntax. Verify the integrity of your state machine and export Mermaid code directly into architectural documentation.