Overview
SDL Trados Business Manager allows to send notifications to specified users when some event occurs (for example, a customer creates a quote request or accepts a quote, a vendor registers on a portal or delivers an assignment, adds an invoice, makes changes in own profile, etc.).
There is a particular set of events defined (which expands with time), which will be described in this document. For each of such notifications, a separate message template is defined in the Reference data > Message templates table. TBM is supplied with some default texts for such notifications, which you can freely edit, turn off or delete.
To completely disable particular type of notification described below, you can simply disable or delete particular message template. When TBM can't find enable message template for some event type, corresponding notifications won't be sent.
Setting-up notifications
Users could receive notifications via 2 channels: by e-mail or in-app. If meaning of e-mail channel is clear, then in-app channel means that notification will be displayed to a user after logging on into the application (via desktop application, online application, customer or vendor portal). If user is already logged on, notification will be displayed immediately to that user (in a form of toast message, and number of unread notifications will increase near the notifications icon):
To control how users receive notifications, go to Other/tools > Users, and select necessary user to open its editing form. Then, switch to the Notifications tab:
Receive notifications checkbox. It has effect only for internal users (users who are NOT vendors or customers). If this checkbox is unchecked, this user will never receive any notifications. The exclusion is when this user is responsible person for some quote/project/job, and customer triggers some event which requires notifying of responsible person (for example, customer accepts a quote).
Vendors and customers will always receive notification regardless of this setting.
Notification method allows to choose a channel how to send notifications to a particular user. To make E-mail method working, two prerequisites must be implemented:
- E-mail filed must be filled for a user
- Under Reference data > Email accounts table, a default e-mail account must be configured and tested
Only get notifications from the following users table allows to limit automated notifications to be send to a current user to a set of specified "source" users who generate a notification. For example, if some manager must receive quote requests only from customer A, then you have to add all users linked with that customer to this table.
List of users who get notifications is specified by Send notifications checkbox in the User editing form. For each user you can also specify a list of vendors, whose actions will generate notifications to a particular user.
After setting up list of users who receive notifications, create a user with Vendor or Customer role to allow them to log in into your portal. When one of supported actions will be performed by such users, each user eligible for receiving notifications will see a toast notification and new unread notification under the "bell' icon.
Default notifications
The following table describes all events which could occur in TBM, corresponding message template used for that event, and default recipients.
Event name | Default message template type | Default recipients | Notes |
Automation rule failed to apply | Automated notification - automation rule failed to apply to an assignment | Responsible person or all managers, if responsible person is empty. | See Automation rules topic to get additional information about automation rules |
Automation rule is ready to be applied | Automated notification - automation rule is ready to be applied | --//-- | If automation rule behavior is set to not automatically assign next vendor in a sequence |
Automation rule successfully applied | Automated notification - automation rule successfully applied | --//-- | |
Customer accepted a quote request | Automated notification - customer accepted a quote | Responsible person or all managers, if responsible person is empty. | |
Customer created a new job | Automated notification - customer created a new job | --//-- | When customer creates a new job directly from the dashboard, skipping quote request phase |
Customer created a new project | Automated notification - customer created a new project | --//-- | |
Customer created a quote request | Automated notification - customer created a quote request | --//-- | |
Customer declined a quote request | Automated notification - customer declined a quote | --//-- | Variable for displaying declining reason provided by a customer: {QuoteLastMessageFromCustomer}. |
Customer profile changes | Automated notification - customer edited own profile | --//-- | |
Customer uploaded additional files | Automated notification - client uploaded additional files | --//-- | |
Quote is ready | Automated notification - quote ready | To customer contact (if e-mail is provided); if contact is empty, to a customer user who initially created a quote request; if initial user is empty, to all customer's users. | |
Project is ready/delivered | Project delivery | To customer contact (if e-mail is provided); if contact is empty, to a customer user who initially created a quote request; if initial user is empty, to all customer's users. | Disabled by default, and will be sent only if Web-app URL is specified in the application settings |
Job is ready/delivered | Job delivery | To customer contact (if e-mail is provided); if contact is empty, to a customer user who initially created a quote request; if initial user is empty, to all customer's users. | Disabled by default, and will be sent only if Web-app URL is specified in the application settings |
Message added to a job | Automated notification - message added to a job | To customer contact person user (if send to customer), or to responsible person or all managers if responsible person is empty (if sent by customer) | Variable for displaying message contents: {AdditionalText}. |
Message added to a project | Automated notification - message added to a project | --//-- | |
Message added to a quote | Automated notification - message added to a quote | --//-- | |
Vendor registered | Automated notification - new vendor registered | To all managers | |
Vendor registration confirmation | Automated notification - vendor registration confirmation | To a registered vendor | This is the only message which contains initial users's password ({RecipientPassword} variable). |
Vendor profile changes | Automated notification - vendor edited own profile | To all managers | |
Vendor profile changes request | Automated notification - vendor requests to edit own profile | To all managers | Used when direct changes in a profile are restricted by security system. Variable that holds explanation of desired changes provided by a user: {AdditionalText}. |
Vendor accepted an assignment | Automated notification - vendor accepted an assignment | Responsible person or all managers, if responsible person is empty. | |
Vendor declined an assignment | Automated notification - vendor declined an assignment | --//-- | Variable to display declining reason: {AssignmentVendorPickNotes}. |
Vendor sent counter-offer for an assignment | Automated notification - vendor counter-offer for an assignment | --//-- | Variable to display counter-offer: {AssignmentVendorPickNotes}. |
Vendor delivered an assignment | Automated notification - vendor delivered an assignment | --//-- | Variable to display delivery notes: {AssignmentNotesFromVendor}. |
Vendor created an invoice | Automated notification - vendor created an invoice | To all managers | |
Vendor edited an invoice | Automated notification - vendor edited an invoice | To all managers | |
Vendor submitted test piece | Automated notification - vendor submitted a test piece | To all managers | |
Test piece marked as finished | Automated notification - test piece results to vendor | To a vendor | |
Vendor assigned to work | Purchase order | To a vendor | If assignment has PO attached, this file will be automatically attached to a created message. |