{"id":"660818cf4aa1bb0019e974c2","title":"2024 03 29","path":"how-to/committee/release-notes/2024-03-29","contentMarkdown":"# 29th Mar 2024 - [v87](https://github.com/nbarrett/ngx-ramblers/compare/5b3fb1d6...7e165e69) - Brevo Transactional Mail Roll-out Part2 \n### Migrated Walk Change Notifications from Mailchimp to Brevo \n\n* Walk notifications now 100% driven from automation, using a new Brevo Template called **fully-automated-text-body**.\n* The template has no manually input template content except the following parameters which fully populate the email content at run-time:\n* **System Merge Fields (`params.systemMergeFields`)**:\n * `params.systemMergeFields.APP_URL`\n * `params.systemMergeFields.APP_SHORTNAME`\n * `params.systemMergeFields.APP_LONGNAME`\n * `params.systemMergeFields.PW_RESET_LINK`\n* **Member Merge Fields (`params.memberMergeFields`)**:\n * `params.memberMergeFields.FNAME`\n * `params.memberMergeFields.LNAME`\n * `params.memberMergeFields.MEMBER_NUM` \n * `params.memberMergeFields.EMAIL`\n * `params.memberMergeFields.USERNAME`\n * `params.memberMergeFields.MEMBER_EXP`\n* **Message Merge Fields (`params.messageMergeFields`)**:\n * `params.messageMergeFields.subject`\n * `params.messageMergeFields.BODY_CONTENT`\n * `params.messageMergeFields.SIGNOFF_NAMES`\n * Email Notification Config is setup in an identical way to other Member Admin driven configurations.\n* 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.\n\n\n\n\n* 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.\n","contentHtml":"29th Mar 2024 - v87 - Brevo Transactional Mail Roll-out Part2
\nMigrated Walk Change Notifications from Mailchimp to Brevo
\n\n- Walk notifications now 100% driven from automation, using a new Brevo Template called fully-automated-text-body.
\n- The template has no manually input template content except the following parameters which fully populate the email content at run-time:
\n- System Merge Fields (
params.systemMergeFields):\nparams.systemMergeFields.APP_URLparams.systemMergeFields.APP_SHORTNAMEparams.systemMergeFields.APP_LONGNAMEparams.systemMergeFields.PW_RESET_LINK
\n \n- Member Merge Fields (
params.memberMergeFields):\nparams.memberMergeFields.FNAMEparams.memberMergeFields.LNAMEparams.memberMergeFields.MEMBER_NUM params.memberMergeFields.EMAILparams.memberMergeFields.USERNAMEparams.memberMergeFields.MEMBER_EXP
\n \n- Message Merge Fields (
params.messageMergeFields):\nparams.messageMergeFields.subjectparams.messageMergeFields.BODY_CONTENTparams.messageMergeFields.SIGNOFF_NAMES
\n \n- Email Notification Config is setup in an identical way to other Member Admin driven configurations.
\n- 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.
\n
\n![\"\"](\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/7812210b-cc7c-4b62-b1a8-0c8e91a8367e.png\")
\n\n- 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.
\n
\n"}