Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

frappe-core-workflow冰沙核心工作流程

Agent Skill

frappe-core-workflow 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

582

周安装

24

GitHub Stars

87

下载量

190
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:frappe-core-workflow(冰沙核心工作流程)
来源仓库:https://github.com/openaec-foundation/erpnext_anthropic_claude_development_skill_package
仓库路径:skills/frappe-core-workflow
安装命令:
npx skills add https://github.com/openaec-foundation/erpnext_anthropic_claude_development_skill_package --skill frappe-core-workflow
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/openaec-foundation/erpnext_anthropic_claude_development_skill_package --skill frappe-core-workflow

简介

用于查找、检索和筛选相关信息。frappe-core-workflow 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 可结合来源仓库和原始 README 核验具体用法。
  • 安装前建议确认权限范围和维护状态,避免触发不必要操作。
  • 注意是否会触发联网、命令执行或文件读写,确保安全使用。

SKILL.md

Workflow Engine

The Frappe Workflow engine is a state machine that controls document lifecycle through configurable states, transitions, and role-based permissions. It governs when and how documents change status, who can perform actions, and what side effects occur on each transition.

Quick Reference

Workflow DocType            → Defines the state machine for a specific DocType
├── states (child table)    → Workflow Document State rows
│   ├── state               → Link to Workflow State
│   ├── doc_status          → 0 (Draft), 1 (Submitted), 2 (Cancelled)
│   ├── allow_edit          → Role that can edit in this state
│   ├── update_field        → Field to update when entering state
│   ├── update_value        → Value to set (literal or expression)
│   └── next_action_email_template → Email Template link
└── transitions (child table) → Workflow Transition rows
    ├── state               → Source state (Link to Workflow State)
    ├── action              → Link to Workflow Action Master
    ├── next_state          → Target state (Link to Workflow State)
    ├── allowed             → Role that can perform this action
    ├── allow_self_approval → Check (default: 1)
    ├── condition           → Python expression (optional)
    └── transition_tasks    → Link to Workflow Transition Tasks

Key Fields on Workflow DocType

FieldTypePurpose
workflow_nameDataUnique identifier
document_typeLink → DocTypeTarget DocType
is_activeCheckOnly ONE workflow per DocType can be active
workflow_state_fieldDataDefault: workflow_state
override_statusCheckPrevent workflow from overriding list view status
send_email_alertCheckEmail notifications with next possible actions

How the Engine Works

1. Activation and Field Creation

When a Workflow is saved with is_active = 1:

  • All other workflows for the same DocType are deactivated automatically
  • A hidden Custom Field (workflow_state_field, default workflow_state) is created on the target DocType if it does not exist
  • The field is type Link to Workflow State, with hidden=1, allow_on_submit=1, no_copy=1
  • Existing documents with empty workflow state get their state set based on their current docstatus

2. State Resolution

Every document under a workflow has a workflow_state field. The engine resolves available transitions by:

  1. Reading current workflow_state from the document
  2. Filtering workflow.transitions where transition.state == current_state
  3. Filtering by user roles: transition.allowed in frappe.get_roles()
  4. Evaluating transition.condition via frappe.safe_eval() (if set)
  5. Returning matching transitions as available actions

3. Applying a Transition

When apply_workflow(doc, action) is called:

  1. Load document from DB (fresh read)
  2. Get available transitions for current user
  3. Find transition matching the requested action
  4. Check self-approval: blocked if allow_self_approval=0 AND user is document owner
  5. Set workflow_state_field to transition.next_state
  6. If update_field is set on the target state, update that field
  7. Execute transition tasks (sync first, then async via frappe.enqueue)
  8. Handle docstatus change based on source/target state doc_status values
  9. Save/Submit/Cancel document accordingly
  10. Add workflow comment

Workflow and DocStatus Interaction

CRITICAL: The workflow engine controls docstatus transitions. You NEVER call doc.submit() or doc.cancel() directly on a workflow-controlled document. The workflow does it.

DocStatus Transition Rules

Source doc_statusTarget doc_statusEngine ActionValid?
0 (Draft)0 (Draft)doc.save()YES
0 (Draft)1 (Submitted)doc.submit()YES
1 (Submitted)1 (Submitted)doc.save()YES
1 (Submitted)2 (Cancelled)doc.cancel()YES
2 (Cancelled)ANYBLOCKEDNO
1 (Submitted)0 (Draft)BLOCKEDNO
0 (Draft)2 (Cancelled)BLOCKEDNO

ALWAYS define your states so that docstatus only moves forward: 0→0, 0→1, 1→1, 1→2. NEVER create a transition from a cancelled state or from submitted back to draft.

Non-Submittable DocTypes

