forge-business-flow-development

Develop end-to-end business approval workflows in Forge Admin with Flowable integration.

103|36|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/yaomindong1996/forge-admin --skill forge-business-flow-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-business-flow-development
Source: https://github.com/yaomindong1996/forge-admin/tree/main/.agents/skills/forge-business-flow-development
Command: npx skills add https://github.com/yaomindong1996/forge-admin --skill forge-business-flow-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developing business approval workflows in Forge Admin requires coordinating business table design, Flowable process binding, form integration, status state management, and database seed scripts, which is error-prone and time-consuming without standardized patterns. This Skill eliminates that friction by providing a complete, reference-backed guide for end-to-end workflow implementation.

Core Features & Use Cases

  • Dual workflow modes: Supports both code-first custom business workflows (for complex logic, custom tables, and non-trivial status repair) and low-code dynamic CRUD workflows (for standard business objects without custom service logic).
  • Reference implementation: Uses the sample purchase order approval flow as a canonical example, with full file maps, status transition rules, and BPMN configuration patterns.
  • End-to-end guidance: Covers every step from database migration and backend service implementation to BPMN model setup, App Center configuration, and end-to-end validation.
  • Use case: Ideal for building leave approval, purchase order review, expense reimbursement, or any other business approval flow in Forge Admin that requires integration with Flowable.

Quick Start

Use this skill to implement a new purchase order approval workflow for your Forge instance, following the code-first pattern with custom business tables and Flowable process binding.

Frequently Asked Questions about forge-business-flow-development

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

FAQPage Schema
How do I build a Flowable workflow in Forge Admin for business approvals?

Building a Flowable workflow in Forge Admin involves designing business tables, binding BPMN process models, configuring form permissions, and managing status states using reusable code-first or low-code patterns provided by the reference guide.

What is the difference between code-first and low-code workflow modes in Forge?

Code-first workflow mode supports custom business tables and complex service logic in Forge, whereas low-code mode handles standard dynamic CRUD objects without custom service code, both integrating with Flowable for process execution.

Does this workflow guide cover Flyway migration script generation?

Yes, the workflow development guide covers Flyway migration script generation to ensure database schema changes for business tables are version-controlled and applied consistently within the Forge platform.

How do I configure BPMN nodes for a purchase order approval flow?

Configuring BPMN nodes for a purchase order approval flow requires defining process transitions, setting up form permissions for each node, and implementing callback idempotency to handle status state management reliably.

Can I use this pattern for leave request and expense reimbursement workflows?

Yes, the standardized workflow pattern applies to various business approval use cases including leave requests, expense reimbursements, and purchase orders, providing end-to-end validation aligned with Forge's microkernel plugin architecture.

Why do I need callback idempotency in Flowable process integration?

Callback idempotency is required in Flowable process integration to prevent duplicate state transitions and ensure business data consistency when workflow callbacks are triggered multiple times during execution.