This documentation supports the 23.3 version of BMC Helix Digital Workplace Basic and BMC Helix Digital Workplace Advanced. Icons distinguish capabilities available only for the Advanced and External license levels. For more information, see License types and features.To view an earlier version, select the version from the Product version menu.

Leveraging the notification engine on BMC Helix Innovation Suite for greater flexibility


Administrators can choose the notification engine on BMC Helix Innovation Suite or the notification engine in BMC Helix Digital Workplace to send email notifications to end users. You can use the two notification engines in the following ways: 

  • Use the notification engine on BMC Helix Innovation Suite to send only email notifications and the notification engine in BMC Helix Digital Workplace to send push or in-app notifications. 
  • Use the notification engine in BMC Helix Digital Workplace to send email, push, or in-app notifications. To learn how to configure the traditional notification engine, see Configuring-the-email-server

Important

  • You can use only one notification engine at a time to send email notifications. 
  • The notification engine on BMC Helix Innovation Suite can be used to send email notifications with the supported email templates, which are related to only Catalog-native requests. To learn more, see Out-of-the-box-notification-events-templates-and-processes.


Benefits of the notification engine on BMC Helix Innovation Suite

The notification engine on BMC Helix Innovation Suite provides the following benefits: 

  • Flexibility to modify or completely redesign the notification templates to match the organization's branding, colors, or locale. 
  • Better governance over operational tasks such as auditing notification failures.
  • Ability to create company-specific templates.
  • Ability to manually trigger failed notifications. 


Supported scenarios


Unsupported scenarios

  • The notification engine on BMC Helix Innovation Suite can be used to send email notifications related to only Catalog-native requests. Notifications for service requests from BMC Service Request Management or other external catlaog sources are unsupported.
  • Existing custom templates cannot be imported. 
  • Notifications to external users are unsupported
  • The following events are not supported:

    • Service health status change
    • Appointments (created and canceled)
    • Social updates


How email notifications are sent by using the notification engine on BMC Helix Innovation Suite

The following image represents how notifications are sent by using the notification engine on BMC Helix Innovation Suite:

How email notifications are sent.png


Before you begin


Process to configure the notification engine on BMC Helix Innovation Suite

The following images shows the process of configuring and enabling the notification engine on BMC Helix Innovation Suite:

Process  to configure notification engine on Helix Platform.png


FAQ


How do I get the notification engine on BMC Helix Innovation Suite?

The notification engine is automatically deployed with version 23.3.04 and later with the out-of-the-box notification events, templates, and processes. 

You can proceed with he configuration steps by following the instructions in Task-1-Setting-up-the-outgoing-mailbox.

Can I create company-specific templates?

Yes. You can create company-specific templates in a multi-tenant environment. You can use variables to rebrand the templates for each company. For more information, see Task-4-Optional-Modifying-the-notification-process.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*