The Actions lens
Defining an action: what it does to a record, where it is run from, and its published versions.
Actions lens
This screen is two lenses of the Model tool: Actions and Runtimes, in its bar beside Entities, Views and Workflows. Without a lens the address opens on Runtimes at the platform and on Actions in a tenant, as before.
An action is something the product does to a record, defined once and run from a record's Run an action… or from a workflow effect, through the same path: its published version, its applicability, the permission it names, its confirmation, then its handler — every run and refusal traced and in the tenant's trail.
| What it does | What you declare |
|---|---|
| Set field values | The fields and the values it sets. It writes through the record's own write path, so the entity's required fields, data types and rules are checked first. |
| Create a related record | The relation it links the new record by, and values for the new record. |
| Start the workflow | Optionally which workflow (otherwise the entity's). |
| Move the record in its workflow | The transition it takes (with its permission, guards, required fields and effects). |
| Notify | The notice. There is no in-app notification storage yet: the notice is kept in the tenant's audit trail only, and nobody is sent a message. |
- Under Define an action, choose what it does and the records it runs on, give a key and a name, the permission a person needs to run it (a platform permission key; a record write needs
record.write) and whether it asks for confirmation. It starts as draft version 1; Publish version N makes it runnable, New draft version starts the next one. - Below, Parameter and Result entries and Applicability conditions can be added to a tenant action's draft version, as before.
Keep in mind An Action whose side-effect class is destructive cannot have the approval policy none; the form stops this before saving. A tenant's action with the same key as a platform action wins in that tenant.