Triggers
On this page
A trigger is a workflow item that runs its program automatically: on a schedule, or when an object is saved or deleted. Every trigger carries a condition and a program; no trigger has a form or a template.
Trigger kinds
Triggers come in three groups, each with its own product label:
| Label | Choice in the trigger window | When it runs |
|---|---|---|
| Trigger on Condition | A schedule | On the Automation Server's schedule, over every object that matches the condition. This is the only kind that runs outside the saving process. |
| Trigger on Condition | After the object has been saved | In the saving process, after the object has been written. |
| Trigger on Created/Modified | Object is created, Object is modified, or Object is created or modified | When an object is created, changed, or either. |
| Trigger on Deleted | - | When an object is deleted. |
Both kinds of Trigger on Condition are created in one window; its first choice, a schedule or After the object has been saved, decides which kind you get.
A scheduled Trigger on Condition never acts on an inactive object: before its own condition is applied, objects in a Closed, Retired, or Inactive status are excluded.
A trigger set to After the object has been saved has no schedule, no history, and no repeat policy, so it fires on every qualifying save.
Escalations
Nothing in the product treats an escalating trigger differently from any other trigger. An escalation is a scheduled Trigger on Condition, and only its name marks it as an escalation: if you rename it, nothing else sets it apart from other triggers. To add an escalation, you add a trigger; the product offers no other way.
A new 2026.1 database created with the Default Workflow contains escalation triggers of this kind; see Default Workflow Configuration. Each has a time-based condition over an active object and a notification in its program. The thresholds they compare against are workflow parameters in the Escalation parameter category, which has a subcategory per module. An upgraded database need not have these triggers, and an administrator may have changed them.
In the Settings App
Where triggers are
In the Settings App, a class sits under its business area and has a Workflow node. A class's Workflow node holds a Triggers folder with three nodes: On Condition, On Created/Modified, and On Deleted. Stock Rooms is the exception: its Workflow node opens a toolbar-actions editor, not this tree. The Global Workflow object has only Functions and E-mail Notifications, so it has no triggers.
- The toolbar offers New, Edit, Delete, Copy Item, and Order....
- New opens an empty trigger window, which is not modal. Edit, a double-click, or Enter opens the selected trigger. Copy Item copies the trigger and opens the copy. OK saves a changed window and closes it.
- The right-click menu adds New, Enable, Disable, and Export Selected Settingsā¦.
You can also create triggers by process, under Workflow and Business Logic > Advanced > Processes. On a process's node, New offers Trigger on Condition, Trigger on Create/Modify, and Trigger on Delete, then the class. The window opens modally, and saving adds the trigger to the process. Remove takes the trigger out of the process without deleting it.
Create a Trigger on Condition
- Select Triggers > On Condition, and click New.
- On the General tab, enter a Name and a Description, and set Enabled.
-
Under Check Condition:, choose one of these:
- Every N minute(s). A new trigger starts at every 5 minutes.
- Use advanced schedule, and click Change... to set the schedule. Saving with this option and no schedule is refused and opens the schedule editor.
- After the object has been saved, to run the trigger in the saving process instead of on a schedule.
While a schedule is chosen and the Automation Server is not running, the tab shows "Warning. For this trigger to be executed, the Automation Server must be set up and running." 4. For a scheduled trigger, under Repeat actuation:, choose whether an object the trigger has already acted on is eligible again: Each time the condition is checked (selected on a new trigger), No more than once in a number of hours, days, or months, which skips an object the trigger acted on within that period, or Do not repeat, which never acts on the same object again. 5. For a scheduled trigger, under Stop actuation:, choose Never (selected on a new trigger) or After N actuations, which skips an object once the trigger has acted on it N times. With After N actuations, you can also select Resume if the object was modified, which makes a modified object eligible again. On a new trigger, this box is selected but unavailable until you choose After N actuations. 6. On the Condition tab, set the condition; see Conditions and Expressions. A scheduled trigger requires a condition; with After the object has been saved, the condition is optional. 7. On the Programming tab, set the program. 8. Click OK.
The window also has a Processes tab and a Sessions tab, and no Form tab. The Sessions tab holds the trigger's own job log: it is filled for a saved scheduled trigger, unavailable on a new trigger, and not shown for a saved trigger set to After the object has been saved.
When a scheduled trigger has a history of objects it acted on (see How triggers run), the General tab shows "You can reset the actuation counter and resume this trigger for all N previously processed objects.", where N is the number of those objects, and a Resume button. With no history, both are hidden. Resume asks "Are you sure you want to delete trigger history?". On Yes, it deletes the trigger's history, and every object becomes eligible again, including objects stopped by an After N actuations limit. Saving the window with Each time the condition is checked and Never after you changed its settings deletes the history the same way, without asking. Choosing After the object has been saved makes the line and the Resume button unavailable; they are hidden when you open a saved trigger set to After the object has been saved.
Switching a scheduled trigger to After the object has been saved removes its Automation Server job and deletes its actuation history, so what the trigger had already acted on is lost even if you switch it back.
Create a Trigger on Created/Modified or a Trigger on Deleted
- Select Triggers > On Created/Modified or On Deleted, and click New. The window identifies its kind as Trigger on Create/Modify or Trigger on Delete.
- Enter a Name and a Description, and set Enabled.
- For a Created/Modified trigger, under Execute when:, choose Object is created, Object is modified, or Object is created or modified. Object is created is preselected.
- For a Created/Modified trigger, optionally select Run this trigger only from the object Full Form. Such a trigger does not run on a save that is not made from the object's full form.
- Optionally, set a condition on the Condition tab. Set the program on the Programming tab.
- Click OK.
The Trigger on Delete window has neither Execute when: nor the full-form option. Both windows have the Condition, Programming, and Processes tabs, and no Form tab.
Set the run order
Order... on the Triggers folder or on one of its three nodes opens the Execution Order window, which lists the class's triggers in the order they run. Move rows with Move Up and Move Down (or Ctrl+Up and Ctrl+Down), or by dragging; you can select several rows. Click OK to save the order, or Cancel. Trigger lists cannot be grouped.
A new trigger goes last in the order. Scheduled triggers and triggers set to After the object has been saved are ordered together, and the three Created/Modified kinds are ordered together.
The execution order is the run order only within one load of a class's triggers. A class's trigger list gains the Object is created or the Object is modified triggers only when a save first needs them, so Object is created or modified triggers that are already loaded can run ahead of them, whatever their place in the order.
How triggers run
- Which triggers are considered depends on what happened to the object: creating an object considers its Object is created and Object is created or modified triggers, editing an object considers its Object is modified and Object is created or modified triggers, and deleting an object considers its Trigger on Deleted triggers.
- A Created/Modified trigger runs inside the save that provoked it, before anything is written.
- Triggers set to After the object has been saved are loaded, for the objects the save created or edited, after the other triggers of the save have finished, and they run after the save is committed. If one of them fails, the save's committed writes stay, and the failing step is logged as failed.
- For the first object of a run that a save, an Action, or a Service Action starts, gaining an attachment or a detailed activity is enough to run its triggers, even when nothing else changed.
- A scheduled Trigger on Condition first selects all matching objects in one query, then checks each object again before running its program for it. A scheduled trigger whose condition is empty does nothing.
- After a successful run, a scheduled trigger records the object it acted on, and the Repeat actuation and Stop actuation settings use that history to exclude objects. No history is kept for a trigger set to Each time the condition is checked and Never.
- A disabled Trigger on Created/Modified, Trigger on Deleted, or trigger set to After the object has been saved is not loaded, so it does not run.
- A scheduled trigger's enabled state is carried by its Automation Server job, and the two are kept the same. Deleting the job also deletes the trigger.
When triggers modify objects, those objects are processed again in the next pass of the same save. A save allows 10 passes, counted across everything the save touches, not per trigger. If a trigger's condition still matches on the eleventh pass, the save fails before anything is written, the trigger's run is logged as failed, and you see "Error while executing the workflow function. Workflow Item # n." followed by "The maximum number (10) of recursive calls for triggers is exceeded. Please simplify your workflow definition."
Related topics
- Conditions and Expressions - build the condition a trigger checks.