01 / Draw the process
Draw the request, review, decision and document step in Camunda Modeler. The BPMN file defines the flow.
The platform
The diagram leads. The platform carries it out.
ProcessBlocks joins the Operaton BPMN engine with a workspace for people and a worker for automated steps. The process folder keeps the meaning of both sides together.
From diagram to everyday work
What happens to an expense claim?
The BPMN model drawn in the designer guides each request from submission to result.
02 / Give people their tasks
The employee sees a request form. The reviewer sees the next task and can approve or return it.
03 / Do routine work
The worker uses declared modules to send a message or create a document when the diagram reaches those steps.
04 / See what happened
The case history shows each step and the exact process version whose forms and rules applied.
Everything for one process
A process is a folder you can open.
The BPMN file tells the engine what happens next. The other files define what people see, the words they use, which reports and documents can be produced, and which actions are allowed. Together they are one version.
Illustrative folder: expense claim, version 1
- The process model
expense-claim.bpmnDrawn in Camunda Modeler. It defines the steps, decisions and hand-offs the engine follows.
- The forms people use
forms/Choose the questions and fields shown at each human task.
- Your wording
i18n/Use your own field labels, instructions and report terms in each language.
- Your reports
reports/Define which process data is counted and shown in reports.
- Your documents
templates/Design the letters, summaries and PDF layouts the process produces.
- Allowed tools and data
capabilities.tomlDeclare the modules, data and groups this version needs for review before activation.
- Optional rules
logic/Add Lua rules when a decision needs more than the diagram and existing modules.
The BPMN file defines the flow. Add the other files only when needed; all belong to the same reviewed version.
01
Review the whole process
The flow, forms, terms, reports and requested access can be inspected together before the version runs.
02
Take it with you
Export the folder, review it and install it on another ProcessBlocks installation.
03
Change safely
Publish a new folder version for new cases. Cases already running keep the version they started with.
Define, then use
The platform builds the working surface.
A process author describes what people need. ProcessBlocks turns those definitions into the application they work in.
Forms from fields
Specify field names, types, choices and rules in a form definition. The platform renders the form and validates submissions from the same definition. No custom form page is needed.
Your words, reports and documents
The process folder supplies labels in each language, report definitions and document templates. People see their process terms rather than internal file names.
Your corporate design
Set a colour palette and text wordmark once for the installation. The platform applies them across its pages and rendered forms; each process keeps its own content.
For people and operators
Work and operations share a platform.
The interface goes beyond viewing BPMN: it guides tasks and shows operators why a process is running or waiting.
Tasks and forms
Fields have types; the same declaration renders in the browser and validates on submission.
Reports, documents and archive
Define reports from process data, create documents from your templates and file results for authorized readers.
Operational view
Module configuration, active backends and failed steps each have a clear place.
Assistant access
An MCP interface lets an assistant work on a person’s behalf with the same groups and validation as the web UI.
Your process, your environment
Let’s talk about your first process.
We can show how a workflow becomes a versioned process folder, and which steps need no custom programming.
Get in touch