1 views collected around this technical thread.
This article explains how to integrate the Camunda 7 workflow engine into a Spring Boot project, covering core concepts, required Maven dependencies, configuration files, database setup, process modeling, task types, gateways, and essential APIs for managing processes, tasks, and variables.
Activiti is a BPMN workflow engine that provides components such as Process, Repository, Runtime, Task, and History services, stores definitions, runtime data, and history in a relational database schema, and is used by deploying BPMN diagrams, starting instances, and managing tasks via its Java API.
This article explains how to design a multi‑level workflow approval system using the Activiti engine, covering process diagram creation, deployment, task handling, variable management, exclusive gateways, and complete project configuration with Spring Boot and an H2 database.
This article provides a comprehensive guide to Flowable, a Java-based BPMN 2.0 workflow engine, covering its concepts, BPMN elements, installation, configuration, code examples, and database schema, enabling developers to design and implement employee leave approval processes.
This guide walks through setting up a Spring Boot 2.2.11 environment with Activiti 7.1, configuring Maven dependencies, explaining the Activiti database tables, defining a BPMN leave‑request process, implementing service and controller layers, and demonstrating API calls to deploy, start, query, and complete the workflow.
This article explains how to integrate the Camunda 7 workflow engine into a Spring Boot project, covering core concepts, required Maven dependencies, configuration files, database schema, process modeling, task types, and detailed API examples for managing processes, tasks, variables, listeners, and permissions.
This article presents a comprehensive overview of the Comet workflow engine, detailing its background, architecture, key design concepts, graph‑based legality checks, plugin mechanisms, and practical use cases such as SRE automation, permission requests, and dynamic linear processes, illustrating how a flexible, low‑code platform can streamline enterprise business flows.
This article explains what a process engine is, distinguishes between processes and engines, reviews common process designer types, explores workflow, BPM and orchestration applications, and details the architectural components, design practices, and code examples for building robust BPM solutions.
The article details Bilibili’s Comet workflow engine—a low‑code, plugin‑extensible platform built since 2019 that uses visual DAG templates, graph‑based legality checks, and asynchronous execution to automate diverse business processes such as SRE automation, permission requests, and push‑task approvals, improving operational efficiency across mobile and web services.
This article provides a comprehensive overview of BPM process engines, covering their definition, design of workflow and BPM, architecture components, organization and form designers, implementation practices, sample BPMN XML, and related commercial opportunities, offering practical guidance for building and using process‑engine‑based solutions.
This article provides a comprehensive overview of process engines, covering their definition, core components, design patterns, implementation details, workflow and BPM applications, as well as practical considerations such as form and page design, permissions, and business opportunities.
This article explains what a process engine is, how it differs from traditional code implementations, describes various process designer approaches, compares Workflow and BPM, outlines the core components of a BPM engine architecture, and presents practical development steps and business opportunities, including a full BPMN XML example.
This article provides a comprehensive overview of process engines, explaining their definition, common scenarios such as workflow and BPM, various design approaches for process designers, form designers, and interfaces, and detailed architectural guidance for building and deploying BPM solutions in backend systems.
This article provides a comprehensive overview of process engines, covering their definition, core components, design patterns, implementation approaches, BPMN modeling, practical workflow and BPM use cases, and related commercial opportunities for backend development and operations.
This article provides a comprehensive overview of process engines, explaining their definition, relationship to workflows and BPM, design of process designers, various application scenarios such as workflow and BPM, detailed architectural components, implementation practices, and potential business opportunities, illustrated with diagrams and XML examples.
This article introduces the need for workflow engines, compares the three major Java‑based engines (Activiti, Flowable, Camunda), explains BPMN notation, and provides detailed guidance on using Flowable's Eclipse Designer, IDEA plugins, flowable‑ui, bpmn.js, and related Vue components to model, deploy, and manage business processes.
Learn how to replace tangled if‑else code with a visual workflow engine using CompileFlow, from setting up the designer and BPM files to binding data, methods, conditions, and executing a sample chicken‑training process, while understanding the underlying principles and practical tips.
This article provides a comprehensive tutorial on installing Flowable 6.6.0, deploying its UI, designing BPMN processes, configuring the database, using core Flowable APIs, and integrating the engine into a Spring Boot project with full code examples and deployment instructions.
This article explains what a workflow engine is, why it is used, compares different workflow types, introduces the three major standards BPMN, CMMN, and DMN, and details the core components and design considerations of business process, case, and decision engines.
This article provides a step‑by‑step guide on deploying Flowable‑UI, designing BPMN diagrams, configuring a Spring Boot backend, managing Flowable database tables, and using Flowable engine APIs to implement a complete leave‑approval workflow with code examples.