workflow-approval-maintenance

Modify workflow approvals, role-based actions, and business_key generation with Flowable-compatible syncing.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/karonluo/pydtlms --skill workflow-approval-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-approval-maintenance
Source: https://github.com/karonluo/pydtlms/tree/main/backend/ai/skills/workflow-approval-maintenance
Command: npx skills add https://github.com/karonluo/pydtlms --skill workflow-approval-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adjusts, debugs, and extends workflow-driven approvals, role-based actions, business_key generation, and Flowable-compatible runtime/history sync for recruitment, scientific reports, outbound studies, and theses.

Core Features & Use Cases

  • Provides targeted guidance for modifying workflow definitions, actions, and role permissions across backend and frontend components.
  • Ensures business_key consistency, proper history logging, and alignment with Flowable-compatible state; supports validation and regression checks with available scripts.
  • Supports end-to-end maintenance workflows, including node/action changes, role mappings, and task detail updates across recruitment, reports, and theses.

Quick Start

Initiate a targeted maintenance plan for a specific workflow, implement changes in staging, and monitor results with a rollback safeguard.

Frequently Asked Questions about workflow-approval-maintenance

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

FAQPage Schema
How do I debug Flowable workflow approval nodes and keep history consistent?

Debug Flowable workflow approvals by modifying backend and frontend code alongside validation scripts. This maintains business_key consistency and syncs runtime state with task history for accurate approval node modifications.

How do I modify role-based actions in a Flowable workflow without breaking task history?

Modify role-based actions by updating role mappings and action definitions across frontend and backend layers. Validation scripts and SQL compatibility layers ensure task history integrity and business_key consistency during the extension.

What is the best way to generate and maintain business_key consistency across recruitment and thesis workflows?

Maintain business_key consistency by applying coordinated changes to backend generation logic and SQL compatibility layers. This ensures aligned runtime and history states across recruitment, scientific reports, outbound studies, and theses.

Can I extend Flowable approval workflows to support new business domains like outbound studies?

Yes, you can extend Flowable approval workflows to outbound studies by defining new workflow nodes, actions, and role permissions. The extension requires end-to-end maintenance covering frontend updates, backend logic, and validation scripts.

Why does my workflow approval task detail update fail to sync with Flowable history tables?

Workflow approval task detail updates fail due to uncoordinated frontend and backend changes that break business_key generation. SQL compatibility layers and validation scripts are required to restore runtime and history synchronization.