Managing notification templates
You can use notification templates to help send email messages when an event occurs. Events can be related to requests, steps, system failure, and user accounts. Notifications are sent automatically on the occurrence of a system failure or user account event. Notifications for requests and steps are sent to the specified mailing list only when email notifications have been configured via the Change Notification Options link available when you edit a request. The request- and step-related notifications are sent to the request and step participants, respectively. The participants include the request owner and requestor (for requests) and the person to whom the step is assigned (for steps). The Exception raised notification is sent to the mailing list specified in the smtp_settings.rb file located at <BRPM_HOME>/server/webapps/brpm/WEB-INF/config. You can specify your mailing list by replacing the DEFAULT_SUPPORT_EMAIL_ADDRESS property with a comma-separated list of email IDs in the smtp_settings.rb file.
The BMC Release Process Management product provides a set of default notification templates that you can modify to suit your needs and then use directly. You can also customize your own notification templates by creating, editing, and deleting notification templates.
You create the notification templates with the Liquid template language. You can add information in the email body of the notification template by using the Liquid markup framework, made up of outputs and tags. Outputs are enclosed by two sets of curly braces: {{output in two curly braces}}. Tags are enclosed by single curly braces and a percentage sign: {% tags with single curly braces and percentage sign %}. Outputs usually contain references of tokens, and tags usually use the {% if true %} and {% endif %} notations. Tokens are similar to variables used for automation that are dynamically set at run time and are added to the input file. For more information about the Liquid template language, see http://wiki.shopify.com/Liquid.
Default notification templates
The following table describes the default notification templates that are available:
Default notification templates
| Template | When the notification is sent |
|---|---|
| Events related to system failure | |
| Exception raised | This notification template is disabled |
| Events related to user accounts | |
| Login | User requests his login to the system |
| Password Changed | Users changes own password by using the profile or an administrator changes the password for a user |
| Password Reset | User clicks the Forgot password? link during logon to request new logon details |
| User Admin Created | User logs on to the product via Light Directory Access Protocol (LDAP) authentication or Central Authentication Service (CAS) |
| User Created | Administrator creates a user account; the notification contains logon details |
| Events related to requests | |
| Request Cancelled | Request is canceled |
| Request Completed | Request is completed successfully |
| Request Message | During request execution, to the distribution list with the same message that you update when you cancel a request or manually move the step under the request into the problem state |
| Request On Hold | Request status changed to the On Hold state |
| Request In Problem | Request status changed to the Problem state |
| Request Planned | Request status changed to the Planned state |
| Request Resolved | Request status changed to the Resolved state |
| Request Started | Request has started |
| Events related to steps | |
| Step Blocked | Step is blocked |
| Step Completed | Step is successfully completed |
| Step Problem | Step goes into the problem state |
| Step Ready | Request is ready, so the step is in the ready state |
| Step Started | Step has started |
Comments
Log in or register to comment.