Skip to content
Symbiant System Black Logo
  • Home
  • Knowledge Base
  • Symbiant Website
  • Symbiant Changelog
  • Submit a Ticket
  • My Support Tickets
  • Home
  • Knowledge Base
  • Symbiant Website
  • Symbiant Changelog
  • Submit a Ticket
  • My Support Tickets
Popular Keywords importuserdivisionsamlimport risk

Admin Basics

  • Sharing Dashboard Layouts with Other Users
  • Setup Mode/Admin Menu
  • Creating/Adding Users
  • Transferring Ownership from One User to Another (Assuming)
  • Making a User Active/Inactive
  • Delete a User
  • Changing a Record Reference
  • Managing Drop-Downs, Multi-Selects, and Multi-Levels
  • Resetting a User’s Password
  • Checking System Attachment Storage
  • Database History & Restoring Historical Records
  • Restoring a Deleted Record (Archived)
  • Audit Trails
  • Email Log Viewer
  • System Menu Layout & Options

System Translations

  • Adding a Translation Pack
  • Editing a Translation Pack
  • Mass Editing a Newly Created Translation Pack
  • Assigning a Translation Pack to a User
  • Exporting a Translation Pack
  • Importing a Translation Pack
  • Adding a Default Translation Pack
  • Creating a Locale Specific View (Translated View)
  • Editing a Locale Specific View (Translated View)

Importing Data

  • Preparing Data for Import (Default)
  • Imports with Hierarchical Data
  • Importing Data (Generic)
  • Preparing Data for Import (Risks)
  • Importing Data (Risk Register Specific)
  • Preparing Data for Import (Users)
  • Importing Users
  • Importing Divisions
  • Importing Errors & Issues

Automated Emails (Task Based)

  • How Automated Emails Work (Triggers and Schedules)
  • Activating and Deactivating an Automated Email (Trigger) and (Scheduler)
  • Creating an Automated Email – When a Record is Created (Trigger)
  • Creating an Automated Email – When a Record is Updated (Trigger)
  • Creating an Automated Email – When a Record is Deleted (Trigger)
  • How to Receive Module Specific Emails as System Admin (Trigger) and (Scheduler)
  • Editing an Automated Email – Sending to a Different Module Role (E.g. Risk Manager) (Trigger)
  • Editing an Automated Email – Sending to a Record User (Trigger)

Automated Email Reminders (Time Based)

  • How Automated Emails Work (Triggers and Schedules)
  • Activating and Deactivating an Automated Email (Trigger) and (Scheduler)
  • Creating an Automated Email Reminder – When a Record is Due (Scheduler)
  • Creating an Automated Email Reminder – When a Record is Overdue (Scheduler)
  • Setting up Recurring Schedules
  • How to Receive Module Specific Emails as System Admin (Trigger) and (Scheduler)
  • Editing an Automated Email Reminder – Sending to a Different Module Role (E.g. Risk Manager) (Scheduler)
  • Editing an Automated Email Reminder – Sending to a Record User (Scheduler)

System Views

  • Editing a Dashboard Chart
  • Sharing Dashboard Layouts with Other Users
  • System Views (Quick Explainer)
  • Creating Your Own Custom Views
  • View Editor Tool Overview
  • Editing a View
  • How to Hide/Unhide Fields
  • Loading/Saving a Particular User’s View
  • What are Widgets?
  • Adding, Removing and Editing a Grid Column
  • Adding Help Tips & Placeholder text
  • Modifying a User Field to Limit or Allow Specific Users
  • Modifying a Currency Field to Set Default

Exporting Data

  • Exporting Dashboard Data
  • Exporting Divisions
  • Exporting Users
  • Generating the System User Details Report

System Errors & Issues

  • Resolving System Issues
  • System Error Messages
  • Login Issues

