Events and processes

Define business events that generate notifications and manage processes that determine which template sends notifications to whom for each event.

The Events and processes screen is where you specify which notification goes to whom for each business event. An Event is the name of a business event in the system that can generate a notification (e.g., order creation). A Process is the rule that specifies which message type, template, and recipients receive a notification when that event occurs. For an event to generate notifications, it must have at least one active process linked to it. Changes made in processes immediately affect real customer notifications.

Accessing the screen

Navigate via the menu: Notifications & Logs › Events and processes. If you do not see it in the menu, your account does not have permission for this screen.

Screen sections

  • Title: Events and processes with a brief description below.
  • Filter card: First name field and (in Processes view) detailed filters you select; below are the Events / Processes view selector, Clear, Detailed filters (Processes only), and Filter buttons.
  • List card: Per page selection, record counter (filter result), action buttons depending on view, sort selector and direction button, refresh icon, Columns menu, table, and pagination.

Views: Events and Processes

Switch between Events and Processes views using the selector below the filter card. When you change the selection, a View changed warning appears in the table; press Filter to load records for the new view. The columns, filters, and actions differ between the two views.

Filtering and searching

Filters and sort selections are applied when you press the Filter button (or Enter while in a field). Clear empties filters and refreshes the list immediately.

In the Events view:

Field Purpose Tip
First name Finds the event by name. Searches for exact name (Type the exact name).

In the Processes view:

Field Purpose Tip
First name Finds the process by name. Always visible. Type the exact name.
Live Yes: active processes; No: frozen processes. Visible by default.
Message type Processes with a specific message type. Added via Detailed filters menu.
Event Processes linked to a specific event. Use to see which notifications an event triggers.
Notification list Processes linked to a specific notification list.
Consent required Processes marked with consent required (Yes) or not (No).
Output type Processes that produce a specific type of attachment (e.g., .pdf, .xlsx).

Sorting

Select the field from the Sort by list in the list card, choose direction with the adjacent button, then press Filter. The default sort is by creation date from newest to oldest.

  • Events: Created or First name.
  • Processes: Created, Message type, Live, or First name.

List

Events view:

Column Meaning
First name Event name; description below. Cannot be hidden.
Created Event creation time. Hidden by default. Often not present in event records and shows as —; sorting by Created still works.
Identity Event number. Hidden by default.

Processes view:

Column Meaning
First name Process name (link; opens process page on click) and description below. Cannot be hidden.
Event Event that triggers the process.
Message type SMS, Email, Call, or Push.
Status Live (green) or No (gray: frozen).
Consent required Yes / No. Hidden by default.
Output type Type of attached file (e.g., .pdf); — if none. Hidden by default.

Page size can be 25, 50, or 100. Clicking a row in Processes view or selecting Open detail from the three-dot menu opens the process page. Clicking a row in Events view opens the event edit window; if you lack permission to edit events, rows are not clickable and no three-dot menu appears.

Actions

Adding an event

When you need to configure notifications for a new business event, first define the event.

  1. In the Events view, press Add event on the list card.
  2. Enter the event name in the First name field. The name must exactly match the name used in the sending system (e.g., OrderCreated).
  3. Optionally enter a Description.
  4. Press Save. The button is disabled if First name is empty.
  5. Read the confirmation warning "Events trigger processes; the name must exactly match the name used by the sending services." and confirm with Save.

If successful, a Saved notification appears, the window closes, and the list refreshes. The name can be up to 200 characters, description up to 1000 characters; exceeding limits causes rejection after confirmation and a Something went wrong notification.

Editing an event

  1. In the Events view, click the event row or select Edit event from the three-dot menu.
  2. Change First name or Description and press Save.
  3. Read the live usage warning again and confirm with Save.

Changing the name of an event in use may affect triggering of linked processes; the name must remain exactly as in the sending system.

The Copy option in the three-dot menu copies the event identity to the clipboard.

