Core concepts
The high-level tour explains what wasabi is. These pages go one level deeper into the ideas that let you model real business processes, not just data-entry screens. Everything here is part of the platform today.
Artifacts are the unit you author, and they come in four kinds: a form, a data source, a browser, or a template. When you publish, they compile into immutable, content-hashed snapshots with full provenance, so every app is reproducible and auditable.
Views shape data. A view is a pipeline that derives a fresh dataset from your live documents, much like a view in a database: it filters, groups, and aggregates records into a result that is computed on demand and always current. Views turn raw documents into totals, rollups, and reports without defining a new record type.
Browsers control presentation. A browser configures how a dataset is shown and what people can do with it: the columns, search, filters, facets, the detail view, and the actions on each record. Most browsers belong to a form, but a standalone browser backed by a view becomes a report or dashboard in its own right.
Workflows are business processes drawn as BPMN diagrams: user, service, and AI tasks wired together with events and gateways, run by a durable, event-sourced engine that survives restarts and waits for timers or external signals.
Message-driven processes let people advance work by acting on a document. A workflow can pause and wait, then move forward when someone clicks Approve or Reject on the record, independently of any single assigned inbox task, the way real approvals and fulfilment actually work.
Data transformation reshapes data between steps. Input and output mapping let every workflow step adjust the data on the way in and on the way out, picking fields, computing values, and restructuring nested data, all without custom code.
Expression scope is what an expression can see. Wherever an expression runs, its scope depends on the context: a form's fields, the running process and its variables, the current task, the user and their role, or the data a workflow step is carrying.