Forms That People Actually Fill — Building and Driving Process Forms in Oumma
Forms That People Actually Fill — Building and Driving Process Forms in Oumma Most workflow tools give you a form widget and wish you luck. Oumma forms are first-class design objects: built in a visual builder, labeled in three languages, validated at launch and completion, and — because a form *defines a step's input — the thing that drives the engine when a step is completed.* Series: Oumma ·…
Oumma's form builder creates fully-functional forms that can be displayed at three different points in a process. At launch, the form becomes the "Create a dossier" form, which must be valid to start the process. During a human step, completing the form is the only way to submit the step. At a system step, the input schema plays the same role, declaring what the step consumes from the process context.
All three types of forms are designed in the same visual builder within the Forms tab. The builder allows for authorized field types, required flags, trilingual labels, and per-step ownership. The builder also includes AI functionality that can create forms from plain language or pasted JSON definitions. When a process reaches a human step, the form is rendered to the task view, with required fields gating the submit button.
The submitted values are checked against the schema and stored in the process context for downstream decisions. Documents attached to a process can also be analyzed by the AI and folded into the process context. This design ensures a single builder for all forms, three languages for localization, and a contract-based validation system to enforce process rules.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.