Send notifications to internal recipients through the email channel using email templates.

You can now send notifications to internal recipients through the email channel using email templates. Your administrator has the ability to define different email templates based on the object and the notification type.

With this feature email templates are utilized for internal notifications within a system. This approach offers several advantages, including standardized formatting, branding consistency, and the ability to dynamically insert variable data using tokens. Here's a breakdown of the key points you've mentioned:

  1. Email Templates:

    • Allows predefined structures for emails.
    • Enables consistent branding and styling across notifications.

  2. Subject Line Customization:

    • Administrators can predefine the email subject line.
    • This ensures that the subject is clear and follows a standardized format.

  3. Branding and Images:

    • The inclusion of branding elements (such as logos) maintains a consistent corporate identity.
    • Images can be used to enhance the visual appeal of the email.

  4. Variable Substitution:

    • The use of tokens allows dynamic content insertion.
    • For example, inserting user names, dates, or other relevant information based on the context of the notification.

  5. Flexibility in Message Definition:

    • The notification message defined in the Notification Preference Manager serves as the body of the email.
    • This approach provides flexibility in crafting detailed and context-specific notification messages.

By incorporating these features, the system offers a robust framework for tailoring internal notifications to specific needs. Users can leverage the email templates to create notifications that are not only informative but also visually consistent with the organization's branding. The use of variable substitution adds a layer of personalization to the messages, making them more relevant to the recipients.

Overall, this approach provides a versatile solution for managing internal notifications through email, giving companies the tools to communicate effectively and maintain a professional appearance in their correspondence.

Steps to Enable

To enable this feature, there are several steps that need to be taken:

Defining an Email Template:  

Defining the Notification Trigger:

  • To define a notification triggers, you will need to write groovy script in Application Composer
  • Detailed instructions on defining a groovy notification trigger are available here: https://docs.oracle.com/en/cloud/saas/fusion-service/fairs/define-notification-triggers.html#s20066792
  • We also provide a number of example notification groovy triggers for the most commonly used notifications here: https://docs.oracle.com/en/cloud/saas/fusion-service/fairs/service-request-assigned.html#s20071614
  • To specify a specific email template that you want to use when email is selected as a delivery channel for a notification, you will need to specify the email template name as part of the notification trigger groovy script.
  • Here is the groovy code that you will need to include as part of your notification trigger groovy script to specify the email template:

    • def map = }}{{new {{HashMap(); }}map.put("EmailSubject","<subject>"); {}map.put("EmailTemplateName","<templatename>"); {}adf.util.sendNotification(adf, map);

Define the Notification Recipients and Delivery Channel:

Tips And Considerations

There are a few rules and conditions that you should be aware of when setting up this feature.

The Notification Author will define the groovy script so that the subject and template name are passed as part of the trigger definition for the notification delivery channel of email.

  • Please note that you are able to define multiple delivery channels for a notification such as Browser, Bell, Mobile and Email. The addition of the email template definition in the groovy trigger only applies to notifications sent through the email channel and will not have any impact on notifications sent through other channels.

Rules:

  • If no Subject is passed as part of the groovy trigger definition and no subject is defined in the email template, the system will use the default email subject.
  • The default subject is derived by the Outbound message service before sending, it can implement the same logic to take first 70 characters from the message text
  • If the Subject is defined in the email template the system will use the subject in the email template.
  • If the Subject is passed as a specific value in the groovy notification trigger, the system will use that as the subject (and ignore the subject defined in the email template if one has been defined)

Access Requirements

Implementing this feature will require the appropriate privileges to access Application Composer