Guides
Triggers
A trigger defines when a workflow starts: on request or on a data change.
What it is for
Section titled “What it is for”The trigger determines what starts a workflow and whether it runs at all. A disabled trigger starts nothing.
Where in the app
Section titled “Where in the app”Triggers have no page of their own. The trigger is part of the Workflow’s rules document (field on), which Polaris writes. The workflow as a whole is enabled and disabled.
Key terms
Section titled “Key terms”| Trigger type | Starts the workflow … |
|---|---|
Manual (manual) |
on request, for example by Polaris |
Database change (CDC) (db.<table>:insert, :update, :change) |
when records are created, updated or both in a table |
CDC stands for „Change Data Capture“, i.e. detecting data changes. Deletes are not possible as a trigger.
How it works
Section titled “How it works”A workflow has exactly one trigger per version. A condition (when) in the document decides whether a run continues, for example only when a status changed to “Done”. A CDC trigger delivers the affected row before and after; the rules can work with that.
New workflows start disabled. Only after the owner or an admin enables it does the trigger start runs.
Permissions: only the workflow’s owner or an admin may enable; the owner or any admin may disable.
Interplay
Section titled “Interplay”- Every triggered run appears under Executions with its trigger source.