Technical Alert: Email Submitter Rollback
Due to a recently-found issue with the email code, we need to rollback a previously released change.
We have identified an issue caused by the resolution of development ticket PD-5248, which was released in May to fix behavior with test emails using conditional content and query-based recipient lists with conditional content. This is a back-end change which will not require any new package install, and will be updated on Tuesday, July 11.
The following behaviors (tracked in development ticket CL-1948) will be fixed:
- Conditional content sections display the default version when multiple child records exist for a contact, and the broadcast is using a report-based recipient list.
This issue causes the default section(s) to be sent, even when a student meets specific conditional criteria. For example, if a student has an application with the status of ‘Admit’ and also has additional application records, the conditions based on the status of ‘Admit’ will not evaluate, and the default version of the content will display.
The following behavior (previously fixed in PD-5248) will be reintroduced:
- Only contact-based conditional content will display when using a query-based recipient list
- Email Template Conditional Content criteria using objects other than the contact will result in the default version displaying
- Only contact merge fields are supported when using a query-based recipient list
- Only contact-based conditional content and merge fields are supported in Test Emails
Test emails will be impacted in addition to live broadcasts.
If you are currently sending emails with template conditions or merge fields based on objects other than the Contact AND using a query-based recipient list, the template will revert to showing the default version, and non-contact merge fields will not populate.
Our team is working to address this and expects that non-Contact criteria and merge fields used with query-based recipient lists will once again be allowed in the future, though we do not currently have a timeline for the resolution of this request. As soon as this is once again available, we will share an update.
We apologize for any inconvenience that this change causes for your institution.