Triggers for Submit and Cancel

A guide to configuring triggers for submit and cancel buttons in form pages, based on the schema.

When to Use

Use triggers to define actions that should be performed when a user clicks the submit or cancel button on a form page.

How It Works

• triggers is an array of trigger objects, each specifying conditions and actions.
• Each trigger can include:
  • label (string, optional): Trigger label.
  • labels (object, optional): Translated trigger labels.
  • breakAfter (boolean, optional): If false, continue to next trigger even if this one succeeds.
  • loop (string, optional): Loop expression for repeated actions.
  • if (array, optional): Conditions for running the action (see JSON Query).
  • then (object, required): Actions to perform if the trigger is activated. Supported actions include:
    • crud: CRUD operations (insert, update, relate, delete)
    • files: File actions
    • note: Note actions
    • itemImage: Image actions
    • createResourcePlanning: Resource planning actions
    • redirect: Navigation (back, dashboard, item, uri, itemkey)
    • redirect_uri: URI for navigation
    • closeModal: Close the modal
    • sendEmail: Send email
    • loop: Loop expression for repeated actions (see advanced triggers)

Usage Example

{
  "submit": {
    "label": "Save",
    "triggers": [
      {
        "if": [["field_id", "=", "value"]],
        "then": {
          "crud": { "insert": { /* ... */ } }
        },
        "breakAfter": false
      },
      {
        "then": {
          "closeModal": true
        }
      }
    ]
  }
}

This example shows a submit button with two triggers: one for a conditional insert and redirect, and one for closing the modal. The second trigger runs regardless of the first due to breakAfter: false.