If the target DocType is NOT submittable, ALL states MUST have doc_status = 0. The engine validates this and throws an error if any state has doc_status = 1 or 2 on a non-submittable DocType.

Workflow States

Workflow State is a separate DocType used as a master list. Each state has:

FieldPurpose
stateDisplay name of the state
styleCSS class for badge display (Primary, Success, Warning, Danger, Info, Inverse)
iconFont Awesome icon class

State Row Fields (Workflow Document State)

FieldPurpose
stateLink to Workflow State
doc_statusSelect: 0, 1, or 2
allow_editLink to Role — ONLY this role can edit the document in this state
update_fieldField to update when document enters this state
update_valueValue to set (string or Python expression if evaluate_as_expression=1)
is_optional_stateCheck — optional states are skipped in get_next_possible_transitions
send_emailCheck (default 1) — send email notification on entering this state
next_action_email_templateLink to Email Template
messageText message for the email notification

Workflow Transitions

Each transition row defines one possible action:

FieldPurpose
stateSource state (MUST exist in states table)
actionLink to Workflow Action Master (e.g., "Approve", "Reject", "Review")
next_stateTarget state (MUST exist in states table)
allowedLink to Role — ONLY users with this role see this action
allow_self_approvalCheck (default 1) — if 0, document owner cannot perform this action
conditionPython expression evaluated with frappe.safe_eval()
transition_tasksLink to Workflow Transition Tasks (v15+)

Condition Expressions

Conditions are Python expressions evaluated in a sandboxed environment. Available globals:

# Available in condition expressions:
frappe.db.get_value(doctype, name, fieldname)
frappe.db.get_list(doctype, filters, fields)
frappe.session.user
frappe.session.roles  # NOT available — use frappe.get_roles() outside conditions
frappe.utils.now_datetime()
frappe.utils.add_to_date(date, **kwargs)
frappe.utils.get_datetime(datetime_str)
frappe.utils.now()
doc.fieldname  # Access any field on the document (as dict)

Example conditions:

doc.grand_total > 50000
doc.department == "HR"
doc.grand_total > 50000 and doc.department != "Finance"

Workflow Actions

Workflow Action Master

Simple DocType with just a workflow_action_name field. Common actions: Approve, Reject, Review, Send Back, Cancel. Create these first before defining transitions.

Workflow Action DocType

Tracks pending actions for users. Created automatically when a document enters a state with outgoing transitions.

FieldPurpose
statusOpen or Completed
reference_doctypeThe DocType of the document
reference_nameThe document name
workflow_stateCurrent workflow state
userAssigned user
permitted_rolesTable MultiSelect of roles that can act
completed_byUser who completed the action
completed_by_roleRole used to complete

Workflow Actions appear in the user's "Workflow Action" list and can be acted on via email links.

Self-Approval Control

def has_approval_access(user, doc, transition):
    return (user == "Administrator"
            or transition.get("allow_self_approval")
            or user != doc.get("owner"))
  • Administrator ALWAYS has approval access regardless of settings
  • If allow_self_approval = 1 (default): document owner CAN approve
  • If allow_self_approval = 0: document owner CANNOT approve their own document

Decision Tree

Need workflow on a DocType?
├── Is DocType submittable?
│   ├── YES → States can use doc_status 0, 1, 2
│   └── NO  → ALL states MUST have doc_status = 0
├── Define states → Create Workflow State records first
├── Define transitions → Need Workflow Action Master records first
├── Who can edit in each state? → Set allow_edit per state
├── Need conditional transitions?
│   └── Use Python expressions with doc.field access
├── Need to block self-approval?
│   └── Set allow_self_approval = 0 on specific transitions
└── Need email notifications?
    └── Set send_email_alert on Workflow + email templates on states

Common Errors

ErrorCauseFix
WorkflowStateErrorDocument has no workflow_state setEnsure workflow sets initial state on creation
WorkflowTransitionErrorAction not valid for current state/roleVerify transitions table covers all needed paths
WorkflowPermissionErrorUser lacks role for transition, or self-approval blockedCheck allowed role and allow_self_approval
"Illegal Document Status"Invalid docstatus transition (e.g., 0→2)Fix state doc_status values
"Cannot cancel before submitting"Transition from draft (0) to cancelled (2)Add intermediate submitted (1) state

See Also

  • API Reference — Complete workflow Python API
  • Examples — Workflow configuration examples
  • Anti-Patterns — Common mistakes and how to avoid them
  • frappe-impl-workflow — Step-by-step implementation guide

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

31.44%
按下载量换算60

Claude

30.64%
按下载量换算58

Cursor

18.18%
按下载量换算35

Gemini CLI

10.1%
按下载量换算19

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills