Ascaion
Product platform · Services · Workflow designer

Business logic, made visible.

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.

Workflow · application · approval
Nodes
Start
Task
Script
Gateway
Timer
Mail
S
Application
×
Amount?
Auto-check JS
Approval
Signature
E
Properties
Type
Script
Execution
Server
Sandbox
yes
Input
application
Output
route
Sandbox active
Workflow · designer
ModelDataCodeBPMN
S
Application
×
Amount?
Auto-check JS
Approval
Signature
E
Sandbox · auto-check
// am Server, isoliert pro Mandant
if (antrag.betrag < 5_000)
  route("auto");
else
  route("genehmigung");
One designer, one engine

Draw what should happen. Exactly that runs.

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.

Highlights

Four traits that make a good workflow.

Visible, executable, isolated, pausable.

01

Visual workflow designer

Place nodes, draw paths, maintain properties alongside. From the simple approval to the branching procedure — visible and manageable.

S
Application
×
Amount?
Auto-check JS
Approval
Signature
E
02

Server and client logic

Some steps belong on the server, others on the case worker's form. The designer separates the two cleanly — without switching tools.

Server
Run script
Call REST
Send mail
Client
Show form
Signature
Approval
03

Integrated JavaScript sandbox

Customer-specific edge cases in an isolated sandbox, with access to the data model, separate from platform and other tenants.

Sandbox · onApprove.js
// no access to the host system
export function onApprove(antrag) {
  if (antrag.kofinanzierung)
    signal("buchhaltung");
}
04

Pause and resume

Workflows can wait for a signature, a reply or an event. They sleep without binding resources and resume exactly where they paused.

Instance · #2026-0412
Startwaiting for replyResumeEnd
Waiting for reply paused
BPMN designer

BPMN 2.0 — executable, not decorative.

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 · procurement.bpmn executable
Application
Review
Application
Capture application
Domain review
×
approved?
Release
Reject
End
End
validated 7 nodes · 7 paths · 0 errors Procurement · executable
01 Executable BPMN diagrams

BPMN 2.0 not as wallpaper but as an executable model. What is in the diagram runs in the platform — without a second system.

02 Import existing diagrams

Read in BPMN XML from Camunda, Bizagi or Signavio — review, adopt. Existing modelling stays usable.

03 Validation of execution logic

Dead paths, unconnected gateways, missing assignments and unclear correlations are flagged before publication.

All capabilities

Designer, engine, logic, observability.

More than two dozen capabilities, grouped into four areas — all part of one platform service, nothing is a third-party tool.

Designer & modelling

Design visually, structure cleanly, maintain multilingually.

Visual designer

Nodes, paths and gateways via drag and drop, with a properties pane and preview.

BPMN 2.0

Create, import, validate. Executable diagrams instead of decorative models.

Sub-workflows

Model recurring sections once, reuse them in any workflow.

Multilingual texts

Task titles, hints, emails and letters — maintainable per language with comparison.

Templates & library

Approval, procurement, inbox, onboarding — as starting points to adopt.

Engine & execution

Run reliably, pause cleanly, resume deterministically.

Server and client logic

Steps server-side or on the case worker — declared separately, in the same model.

Pause & resume

Workflows sleep on replies or events and resume deterministically — without binding resources.

Parallel paths

AND and OR gateways run truly in parallel; at the join they merge cleanly.

Correlation

Incoming events, webhooks and replies find the right instance — without having to guess IDs.

Logic & code

Plain-language rules where possible, isolated code where necessary.

JavaScript sandbox

Customer-specific code, isolated per tenant, with access to the typed data model.

Rules in plain language

Conditions on gateways and tasks, readably phrased, with Intellisense in the editor.

Data-model mapping

Workflow variables linked to the data model — types are checked.

Permissions per step

Per node which role, which tenant, which data context — with clear defaults.

Reusable code

Maintain script building blocks centrally, embed them in multiple places, update them once.

Observe & intervene

See what is happening, step in when needed.

Execution log

Every step logged — with inputs, outputs, duration and operator.

Step-by-step trace

Open one instance, see every transition, condition and data state per node.

Simulation / dry-run

Play the workflow against test data before publication — without side effects.

Multi-tenancy

Own workflows per organisation, area or process — visible only to those entitled.

Absidion product platform

All processes and services at a glance.

From any Absidion page, navigate to every other process and to the services that work across all of them.

Next step

See the Absidion workflow designer in action.

A short demo where we're happy to answer your questions in person. No commitment, no sales theatre.

01 Request a demo