[{"data":1,"prerenderedAt":60},["ShallowReactive",2],{"legacy:engine\u002Fflow:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":59},"engine\u002Fflow","Workflow Engine - Flowable BPM Approvals & Business Flows - JEDP Digital Platform","JEDP Process Engine: Orchestrates approvals and business flows based on Flowable\u002FBPMN 2.0; supports countersignature, rollback, parallel processing, and timeout escalation, with handlers resolved according to organizational rules.","JEDP, Process Engine, Six Engines, Digital Platform, Lang Bowan","Shenzhen Langbowan Information Technology Co., Ltd.","index, follow","page-engines","https:\u002F\u002Fwww.jedp.cn\u002Fres\u002Fimages\u002Fproduct\u002Fplatform-overview.webp",[13,30],{"@context":14,"@type":15,"itemListElement":16},"https:\u002F\u002Fschema.org","BreadcrumbList",[17,22,26],{"@type":18,"position":19,"name":20,"item":21},"ListItem",1,"Home","https:\u002F\u002Fwww.jedp.cn\u002F",{"@type":18,"position":23,"name":24,"item":25},2,"Platform","https:\u002F\u002Fwww.jedp.cn\u002Fengines",{"@type":18,"position":27,"name":28,"item":29},3,"Workflow Engine","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Fflow",{"@context":14,"@type":31,"@id":32,"name":33,"applicationCategory":34,"applicationSubCategory":35,"operatingSystem":36,"inLanguage":37,"description":6,"url":29,"provider":41,"isPartOf":43,"offers":45,"featureList":52},"SoftwareApplication","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Fflow#software","JEDP Workflow Engine","BusinessApplication","Enterprise Digital Platform Engine","Web (browser access; SaaS multi-tenant, private deployment assessed by scenario)",[38,39,40],"zh-CN","zh-TW","en",{"@id":42},"https:\u002F\u002Fwww.jedp.cn\u002F#organization",{"@id":44},"https:\u002F\u002Fwww.jedp.cn\u002F#software",{"@type":46,"url":47,"availability":48,"priceSpecification":49},"Offer","https:\u002F\u002Fwww.jedp.cn\u002Fcontact?from=engine-flow","https:\u002F\u002Fschema.org\u002FInStock",{"@type":50,"priceCurrency":51},"PriceSpecification","CNY",[53,54,55,56,57,58],"BPMN Orchestration: Based on Flowable and BPMN 2.0 for process definition and version management, it supports common patterns such as sequential and parallel gateways and human tasks. Complex manufacturing approvals can be expressed, rather than being squeezed into lightweight tools that only have 'approve\u002Freject' options.","Handler Analysis: Parse the handler according to rules such as role, department, supervisor, and department head, and update it with changes in the organization's appointment effective dates. This reduces situations where hardcoding individuals causes workflows to fail extensively when the organization is adjusted.","Add Sign \u002F Rollback \u002F Transfer: Common collaborative actions in manufacturing approval can be configured and process traces are retained, meeting supplementary signing scenarios such as quality countersignature, engineering changes, and procurement designation, with responsibility traceable to individuals in the track record.","Timeouts and Upgrades: Node time limits, reminders, and escalation strategies can be configured to reduce the situation where a document 'sits in someone's to-do list'; the escalation path is still subject to organizational and permission constraints to prevent it from being arbitrarily transferred to unrelated personnel.","Linked with form permissions: Node can constrain field editing; submit, approve, and reject align with the business state machine to prevent the process from progressing while the document status remains in draft or 'Effective'.","Case Audit: Process trajectories can be traced, service compliance audits and accountability tracking; the strategy for in-transit instances after redefining in the design state should be explainable, without silently rewriting historical handling records.","\u003Csection class=\"product-detail-section page-section\">\n    \u003Cdiv class=\"detail-container\">\n      \u003Cnav class=\"breadcrumb\" aria-label=\"Breadcrumb\">\n        \u003Ca href=\"\u002F\">Home\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Ca href=\"\u002Fengines\">Platform\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Cspan>Workflow Engine\u003C\u002Fspan>\n      \u003C\u002Fnav>\n      \u003Cdiv class=\"product-detail\">\n        \u003Cdiv class=\"detail-header\">\n          \u003Cdiv class=\"detail-icon\">\u003Ci class=\"fas fa-project-diagram\">\u003C\u002Fi>\u003C\u002Fdiv>\n          \u003Cdiv>\n            \u003Ch1>Workflow Engine\u003C\u002Fh1>\n            \u003Cp class=\"detail-subtitle\">Based on Flowable and BPMN 2.0: Approvals and business flows can be orchestrated—add sign, rollback, parallel processing, and timeout escalation with assignee resolution according to organizational rules\u003C\u002Fp>\n          \u003C\u002Fdiv>\n        \u003C\u002Fdiv>\n        \u003Cdiv class=\"detail-content\">\n\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Engine Positioning\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">The workflow engine handles high-frequency approvals and cross-role collaboration for manufacturing enterprises: designated purchasing, quality nonconformance review, engineering changes, payroll lock, project changes, and more. Based on Flowable and BPMN 2.0, it supports serial, parallel, rollback, countersignature, and timeout strategies; task assignees can be determined according to roles, departments, superiors, department heads, and other rules, and can leverage the reporting relationships from the organizational engine.\u003C\u002Fp>\n            \u003Cp class=\"detail-lead\">With the form and permission engines, the flow is not a second directory: who can see a record, who can edit fields on a node, and whether a delegate has expired all sit on the same foundation. Design-time can help build or change flows and preview component permissions. Runtime can complete a review within that person's own permissions through the API. It does not skip node rules, and it does not take the decision away from the person.\u003C\u002Fp>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Where It Fits\u003C\u002Fh2>\n            \u003Cul class=\"pain-list\">\n              \u003Cli>Approvals rely on offline signatures or IM, if overdue no one escalates, during audits the complete trail cannot be found, and responsibility is unclear.\u003C\u002Fli>\n              \u003Cli>Branching, parallel processing, rollback, and countersigning are not clearly represented in lightweight tools, and complex manufacturing processes (quality countersigning, engineering changes) cannot be implemented.\u003C\u002Fli>\n              \u003Cli>If the handler is fixed to an individual, any organizational adjustment process will largely fail, forcing repeated revisions of the workflow diagram during implementation.\u003C\u002Fli>\n              \u003Cli>The business flow and approval flow are disconnected, the document status is inconsistent with the process instance, resulting in 'the process has passed but the document is still a draft'.\u003C\u002Fli>\n              \u003Cli>There is no standard for agency or transfer handling, responsibilities cannot be clearly explained in the process logs, and there is a lack of evidence for compliance and accountability.\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Capability Highlights\u003C\u002Fh2>\n            \u003Cul class=\"capability-list\">\n              \u003Cli>\u003Cstrong>BPMN Orchestration\u003C\u002Fstrong>\u003Cspan>Based on Flowable and BPMN 2.0 for process definition and version management, it supports common patterns such as sequential and parallel gateways and human tasks. Complex manufacturing approvals can be expressed, rather than being squeezed into lightweight tools that only have 'approve\u002Freject' options.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Handler Analysis\u003C\u002Fstrong>\u003Cspan>Parse the handler according to rules such as role, department, supervisor, and department head, and update it with changes in the organization's appointment effective dates. This reduces situations where hardcoding individuals causes workflows to fail extensively when the organization is adjusted.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Add Sign \u002F Rollback \u002F Transfer\u003C\u002Fstrong>\u003Cspan>Common collaborative actions in manufacturing approval can be configured and process traces are retained, meeting supplementary signing scenarios such as quality countersignature, engineering changes, and procurement designation, with responsibility traceable to individuals in the track record.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Timeouts and Upgrades\u003C\u002Fstrong>\u003Cspan>Node time limits, reminders, and escalation strategies can be configured to reduce the situation where a document 'sits in someone's to-do list'; the escalation path is still subject to organizational and permission constraints to prevent it from being arbitrarily transferred to unrelated personnel.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Linked with form permissions\u003C\u002Fstrong>\u003Cspan>Node can constrain field editing; submit, approve, and reject align with the business state machine to prevent the process from progressing while the document status remains in draft or 'Effective'.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Case Audit\u003C\u002Fstrong>\u003Cspan>Process trajectories can be traced, service compliance audits and accountability tracking; the strategy for in-transit instances after redefining in the design state should be explainable, without silently rewriting historical handling records.\u003C\u002Fspan>\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Works With Other Engines\u003C\u002Fh2>\n            \u003Cdiv class=\"platform-boost\">\n              \u003Carticle>\u003Ch3>Organization Engine\u003C\u002Fh3>\u003Cp>Rules for handlers such as superiors\u002Fdepartment heads depend on reporting relationships and the effective date of the position; when the organization changes, the process still operates according to the rules rather than failing on a large scale.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Permission Engine\u003C\u002Fh3>\u003Cp>Who can see the document and who can change fields at the node should be consistent with functional\u002Fdata permissions; long-term situations where one 'can approve but cannot view' should be regarded as a configuration defect.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Form Engine\u003C\u002Fh3>\u003Cp>Process attached to business forms; rejection and approval are aligned with the business state machine, and the approval conclusions are synchronized with the document status in a way that is explainable and auditable.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Dual Agents\u003C\u002Fh3>\u003Cp>Design-time helps build or change process definitions and can preview component permissions. Runtime helps complete reviews through the process API and does not go beyond that account's handling scope.\u003C\u002Fp>\u003C\u002Farticle>\n            \u003C\u002Fdiv>\n          \u003C\u002Fdiv>\n          \u003C!-- engine-depth:BEGIN -->\n\n          \u003Cdiv class=\"detail-section\">\n            \n            \u003Ch2>Typical breakpoints\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Breakpoint\u003C\u002Fth>\u003Cth>Common cause\u003C\u002Fth>\u003Cth>Control lever\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>After the organizational adjustment, the process largely failed\u003C\u002Ftd>\u003Ctd>The handler writes a fixed individual\u003C\u002Ftd>\u003Ctd>Rule Analysis + Effective Date of Appointment\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>The process has passed but the document is still a draft\u003C\u002Ftd>\u003Ctd>Business status not linked\u003C\u002Ftd>\u003Ctd>Pass\u002FReject the driver state machine\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>No trace of co-signing and transferring\u003C\u002Ftd>\u003Ctd>Standard collaboration actions not enabled\u003C\u002Ftd>\u003Ctd>Adding signatures\u002Frollback\u002Ftransfer leave traces for auditing\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Documents long pending tasks\u003C\u002Ftd>\u003Ctd>No timeout upgrade strategy\u003C\u002Ftd>\u003Ctd>Time Limits, Reminders, and Escalation Path\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>After the revision, the behavior of in-transit instances is unclear\u003C\u002Ftd>\u003Ctd>Version strategy undefined\u003C\u002Ftd>\u003Ctd>Continue using the old version en route or formalize the migration rules\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>The parallel branch takes effect as soon as one side approves\u003C\u002Ftd>\u003Ctd>Gateway condition error\u003C\u002Ftd>\u003Ctd>BPMN Parallel Convergence Rule Regression\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>External write-back triggers error node\u003C\u002Ftd>\u003Ctd>Integrated events are not idempotent\u003C\u002Ftd>\u003Ctd>Business Key + Node Trigger Condition\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n            \u003Ch2>Promotion and Acceptance\u003C\u002Fh2>\n            \u003Cul class=\"accept-list\">\n              \u003Cli>Sample three types of processes: non-conforming quality review, procurement changes, and project milestones, to verify the completeness of parallel, rollback, and additional signature trails.\u003C\u002Fli>\n              \u003Cli>The analysis result of the same document handler around the effective date of the job transfer complies with the rules; after the proxy expires, it will no longer appear in the candidate list.\u003C\u002Fli>\n              \u003Cli>Rejection\u002FApproval\u002FWithdrawal is consistent with business status, inventory, or order status, and can be interpreted in reverse.\u003C\u002Fli>\n              \u003Cli>Runtime can complete reviews within that person's own permissions through the API, and does not approve for someone else; operation logs can be traced to specific accounts\u003C\u002Fli>\n              \u003Cli>After the process definition is revised, the in-progress instance strategy should be documented in writing, and at least one in-progress order should be randomly checked.\u003C\u002Fli>\n              \u003Cli>The overdue escalation path can be demonstrated: the complete trajectory from reminder to escalation handler\u003C\u002Fli>\n              \u003Cli>Process definition revision records the BPMN version number and specifies the in-progress instance strategy in the release notes\u003C\u002Fli>\n            \u003C\u002Ful>\n            \n            \u003Ch2>Implement in stages\u003C\u002Fh2>\n            \u003Cul class=\"accept-list\">\n              \u003Cli>\u003Cstrong>Phase One\u003C\u002Fstrong>: high-frequency approval templates, handler rules, status linkage, traceable baseline\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Phase II\u003C\u002Fstrong>: Parallel\u002FJoint Approval, Timeout Escalation, Additional Signing\u002FTransfer, Integration with Business State Machine\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Phase Three\u003C\u002Fstrong>: Cross-product process connection, integration triggers, operational backlog management, and design phase revision strategies\u003C\u002Fli>\n            \u003C\u002Ful>\n            \n            \u003Ch2>Create a landing prompt\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">Quality nonconformance review, engineering changes, procurement approvals, outsourced material issuance approvals, payroll locking, project changes, etc., should preferably all go through Flowable so that audit trails are centralized. Parallel countersigning is common in quality and process countersigning and should clarify the approval ratio and veto power; timeout escalation should distinguish between 'remind SQE' and 'escalate to department head.' When linked with MES\u002FWMS status, the process approval\u002Frejection should drive the business status, rather than having both sides change independently.\u003C\u002Fp>\n            \u003Ch2>When not to apply\u003C\u002Fh2>\n            \u003Cul class=\"pain-list\">\n              \u003Cli>Using a process engine to replace MES workstation scheduling or WMS wave algorithms—it orchestrates human review and collaboration, but does not replace execution algorithms\u003C\u002Fli>\n              \u003Cli>All business rules are crammed into gateway expressions with no documentation—complex rules should be combined with form status and integration backwriting\u003C\u002Fli>\n              \u003Cli>Asking the agent to approve for someone else is out of bounds — handling stays within that person's own permissions and is logged through the business API\u003C\u002Fli>\n              \u003Cli>Treat instant chat confirmations as a process substitute — key collaboration should still be auditable and replayable\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003C!-- engine-depth:END -->\n\n\u003Cdiv class=\"detail-section\">\n            \u003Ch2>Product Fit\u003C\u002Fh2>\n            \u003Cul class=\"related-cases\">\n              \u003Cli>QMS: Nonconformance Review, CAPA \u002F 8D Approval and Escalation\u003C\u002Fli>\n              \u003Cli>CRM: Quotation, Pricing, and Contract Approval Workflow\u003C\u002Fli>\n              \u003Cli>PMS: Change Control and Milestone Acceptance Approval\u003C\u002Fli>\n              \u003Cli>Dual Agents: Workflow Creation\u002FModification and Overtime Backlog Warning Delegation\u003C\u002Fli>\n              \u003Cli>Case: Nonconformance\u002FCAPA Process Closure\u003C\u002Fli>\n              \u003Cli>Insight: Why the CAPA Closure Rate Is Miscalculated\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"product-detail-cta scroll-reveal\">\n            \u003Ca href=\"\u002Fengines#engines\" class=\"btn btn-outline\">Back to Platform\u003C\u002Fa>\n            \u003Ca href=\"\u002Fcontact?from=engine-flow\" class=\"btn\">Book a Meeting\u003C\u002Fa>\n          \u003C\u002Fdiv>\n        \u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \n  \n  \n  \n  \n  \u003C!-- GEO:software-app:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \n  \u003C!-- GEO:software-app:END -->",1793937990235]