Reporting Suite Tutorial

  • Creating a Word Report (Basic Data Output)
  • Creating an Excel Report (Basic Data Output)
  • Creating a PowerPoint Report (Basic Data Output)
  • Creating an Excel Tabular Report (Perfect for CSV)
  • Creating an Excel Audit Report (Audit Log Of Changes)
  • Adding a new column to an Excel Report
  • Removing a column in an Excel Report
  • Creating an Advanced Word Report (Adding Functions)
  • Advanced Report Coding (Using Owners, Divisions & Assignees in a Report)
  • Advanced Report Syntax
  • Advanced Filtering on Reports (Filtering Via Code)
  • Reporting Permissions

Advanced System Functionality

  • Symbiant API

Document Management (System Setup)

  • Setting Up Document Types
  • Setting Up Document Statuses
  • Document Storage Limits and File Sizes
View Categories
  • Home
  • Knowledge Base
  • Admin Information
  • Automated Emails (Task Based)
  • Creating an Automated Email – When a Record is Created (Trigger)

Creating an Automated Email – When a Record is Created (Trigger)

0:00 / 5:19
  • View as Markdown Open this page as plain Markdown (opens in a new tab)
  • Open in ChatGPT Ask questions about this page (opens in a new tab)
  • Open in Claude Ask questions about this page (opens in a new tab)
  • Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)
AI Doc Summarizer Doc Summary
AI Doc Summarizer Thinking Thinking

This article shows you how to build a trigger that sends an email when a new record is created, for example emailing the Risk Admins whenever a new risk is added.

Applies to: System administrators (admin role) · Module: Set up > Triggers

Before you start #

  • Most modules already have shipped triggers named <module>-...-generic (for example register-risks-new-risk-generic). They arrive inactive. Check the list first: activating a shipped trigger is often all you need. See Activating and Deactivating an Automated Email.
  • For how triggers work in general, see How Automated Emails Work (Triggers and Schedules).

Accessing Triggers #

  1. Click the Set up spanner at the bottom left of the screen.

    The Set up spanner at the bottom left

  2. In the Set up menu, under Events, click Triggers.

    Triggers in the Set up menu

  3. Click the + icon at the top right.

    The plus icon

Trigger Details #

  1. In Resource, choose the module the email is about, for example Register-Risks. Type to search the list.

    Choosing the Resource

  2. In Operation, choose Create.

    Choosing the Operation

  3. In Name, enter a name with no spaces, for example register-risks-new-risk-company. A good convention is module, what happens, then your company name.

    Naming the trigger

  4. Leave Active? unticked while you build and test. See Activating and Deactivating an Automated Email.

Trigger Assignment #

Assignments (who can cause this trigger to fire) controls whose actions fire the trigger. It is not the list of people who receive the email.

  1. Tick the users, roles and/or divisions whose changes should fire it. To cover everyone, tick the root division (for example Company): every user sits in it or a division below it.

    Assigning the trigger to the root division

The Function Chain #

The ƒ chain panel on the right holds the steps (interceptors) the trigger runs, from top to bottom. Each interceptor can use the output of the ones above it through its Data source.

  1. To add an interceptor, click the + at the top of the ƒ chain panel and pick it from the list. It is added at the bottom of the chain.

    Adding an interceptor to the function chain

  2. To remove one, click the − at the top right of its card.

Adding the tx-entity Interceptor #

The tx-entity interceptor loads the record that was created.

  1. Add a tx-entity interceptor.
  2. Under Load entity associated with transaction, choose After change, because the record didn’t exist before the change.

    tx-entity loading the record after the change

Adding the Manager Interceptor (Optional) #

Use a manager interceptor when the email should go to users with a particular role, such as the module admins. Emails to the record’s owners, creator or assignees don’t need one.

  1. Add a manager interceptor.
  2. Data source: the interceptor above it (here tx-entity).
  3. Attribute: the user field to look through, usually generic/owners.
  4. Role: the role to send to, for example risk_admin. Add one manager interceptor per role.

    The manager interceptor

Critical: Don’t choose the plain admin role. Choose the module role (for example risk_admin) and give that role to any admins who should get the email. See How to Receive Module Specific Emails as System Admin.

Adding the Template Interceptor #

