29th Mar 2024 - v87 - Brevo Transactional Mail Roll-out Part2
Migrated Walk Change Notifications from Mailchimp to Brevo
Walk notifications now 100% driven from automation, using a new Brevo Template called fully-automated-text-body.
The template has no manually input template content except the following parameters which fully populate the email content at run-time:
System Merge Fields (params.systemMergeFields):
params.systemMergeFields.APP_URL
params.systemMergeFields.APP_SHORTNAME
params.systemMergeFields.APP_LONGNAME
params.systemMergeFields.PW_RESET_LINK
Member Merge Fields (params.memberMergeFields):
params.memberMergeFields.FNAME
params.memberMergeFields.LNAME
params.memberMergeFields.MEMBER_NUM
params.memberMergeFields.EMAIL
params.memberMergeFields.USERNAME
params.memberMergeFields.MEMBER_EXP
Message Merge Fields (params.messageMergeFields):
params.messageMergeFields.subject
params.messageMergeFields.BODY_CONTENT
params.messageMergeFields.SIGNOFF_NAMES
Email Notification Config is setup in an identical way to other Member Admin driven configurations.
A new "Built-in Process Mappings" tab on mail-settings now allows each built-in process (currently forgotten-password and walk change notifications) to be associated with a Notification Configuration.
If a Notification Configurations is associated with a built-in process, it will not be available in the list of email types in Member Admin Send emails dialog. This is because a built-in process needs to supply customised content to the email request which won't be available unless it's called by the built-in process.