01 / Draw
Tasks, forms and decisions in the BPMN model. No custom code.
The workflow platform by DemandFlow
Draw workflows in BPMN, give people the right tasks and automate the rest. ProcessBlocks joins an open process model with clear rules for operation, data and change.
The diagram shows what happens and when, including to the people operating the process.
Levels 1 and 2 connect forms and existing modules to the diagram.
The engine, application and data stay in your environment.
One process. One folder.
Draw the steps in Camunda Modeler. Put the forms people fill in, your wording, reports and document layouts beside the diagram. That folder is the version you review, install and export.
Illustrative folder: expense claim, version 1
expense-claim.bpmnDrawn in Camunda Modeler. It defines the steps, decisions and hand-offs the engine follows.
forms/Choose the questions and fields shown at each human task.
i18n/Use your own field labels, instructions and report terms in each language.
reports/Define which process data is counted and shown in reports.
templates/Design the letters, summaries and PDF layouts the process produces.
The BPMN file defines the flow. Add the other files only when needed; all belong to the same reviewed version.
Tasks, decisions and hand-offs come from the BPMN file. The engine follows that model.
Choose the terms people see, and define the reports and documents this process produces.
The model and its supporting files travel together, so a change can be reviewed and installed as a new version.
Existing cases keep the model, forms and wording of the version they started with.
Learn moreFrom diagram to extension
Most processes can use a diagram and reusable modules. Custom business logic only needs a script when those do not suffice.
Tasks, forms and decisions in the BPMN model. No custom code.
Send messages, create or file documents as visible steps in the diagram.
Process-specific computations run in a constrained Lua environment.
Developers can build a compiled process handler for unusual integrations using the ProcessBlocks worker runtime.
Why this architecture
The diagram, the process folder and the platform each have a clear job. A new process does not need its own application.
Open the folder to see the actual flow, forms, wording, reports and permissions together.
Define the fields. ProcessBlocks draws the task form and checks what people submit.
A running case keeps its original process version while new cases use the new one.
Your process, your environment
We can show how a workflow becomes a versioned process folder, and which steps need no custom programming.
Get in touch