Forms, UI flow, server flow and what sits behind them. The lists below are not written by hand — they are generated from the same catalogue the Studio editors are read into, so the page cannot quietly fall behind the product.
Generated 2026-09-17 · Contract for design tools →
Every form sits on a 12-column grid. A component takes between 1 and 12 columns, and the row wraps on its own once they run out. Panels nest, so a layout is built by putting grids inside grids rather than by pointing at pixels.
CurePanel18 propertiesCureTabs13 propertiesCureToolbar18 propertiesCureNavigation2 propertiesCureButtonGroupHeading7 propertiesTextLabel9 propertiesCureText2 propertiesCureMarkdown2 propertiesCureImage27 propertiesDividerUInput7 propertiesUTextarea3 propertiesUEditor1 propertiesCureEditor9 propertiesUInputNumber4 propertiesUInputDate2 propertiesUInputTime1 propertiesCureDateTimeInput3 propertiesUCalendarUSlider3 propertiesUSelect8 propertiesUTreeSelect8 propertiesUCheckbox2 propertiesUCheckboxGroup3 propertiesURadioGroup3 propertiesUSwitch3 propertiesUInputTags1 propertiesUPinInput3 propertiesUColorPickerUFileUpload3 propertiesCureFileBrowser3 propertiesCureTableCureProgressTable9 propertiesCureCalendar15 propertiesCureMap21 propertiesCureGantt20 propertiesCureResourceScheduler26 propertiesCureKanban26 propertiesCureStatusFlow14 propertiesCureStatusTimeline9 propertiesCurePanelForms20 propertiesCureSvg5 propertiesCureMetrix6 propertiesCureCharts7 propertiesCureCirclePacking7 propertiesUBadge1 propertiesUAlert4 propertiesUAvatar3 propertiesUProgress2 propertiesUKbdUSkeletonUChipCureMorphNumber8 propertiesCureStatCard4 propertiesCureStatSection3 propertiesCureSvg5 propertiesUButton5 propertiesUFieldGroupUDropdownMenu2 propertiesEvery component inherits the same groups: binding to a field, display and column width, colour, variant and size, validation, per-role permissions, table settings and the form’s outer frame. On top of those, components have their own.
The data type decides which component a field gets by default — text, number, date, time, choice, boolean, file, or a reference to another record. The choice can be overridden per field.
Every component takes a customCss property, and panels additionally expose frame, title row, icon, collapsibility, background colour and elevation as ordinary settings.
Table, kanban, gantt, calendar, map, panel forms and status flow search out a set of records themselves — and the datasource need not be the form’s own.
When no component fits, CureSvg draws anything at all from a datasource, with your own JavaScript in a confined context.
Roles govern not only who sees a view, but which fields and which rows. The rules are evaluated on the server, not in the client.
UI flow runs inside the open form and sees the fields as the user sees them. Behaviour belongs here: conditional fields, calculations while typing, navigation between views, driving a map component. None of it needs a round trip to the server.
| After Modify | form.afterModify | Efter lyckad modify |
|---|---|---|
| After Submit | form.afterSubmit | Efter lyckad submit |
| Attachment Start/End | field.attachment | Bilaga start/slut |
| Button/Menu | field.button | Knapp eller menyval |
| Clear | field.clear | Fält rensas |
| Collapse/Expand | field.collapseExpand | Panel kollaps/expand |
| Content Change | field.contentChange | Innehåll ändras |
| Display | form.display | Efter load innan visning |
| Drag | field.drag | Drag start |
| Drop | field.drop | Släpp över droppable |
| Event | window.event | Internt klient-event (anropbar från workflow/JS) |
| Gain Focus | field.focus | Fokus in på fält |
| Hover | field.hover | Hover på fält/data/label |
| Interval | window.interval | Periodiskt när fönster är öppet |
| Level Double Click | table.levelDouble | Drill-down i tree |
| Lose Focus | field.blur | Fokus lämnar fält |
| Menu Choice | field.menuChoice | Val i menyfält |
| Modify | form.modify | Innan ändring skickas |
| Return | field.return | Enter/Shift-Enter |
| Row Choice | table.rowChoice | Välj rad |
| Row Collapse | table.rowCollapse | Rad kollapsar |
| Row Double Click | table.rowDouble | Drill-down |
| Row Expansion | table.rowExpand | Rad expanderas |
| Row Unselect | table.rowUnselect | Rad avmarkeras |
| Search | form.search | Innan sökning körs |
| Set Default | form.setDefault | När defaults sätts |
| Submit | form.submit | Innan ny request skickas |
| Table Refresh | table.refresh | När tabell laddas/refresh |
| URL Click | field.urlClick | Länk klickad |
| Un-Display | form.unDisplay | När request lämnar vyn |
| Window Closed | window.closed | När fönster stängs |
| Window Open | window.open | När fönster öppnas |
| Call Component Method | ui.callComponent | Anropa en publicerad metod på en komponentinstans |
|---|---|---|
| Call Process | ui.process | Kör extern process |
| Change Field | ui.changeField | Ändra UI-egenskaper |
| Close Page | ui.closePage | Stäng sida / modal |
| Commit Changes | ui.commit | Spara/commit ändringar |
| Create Folder | ui.fileFolderCreate | Skapa folder i File Browser |
| Delete Folder | ui.fileFolderDelete | Ta bort folder i File Browser |
| Fire Event | ui.fireEvent | Sänd internt event (window.event) |
| Goto | ui.goto | Hoppa i exekvering |
| Map Actions | ui.mapActions | Styr kartkomponent (pins, zoom, center) |
| Message | ui.message | Visa meddelande/stoppa |
| Open Page | ui.openPage | Öppna annat formulär |
| Post Submit | ui.postSubmit | Styr beteende efter submit (rensa/ladda) |
| Put Fields | ui.put | Skapa/uppdatera entries |
| Refresh Table | ui.refreshTable | Ladda om tabell-data |
| Set | ui.set | Sätt fältvärden |
| Validate Fields | ui.validateFields | Validera obligatoriska fält |
| If | condition.if | Villkorad gren med true/false |
|---|---|---|
| Label | flow.label | Namngiven hoppunkt i flödet |
Server flow runs where the record is saved, whatever wrote it: a form, the integration API, or another flow. Rules that must always hold belong here, not in the client.
Conditions are written against three namespaces: TR. is the value submitted in this transaction, DB. is the value currently stored, and an unprefixed field is what the flow is working with right now. The difference between the first two is what makes “did the status change” expressible at all.
| Create | record.created | Triggers when a new record is created |
|---|---|---|
| Delete | record.delete | Triggers when a record is deleted by a user |
| Get | record.get | Triggers when a record is fetched from server |
| Process | process | Triggered when called as a subroutine from ui.process |
| Schedule | schedule.cron | Run on a schedule (calendar or interval) |
| Update | record.updated | Triggers when a record is updated |
| CALL | flow.call | Invoke subflow and return |
|---|---|---|
| CALL N8N | integration.n8n | Invoke n8n workflow and read response |
| Create Folder | record.fileFolderCreate | Skapa folder för postens filyta |
| Delete Folder | record.fileFolderDelete | Ta bort folder för postens filyta |
communication.email | Skicka e-post med eventuella bifogade filer från appens filmetadata | |
| Exit | flow.exit | Terminate workflow (with/without commit) |
| Goto | flow.goto | Hoppa i exekvering |
| LOG | system.log | Write to audit/debug log |
| MESSAGE | ui.message | Send message to client (info, warning, error) |
| PUT | record.put | Create or update record in database |
| Render document | document.render | Rendera ett formulär till PDF med Typst |
| SET | record.set | Set field values (static, function, lookup, REST) |
| Track Status Change | record.trackStatus | Spårar statusändring till {app}_statustransitions |
| If | condition.if | Conditional branching with true/false paths |
|---|---|---|
| Label | flow.label | Namngiven hoppunkt i flödet |
A SET action in UI flow takes its value from one of six sources. The same six wherever in the form the value is going to land.
current | Values from the form that is open right now. |
|---|---|
datasource | A search against a record definition, with filter, sorting, paging and a pick modal when more than one row matches. |
sql | A SQL query, with the same handling of zero or several matches. |
rest | A REST call to an external service. |
n8n | An n8n flow that runs, and whose response is read back into the fields. |
server-function | One of your own server functions — see the section below. |
Server flow has a CALL N8N action of its own that starts an n8n flow and reads the response. n8n can run as part of the installation, both under Docker and in Kubernetes.
A public REST API for reading and writing records from outside. Keys expire, can be bound to a single application, carry a policy for what they may touch, and have their own rate limit.
Cure is an MCP server. An AI agent can read the catalogues, build applications in an isolated draft, render a preview to an image and activate the result — all against metadata, never against source code.
Server flow calls other flows with CALL and returns. UI flow starts a server flow as a process and waits for the answer.
When a rule cannot be expressed as a flow, you write a server function: a Python class that declares its input and output as schemas. The engine builds the input from the flow's context, runs the function, and maps the output back through the same SET pipeline as everything else. The function receives the tenant, the application, the record's new and previous values, and tenant-isolated database access.
Plugins are read from a directory on disk and can be scoped to one application, to one datasource, or left as free functions. They load at startup and can be switched off entirely with a setting — an installation that does not want to run custom code runs none.
<CURE_SET_FUNCTIONS_ROOT>/
<application>/
datasource/<datasource>/functions/my_function.py
custom/functions/standalone_function.pyServer flow renders a form to PDF with Typst, table rows included, with a ceiling on how many rows each table may contribute.
Every record has a file area with folders. Both UI flow and server flow can create and delete folders, and the e-mail action can attach the files from there.
many-to-one, one-to-one and many-to-many become real foreign keys or a join table in Postgres when the application is published, with configurable delete behaviour.
Status tracking writes every transition to a table of its own, which the status flow component reads. Approval decisions are stored. Timed escalation does not exist yet.
An application is draft, active or maintenance. The runtime tables are created when it leaves draft. Versions are kept as frozen snapshots.
Server flow starts on a calendar or an interval, without anyone having to keep a window open.
Cure runs as shared SaaS, as a dedicated customer environment, in your own Kubernetes or OpenShift, or under Docker — the same product in every case. Read about the deployment options →
The same capabilities exist as a machine-readable contract, meant to be pasted into tools like claude.ai/design.
Go to the design contract →