11.17.0 Release
Production Release Date: Tuesday, February 22, 2022
Platforms: Backoffice (B2B), eCommerce (B2C), ACME Sales (POS)
Release Type: Minor
Downtime: None
Test Environments: Sandbox 10, POS-Sandbox 11.17.0
Create Customized Emails with our SendGrid Integration!
Emails | SendGrid Data Integration
We now have a data integration with the email provider, SendGrid. This integration allows you to create your own customized email content for your guests, while still relying on ACME's email triggers and data elements. This new feature will allow venues to:
- Completely customize the design of your emails to match your brand, create custom content and more.
- Override ACME's default email templates with your own SendGrid Templates.
- For emails that have been customized, whenever an action occurs that would normally send the ACME default email, the configured SendGrid template will be used instead.
- When the email trigger occurs in ACME, the same data will be automatically sent to SendGrid. No additional API integration necessary.
- Review the SendGrid Integration Setup documentation and reach out to your Customer Success contact to learn more!
B2B | Email Status in Order Details
We have added some data columns to the Order Details → Email Status tab in order to help answer email deliverability questions, some of which are specifically for those using the new SendGrid Data Integration. For example: Template ID will show the Dynamic Template ID from SendGrid if configured to override ACME’s default, Response Message (SendGrid) which will show the message about the results of the initial send of the email to SendGrid, and more. See the ACME Email Delivery Status guide for more details.
B2B | Membership Coupons in Backoffice
You can now apply coupons to New Memberships sold in Backoffice. The same coupon drop down list that appears for the Renew Membership flow is now also available for the New Membership Sales flow. All coupons configured will be available for the user to search or select, and messaging will update accordingly if the coupon is valid or invalid. If the coupon is valid for the New Membership level + lifecycle, then a discount will be applied in the cart.
POS | Worldpay SDK Update
We have upgraded the Worldpay SDK to the latest version (2.2a) which should resolve some of the reader disconnect issues that have been reported. IMPORTANT NOTE: This SDK upgrade is not backwards compatible with POS versions 11.15.x and older, as it installs new firmware on the card readers. If your venue uses Worldpay Express, we recommend deploying ACME Sales 11.17 on one POS terminal to start before deploying across all devices.
Bug Fixes
Emails | Membership Card Email QR Codes
We fixed an issue where QR codes were not displaying on a mobile device in portrait mode. The QR code now appears on mobile in both portrait and landscape modes.
POS | Multiple Membership Orders
In this release we followed up to a fix in release 11.15.1. This release now includes the scenario when a POS agent is using a custom POS Configin addition to the ACME default POS Config. When purchasing two memberships in the same order at POS, the second membership was not getting created in ACME. To prevent this from happening, agents will not be able to add more than 1 membership to the cart in the same order. In order to sell more than one membership, create multiple orders.
POS | Membership Gift Message
We have fixed an issue with the Gift Message text box at POS displaying with a black background.
B2C | Branded URL
We have fixed an issue for venues using the Branded URL feature, when clicking on the VERIFY MEMBERSHIP button from the JOIN NOW page, it did not show the Branded URL in the email sent to customers who were verifying by email. With this release, the URL will now be branded. If you are interested in activating a branded URL for your ACME online checkout flows, please contact sales@acmeticketing.com for more information.
Apple iOS Certificates
POS | Certificate Updated
We updated the Apple iOS certificates for the Acme Sales POS application to keep it running on iOS devices. We do this to stay in compliance with Apple development requirements.