What problem does it solve? OrangeHRM drives all approval-style flows (leave, claim, recruitment, timesheet, review) through a single generic state machine table, and this Skill explains how to query, extend, and debug those (workflow, state, role, action) → resultingState transitions without reverse-engineering the schema. ## Core Features & Use Cases - State machine reference: Documents the WorkflowStateMachine entity, the eight FLOW_* constants, per-flow action constants, and the string-typed storage semantics of ohrm_workflow_state_machine. - Service API guidance: Covers AccessFlowStateMachineService methods like getAllowedActions, getNextState, and getActionableStates for permission checks, transitions, and approval queues. - Recipes and checklists: Provides patterns for executing transitions (compute next state, persist, dispatch event), seeding rows via migrations, and debugging why a role cannot take an action. - Use Case: When adding a new leave-approval transition, follow the checklist to add the action constant, seed the workflow row via migration, wire the domain service, and dispatch the notification event. ## Quick Start Ask the AI to explain how to add a new approval transition to the leave workflow using the workflow skill.
