Release Notes - March 28, 2016

Follow

Defect Corrections

The following issues have been resolved:

  • The [Title] token in the news listing module was displaying the token instead of the value.    ENC-22715
  • Tokens in category instructions were not working properly when using a pre-populated link.    ENC-23232
  • Admins who scheduled an email to send immediately, but did not release it immediately received an error when trying to release the email.    ENC-23423
  • Admins were receiving an intermittent server error when trying to view an email in Email History.    ENC-23272
  • Daily Birthday email send was delayed by 4 hours.    ENC-22989
  • Two new Tracking Actions have been created for events:  Events Guest Registered - User  registered guests for an event and Events Guest Removed - User removed guests from an event.    ENC-21016
  • Admins were unable to adjust the main registrant from activities when they had guests.    ENC-23358  Now admins are able to:
    *Adjust commerce that doesn't drive registration in both event categories and in activities
    *Adjust non-commerce registrations and commerce registrations (at both event and activity levels) when there's only a primary registrant and no guests
    *Adjust non-commerce registrations and commerce registrations (at both event and activity levels) when there's a primary registrant and guests
    *If guests are still registered for the event, the event Adjust button will be disabled for primary registrant until those guests are adjusted off
    *If guests are still registered for an activity, the activity Adjust button will NOT be disabled for primary registrant
  • Admins were seeing the wrong message when resetting their password.    ENC-23115
  • Admins were receiving duplicate notifications for scheduled exports.    ENC-23438
  • Error messages in Email Marketing have been improved to provide clients with specific actions they can take to clear an issue blocking an email from being scheduled.
    *If an email exceeds the 1MB maximum email size, admins will be alerted during the Send Preview step that The email message size (*MB) is above the 1 MB limit.  (Community content can exceed the 1MB email size limit.)
    032816_release1.jpg
    *If the "View this email in browser" link can't resolve when the recipient clicks the link to view the iModules hosted page, this error message is displayed: Your email cannot be viewed in browser at this time.

    *When the administrator clicks the Send Preview button and there is a missing or malformed URL appears anywhere in the email, then the administrator will see this error message: At least one of the hyperlinks in your message has a missing or incomplete URL.

    *If all the required fields in the Email Details step are not completed, on the Send Preview step admins will see the following error messages when attempting to send a preview email.  NOTE:  These error messages will NOT be displayed for emails that contain Community Content
    -Email Category is not specified
    -Email Footer is not specified
    -From Email is missing
    -From Name is missing
    -Reply to Email is missing
    -Subject is missing
    -If nothing has been completed in the Email Details step (All required fields are blank) the Email Details step has not been completed error will be displayed.

    *If an admin attempts to move a recurring email back into drafts after it has been released, and then attempts to send that email again within 18 hours, they will get an error stating Re-release of this email is blocked because this email has already been sent today.   NOTE:  If the Email has community content it will bypass this alert and can be sent again within that 18 hour window.

    *If the First Name, Last Name, Mailer Class, Email Address, or Member ID fields are missing a system token, when the administrator clicks the Send Preview button, the admin will see the following error message: The message cannot be sent because of a misconfigured system token field: ##field_identifier##.  If the issue is not resolved, the message will be displayed again on the Release Email step and will not allow the admin to Save & Continue to release the email.  To resolve the issue, an admin will need to go to the form, locate the offending field, edit the advanced options and make the token unique or add back the missing token. NOTE:  The token validation will always check First Name, Last Name, Mailer Class, Email Address, or Member ID PLUS any tokens in the body of the email.
    032816_release2.jpg

    *If the email contains a duplicate token, then when the administrator clicks the Send Preview button, the admin will see the following error message: The message cannot be sent because of a misconfigured/duplicate system token field. Token name is: ##token_name## Field names are: ##field_identifiers##.  If the issue is not resolved, the message will be displayed again on the Release Email step and will not allow the admin to Save & Continue to release the email.  To resolve the issue, an admin will need to go to the form, locate the offending field, edit the advanced options and make the token unique or add back the missing token.  NOTE:  The token validation will always check First Name, Last Name, Mailer Class, Email Address, or Member ID PLUS any tokens in the body of the email.
    032816_release3.png
Have more questions? Submit a request