frappe-core-workflow

Manage Frage document workflows with programmable state machines, transitions, and permissions.

163|53|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/Frappe_Claude_Skill_Package --skill frappe-core-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frappe-core-workflow
Source: https://github.com/OpenAEC-Foundation/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-workflow
Command: npx skills add https://github.com/OpenAEC-Foundation/Frappe_Claude_Skill_Package --skill frappe-core-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Solves the challenge of configuring and enforcing robust, error-free document lifecycles in Frappe by modeling workflows as state machines with states, transitions, and permission rules.

Core Features & Use Cases

  • Define states with doc_status and edit permissions to control who can modify documents in each state.
  • Configure transitions with actions, next_state, and access control to guide document flow and prevent invalid moves.
  • Evaluate transition conditions using document fields and Python expressions to support complex routing.
  • Apply workflows to documents via API or UI integrations, ensuring consistent state progression and automatic auditing.

Quick Start

Create a new Workflow document for your DocType, define the initial and target states, add transitions, and then apply the workflow to a document.

Frequently Asked Questions about frappe-core-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Frappe workflow with states and transitions?

To set up a Frappe workflow, create a Workflow document for your DocType, define initial and target states with doc_status and edit permissions, add transitions with actions and access control, then apply the workflow to documents.

Can I use Frappe workflows on non-submittable DocTypes?

Yes, Frappe workflows apply to both submittable and non-submittable DocTypes, enabling defined states, transitions, conditions, and permissions across diverse business processes regardless of document submission status.

How do transition conditions work in Frappe document workflows?

Transition conditions in Frappe workflows evaluate document fields and Python expressions to support complex routing, ensuring documents only move to the next state when specific criteria are met.

What is the best way to enforce document state permissions in Frappe?

The best way to enforce document state permissions in Frappe is modeling workflows as state machines, defining states with doc_status and edit permissions to control exactly who can modify documents in each state.

Why does my Frappe workflow transition fail for certain users?

Frappe workflow transitions fail when users lack the configured access control for that action, or when document fields and Python expression conditions for the transition are not satisfied.