Adding a process

  1. In the Processes view, press Add process. The Add process button in the Events view switches to Processes view and opens the same form; filters are cleared on this switch.
  2. Fill out the form (fields below).
  3. Press Save. Error messages appear below missing or invalid fields: Required field for First name, Event, Message type, and Template; email format warnings for email fields.
  4. Read the confirmation warning "Process rules determine REAL customer notifications; changes take effect immediately." and confirm with Save.

If successful, a Saved notification appears and the list refreshes. If rejected, an error notification appears and the form remains open.

Field Required Description / rule
First name Yes Up to 200 characters; exceeding shows Required field warning.
Event Yes Event that triggers the process.
Message type Yes SMS, Email, Call, or Push. Changing resets Template selection.
Template Yes Lists only templates of the selected message type. Disabled until message type is selected with warning "Select message type first for template list."
Notification list No Notification list linked to the process. Empty shows No list.
Output type No Type of file attached to notification: .pdf, .xml, .html, .csv, .json, .jpeg, .png, .doc, .docx, .xls, .xlsx, .zip. Empty shows No attachment.
Description No Up to 1000 characters. No warning if exceeded but Save will not proceed; shorten description.
Live — Checked means process is active. Checked by default for new processes.
Consent required — Links process to consent requirement. Unchecked by default for new processes.
To No Fixed recipient email addresses.
CC No Addresses added as CC.
BCC No Addresses added as BCC.

Separate multiple email addresses with ; (e.g., a@x.com;b@y.com). Each address must be valid; otherwise, the error "Invalid email address; separate multiple addresses with ;" appears. Each field can hold up to 2000 characters; exceeding this also triggers the same email warning.

Shortcut buttons

In Processes view, the Events button takes you directly to the Events view (filters cleared, no need to press Filter); the Templates button leads to the Templates screen. These two buttons are visible even to users without edit permissions. If the event or template you need is missing when configuring a process, create them first.

If you do not see the Add event, Add process, Edit process buttons or the Edit event / Copy menu on event rows, your account lacks permission to make changes on this screen. In that case, you can only view events and processes. There is no delete operation on the screen; to stop a process, uncheck Live.

Statuses

Status (on screen text) Meaning Next step
Live Process is active; notifications are sent when the event occurs. —
No (list) / Frozen (process page) Process is stopped; no notifications sent even if event occurs. To reactivate, edit the process and check Live.

Process page

The process page header shows the process name, description below, and message type. Top right shows Live or Frozen badge and (if authorized) Edit process button. Back to processes returns to the previous browser page; if you came from the list, you return there.

Tab Content
Rule First name, Description, Event, Message type, Template (click opens template page), Notification list, Output type, Consent required, and Identity.
Recipients To, CC, and BCC addresses; empty fields show —.

Editing a process

  1. On the process page, press Edit process. The form opens with saved values.
  2. Make changes and press Save.
  3. Read the confirmation warning "Process rules determine REAL customer notifications; changes take effect immediately." and the question "Update process?" then confirm with Save.

If successful, a Saved notification appears, the form closes, and the page refreshes. Changes take effect immediately. If rejected, a Something went wrong notification appears and the form remains open.

The Notification list cannot be changed during editing. As the tooltip states, create a new process for a different list.

Changing Message type clears the Template selection and allows saving without a template. Before saving, refill the Template field; otherwise, the process will have no template.

Common issues

  • I created an event but no notification is sent. An event alone does not send notifications. Ensure there is at least one Live process linked to the event and that the event name exactly matches the sending system's name.
  • Template list is empty. Select Message type first; the template list shows only templates of that type. If the template you want is missing, create one in the Templates screen for that message type.
  • Changing message type cleared my template selection. Templates depend on message type; reselect the template after changing the type.
  • Search with name filter returns no results. The name filter searches for exact matches; enter the full name.
  • I changed the view and the list is empty. If you see the View changed warning, press Filter.
  • Clicking a row in Events view does nothing. If you lack event edit permission, rows are view-only.
  • Pressing Save on the process form does nothing. Check for warnings below fields; if none, the Description may exceed 1000 characters.

Related screens