Notifications
A notification is an automated email sent to a resource, a resource manager, or a learning manager when a specific learning event occurs. For example, you can use notifications to confirm a participant's registration, to send session information to a participant, or to notify a resource manager that a registration approval is required.
A notification includes these components:
Recipient category
The recipient category indicates the type of recipient to receive the notification. For example, participant, resource manager, learning manager, or both participant and resource manager.
Recipient categories are used to sort correspondence records created by notifications.
Notification template
The notification template consists of a header and a notification text, which is an email template where variables are used in place of actual names and are resolved in context.
For example, a notification with {ResourceEmail} on the To line regarding a registration being approved for {DevelopmentActivityDescription}, {SessionDescription} with information such as {FirstClassDate}, {LastClassDate}, {Location}, and {SessionSite} can be sent instantaneously to any resource approved for registration for any activity and session as soon as the resource's registration is confirmed. The recipient will receive a notification specific to his or her registration.
A notification template requires a language (in ISO code). Currently only one language is supported.
Notification rule
A notification rule is associated with a template and one or more attachments. It determines when the notification should be sent (registration, session participation completion, changes to session). You can have more than one rule for each of these types.
For example, for Registration Confirmed, you can have one notification rule attached with a template addressed to the participant and another notification rule attached to a template addressed to the participant's manager.
You could also have more than one notification rule that uses a template,
provided the text of the notification template works for all the notification rules. For
example, you could have a simple notification template addressed to a resource manager with
this text: "{ResourceFullName} has completed {SessionName}, {SessionDescription}
with a participation status of {ParticipationStatus}. "
You could then associate two notification rules to the participation template: one requiring the notification to be sent when the participation status is Participation Completed, and the other requiring the notification to be sent when the participation status is Participation Incomplete.
Learning and Development provides these types of notifications:
-
Automatic notifications are created automatically by the application.
-
Scheduled notifications require manual intervention from the learning manager. The learning manager can either submit the notification to run with immediate effect, or schedule the notification to run on scheduled dates and times.
The tasks to submit or schedule scheduled notifications are located under .
Attachment
A document can be attached to a notification rule. Documents must be uploaded to Learning and Development before they can be attached to a notification rule. For example, to attach directions and hotels for out-of-town activities.
A learning manager can also create an RTF file with variable merge fields related to session information. When the notification rule to which the document is attached is triggered, the recipient will receive an attachment with all the merge fields resolved.