Event Action Mapping

Notifications

Notifications provide visual feedback to the user about whether an action succeeded or failed. You configure success notifications and failure notifications separately - each can use a different notification type, or none at all. If you do not configure a failure notification, failed actions fail silently without any feedback to the user.

None

No notification is shown. This is the default for both success and failure.

System Alert

Displays a browser alert dialog with a status message. The message includes the HTTP status code and the server’s response message if available:

✅ Operation successful (200)

❌ Operation failed (422: Unable to commit transaction)

Inline Text Message

Displays the status message on the page, directly after the element that triggered the action. The “Display duration (ms)” field controls how long the message stays before it disappears automatically. The default is 5000 milliseconds, and a value of -1 keeps the message visible until the next action clears it.

The “Message text” field replaces the wording of the message while the icon is kept. The text can contain the placeholders {status} and {message}, which are filled from the response when the message is shown, for example Saved ({status}). Template expressions like ${me.name} are evaluated when the page renders. Leave the field empty to use the default text. The “CSS class” field sets a class on the message element. Setting a class removes the built-in styling completely, including the positioning, so the class has to place the message itself.

For validation errors, the specific error messages are included:

❌ Operation failed (422: Unable to commit transaction, validation failed)
test must not be empty

Additionally, the input element for each invalid property receives a red border and a data-error attribute containing the error type. On success, these error indicators are cleared automatically.

Custom dialog element(s) defined by CSS ID(s)

Shows an element selected by a CSS selector by removing its hidden class. The element is hidden again after 5 seconds. You need to define the hidden class in your CSS, for example with display: none.

You can specify multiple selectors separated by commas - each selector is processed separately. Note that for each selector, only the first matching element is shown. If you use a class selector like .my-dialog and multiple elements have this class, only the first one will be displayed.

This option does not have access to the result data - it simply shows and hides the element. Result placeholders like {result.id} are not available in the selector.

Custom dialog element(s) defined by linked element(s)

Same as above, but instead of entering a CSS selector, you drag and drop an element from the page tree onto the drop target that appears when this option is selected.

Raise a Custom Event

Dispatches a custom DOM event that you can handle with JavaScript. You specify the event name in an input field. See the section “Custom Events” under Custom JavaScript Integration for details.

Notifications and Result Data

The built-in notification types have no access to the properties of the action result. The inline text message can include the HTTP status and the server’s response message via the {status} and {message} placeholders, but not result properties like the name of a newly created object. The system alert and the custom dialog types display fixed content. If you need to show result data in a notification, use “Raise a custom event” and handle the display logic in JavaScript.

In contrast, follow-up actions support result placeholders like {result.id}. See the section “Accessing Result Properties” for details.

Event Action Mapping

Notifications

Notifications that can be executed after an action was executed.

Markdown Rendering Hint: EventNotification(Custom dialog) not rendered because no formatter registered for format markdown, mode overview and EventNotification(Custom dialog)
Markdown Rendering Hint: EventNotification(Fire event) not rendered because no formatter registered for format markdown, mode overview and EventNotification(Fire event)
Markdown Rendering Hint: EventNotification(Inline text message) not rendered because no formatter registered for format markdown, mode overview and EventNotification(Inline text message)