Visual workflow designer
Place nodes, draw paths, maintain properties alongside. From the simple approval to the branching procedure — visible and manageable.
Model customer-specific processes visually, run them server- and client-side, extend them in an isolated JavaScript sandbox. Workflows pause on replies and events, resume cleanly and log every step.
// am Server, isoliert pro Mandant
if (antrag.betrag < 5_000)
route("auto");
else
route("genehmigung"); In the designer, approvals, applications, procurement and inboxes are built as visible diagrams — with the same building blocks as the portal. Per node you decide whether it runs server- or client-side, whether it waits for input or decides immediately.
Business rules sit in plain language on the gateway, edge cases live in an isolated JavaScript sandbox. What is modelled here also runs overnight, sleeps on replies and events, resumes deterministically and is logged step by step.
Visible, executable, isolated, pausable.
Place nodes, draw paths, maintain properties alongside. From the simple approval to the branching procedure — visible and manageable.
Some steps belong on the server, others on the case worker's form. The designer separates the two cleanly — without switching tools.
Customer-specific edge cases in an isolated sandbox, with access to the data model, separate from platform and other tenants.
// no access to the host system
export function onApprove(antrag) {
if (antrag.kofinanzierung)
signal("buchhaltung");
} Workflows can wait for a signature, a reply or an event. They sleep without binding resources and resume exactly where they paused.
For organisations that have established BPMN as the common language between business and IT. What is in the diagram runs in the platform. Existing models stay usable — no second system for execution.
BPMN 2.0 not as wallpaper but as an executable model. What is in the diagram runs in the platform — without a second system.
Read in BPMN XML from Camunda, Bizagi or Signavio — review, adopt. Existing modelling stays usable.
Dead paths, unconnected gateways, missing assignments and unclear correlations are flagged before publication.
More than two dozen capabilities, grouped into four areas — all part of one platform service, nothing is a third-party tool.
Design visually, structure cleanly, maintain multilingually.
Nodes, paths and gateways via drag and drop, with a properties pane and preview.
Create, import, validate. Executable diagrams instead of decorative models.
Model recurring sections once, reuse them in any workflow.
Task titles, hints, emails and letters — maintainable per language with comparison.
Approval, procurement, inbox, onboarding — as starting points to adopt.
Run reliably, pause cleanly, resume deterministically.
Steps server-side or on the case worker — declared separately, in the same model.
Workflows sleep on replies or events and resume deterministically — without binding resources.
AND and OR gateways run truly in parallel; at the join they merge cleanly.
Incoming events, webhooks and replies find the right instance — without having to guess IDs.
Plain-language rules where possible, isolated code where necessary.
Customer-specific code, isolated per tenant, with access to the typed data model.
Conditions on gateways and tasks, readably phrased, with Intellisense in the editor.
Workflow variables linked to the data model — types are checked.
Per node which role, which tenant, which data context — with clear defaults.
Maintain script building blocks centrally, embed them in multiple places, update them once.
See what is happening, step in when needed.
Every step logged — with inputs, outputs, duration and operator.
Open one instance, see every transition, condition and data state per node.
Play the workflow against test data before publication — without side effects.
Own workflows per organisation, area or process — visible only to those entitled.
What is modelled here orchestrates forms, tasks, letters and signatures — fed by CRM and case, visible in the portal and the app.
Workflows launch forms, inputs flow back. Tasks show exactly the form the procedure requires.
Modelled in the workflow, rendered in the portal — with the tenant's brand and rights.
Reach contacts, create dossiers, maintain history — automatically in the course of the workflow.
Applications become cases. Status and processing follow the workflow, not the mail inbox.
Tasks arrive mobile, with push and offline buffering — on the same data trunk.
Approvals are signed legally — directly in the workflow, without media breaks.
From any Absidion page, navigate to every other process and to the services that work across all of them.
A short demo where we're happy to answer your questions in person. No commitment, no sales theatre.