Short, practical guides to designing, building and running processes with Orkovia.
Run Orkovia on your own computer with Docker, sign in, deploy a first process and start an instance.
Step through a diagram node by node inside the designer, choose gateway branches, and watch variables change — without deploying anything.
Give a service task a pretend response, delay and failure rate, so you can run the whole process before the real system or worker exists.
When a step fails, the instance stops and an incident is raised. Here are the ways to get it moving again.
Move business rules out of code and into a table anyone can read: build a discount table, test it, and call it from a process.
Build the forms people fill in during a process: 22 component types, validation, conditional fields, versions and translations.
A worker is your code that does the work behind a service task. Here is the loop it runs, in Node.js, Python and Java.
Three ways a process can wait for something to happen. When to use each, with examples.
Move live instances onto a new version of a process, and cancel, retry or update many instances in one go.
Two records answer two different questions: what happened inside a process, and who changed something in the platform.
Call REST, GraphQL and SOAP services or send email straight from a service task — configured, not coded.
What carries over when you open a Camunda 8 (Zeebe) BPMN model in Orkovia, and what you need to fix by hand.