The template is the email itself: who it is from and to, the subject and the body.

  1. Add a template interceptor.
  2. Write the email in Content in this order: From:, To:, optional Cc: and Bcc:, Subject:, a blank line, then the body.

    A template interceptor

  3. For From:, use the no-reply address shown in the shipped templates ([email protected]) rather than a person’s address.
  4. For To: and Cc:, use user names, email addresses, or recipient codes. The table below lists the common codes.
Send toCode
Record owners{{<generic/owners}}{{sm.user/name}}, {{>generic/owners}}
Record creator{{<created/user}}{{sm.user/name}}, {{>created/user}}
Last person to change the record{{<modified/user}}{{sm.user/name}}, {{>modified/user}}
Users with the manager interceptor’s role{{<generic/owners}}{{<manager}}{{sm.user/name}}, {{>manager}}{{>generic/owners}}

The code works as a block: {{<generic/owners}} opens the Owners field, {{sm.user/name}} picks out each user, and {{>generic/owners}} closes the block. When a manager interceptor is used, wrap the whole content in {{<manager}} at the top and {{>manager}} at the bottom, as in the shipped templates.

  1. Add record data to the subject or body with markers such as {{risk/reference}} and {{generic/summary}}. Click template patterns… above the content, then the Text Markers tab, for the marker syntax.

    Text Markers in template patterns

  2. Click validate template to check the template before saving.

Note: Field keys such as risk/reference are the same keys shown in the tx-check Contains? list and in Set up > Translators.

Adding the Email Interceptor #

  1. Add an email interceptor.
  2. In Send Email, choose your template.
  3. In Send as, choose HTML (lets you use <br/> for line breaks and <b>text</b> for bold) or plain text.

    The email interceptor

Adding the Log Interceptor #

  1. Add a log interceptor, set Log to Emails, enter a Log Group (for example Register-Risks) and choose your template in Info line template.

    The log interceptor

Critical: Don’t use spaces in the Log Group name. Use dashes instead.

Sent emails then appear in Set up > Log viewer under that group.

Saving and Testing #

  1. Click Save at the top right.

    The Save button

  2. Tick Active? and save again when you’re ready to test (see Activating and Deactivating an Automated Email).
  3. Create a test record in the module (here, a new risk) with yourself as owner.
  4. Check Set up > Log viewer for the log entry.

    The Log viewer

Critical: An active trigger sends real emails to real users. Test with a test record, and check the recipients before activating.

Related articles #

  • Creating an Automated Email – When a Record is Updated (Trigger)
  • Creating an Automated Email – When a Record is Deleted (Trigger)
  • Editing an Automated Email – Sending to a Record User (Trigger)
  • How Automated Emails Work (Triggers and Schedules)
Add, Triggers
Did this help?

Share This Article :

  • Facebook
  • X
  • LinkedIn
Require Additional Information? Please Contact Support

How can we help?

Updated on 30 October 2026
Activating and Deactivating an Automated Email (Trigger) and (Scheduler)Creating an Automated Email – When a Record is Updated (Trigger)
Table of Contents
  • Before you start
  • Accessing Triggers
  • Trigger Details
  • Trigger Assignment
  • The Function Chain
  • Adding the tx-entity Interceptor
  • Adding the Manager Interceptor (Optional)
  • Adding the Template Interceptor
  • Adding the Email Interceptor
  • Adding the Log Interceptor
  • Saving and Testing
  • Related articles
Symbiant System White Logo

20-22 Wenlock Road

London

N1 7GU

Linkedin
Telephone Numbers
  • UK - 0113 5263 755
  • Support - 0204 5514 735 option 2
  • USA - 347 991 7130
Information
  • Home
  • Knowledge Base
  • Symbiant Website
  • Submit A Ticket
  • Change Requests
  • Support Staff Login

Copyright © 2025 Symbiant All Rights Reserved - Risk, Audit and Compliance Management Software

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
Cookie SettingsAccept All
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
SAVE & ACCEPT
Loading...

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.