Automation Runner Job #
The Automation Runner executes defined automation rules on a 15-minute schedule. It is the engine behind the extension’s workflow automation feature.
What DMSI Service Management Adds
The automation rules system and the Automation Runner job are entirely new. Core has no workflow automation.
What Are Automation Rules? #
Automation rules are configured by admins at Services > Automations. Each rule has:
- A trigger — the condition that causes the rule to fire (schedule-based or event-based)
- One or more actions — what happens when the rule fires (create a request, send a notification, update a contract field, etc.)
Job Behavior #
On each run (every 15 minutes), the Automation Runner:
- Queries all enabled automation rules.
- For each rule, evaluates whether the trigger condition is met.
- If the trigger is met and the rule has not already fired in the current evaluation window (deduplication), it executes the configured actions.
- Logs the result (fired / skipped / error) to the automation log.
Trigger Types #
| Trigger Type | Description |
|---|---|
| Schedule-based | Rule fires at a defined time or interval (e.g., every Monday at 9am, first of month) |
| Event-based | Rule fires in response to a system event (e.g., contract created, request overdue) |
Action Types #
| Action Type | Description |
|---|---|
| Create Request | Automatically opens a new service request with specified details |
| Send Notification | Sends an email to a defined recipient |
| Update Field | Updates a field on a contract or request record |
| Add Note | Adds an internal note to a request |
Automation Log #
Results of each automation execution are stored in the automation log table. Admins can view the log at Services > Automations > Log. The log shows:
- Which rule fired
- When it fired
- The action taken
- Whether it succeeded or produced an error
Log entries older than 90 days are automatically pruned.