Creating notifications
A notification system is available to send emails when particular events occur. Templates and tokens are available to simplify the creation of detailed notifications. The following event types can trigger a notification:
- Signoffs, which occur when a package is about to be deployed into an environment. If the environment has signoff information configured, a signoff notification goes to the configured recipient list.
- Processing, which can occur anytime. Several of the activity libraries include a notification task. With this task, you can configure the system to send a notification to any recipient list at any time during the running of any process.
You can populate notification templates with tokens that are replaced with event-specific information.
To create notification templates
- Click the Define tab.
- From the left menu, select Notifications.
- After the list of existing templates, click New Template.
- In Label, enter an appropriate label to identify the notification template set.
- From the Language menu, select the language for the first template in the template set.
- In Subject, provide a subject line for the email template.
- In Body, enter the email body text.
Click Create Template to create the notification template set with the initial language version.
To add another language email to a notification set
- Click the Define tab.
- From the left menu, select Notifications.
Click Edit for the template set, if you want to receive the email with the previously defined content in a different language.
In the Change Language section at the bottom of the page, select the language to add.
- Select an existing language to initially populate the new language email.
- Click Create.
The system presents the edit page for the new language email, prepopulated with the selected language.
To use a token in a notification template
To use a token in the subject or body of a template, use the following format: ${<TOKEN NAME>}. For example, 'Deployment of ${VL_PACKAGE} ${VL_INSTANCE} suspended' would render the name of the package and the name of the package instance upon sending (provided that both tokens are valid at the time). To see the full list of the existing BMC Release Lifecycle Management tokens, see Tokens.