Use this link to share with your colleagues:
July 2018 Release Notes: https://help.pm.leapevent.tech/a/944378
What's New in This Release
This release contains a diverse set of exciting PatronManager improvements that we built based on your feedback. They include:
-
Accessibility Improvements for the new PatronManager Box Office
- Design updates to field labels to ensure the new box office is accessible for everyone.
-
Further Improvements for "Other" types of to-be-qualified Contacts
- Contacts originating from a third-party source are labeled as "Other", per a previous release. We have introduced a field set to customize what fields you see during qualification of these Contact Records.
-
Canadian currency display format for Bluefin customers
- Canadian currency will now format correctly for Bluefin customers using the PatronManager Box Office.
-
Bug Fixes:
- Phone numbers will auto format in the new box office, as it did in the previous box office.
- Payment transaction error due to long cardholder names.
- We solved an issue clearing the keyword text field when filtering an event list in the box office.
- $0 fixed price discount codes can now be created.
- You can now edit or clone the "Buy X, Get Y" discount code type.
- Qualification improvements for clients using Emma for their email marketing
Below you'll find more details about these features and enhancements.
Your feedback helps us improve PatronManager for all of our clients. Have ideas or comments for us? We'd love to hear from you!
PatronManager Box Office Accessibility Updates
In order to make the PatronManager Box Office accessible to all users, we recently performed a design accessibility audit. Using the industry standard Web Content Accessibility Guidelines (WCAG) as well as Salesforce's Lightning Design System, we looked at standardizing the way we design labels for input fields. Placeholder text, which was previously shown lightly inside the fields, now has a separate label. You may notice these changes on the Contact Lookup and Buyer Info fields in the new box office experience.
Handling Custom Fields during Qualification when Contact Origin is "Other"
In the previous release, we instituted a new category for unqualified contacts: any to-be-qualified (TBQ) Contact that comes from a source other than PatronTicket, PatronDonate, or PatronSignup, can easily be viewed in the "unqualified contacts list" by using the "Other" filter. For example, if you are currently using Emma as your email marketing software for patrons to sign up for your email list, using an Emma signup form will be in this group because their Signup Source is “Emma”. Other reasons for having an “other” type of TBQ Contact include a class registration form, a volunteer registration form, and an integration or import from an external system.
We’ve introduced a field set which will allows you to customize what fields you see during qualification of these kinds of contacts. We recommend that you add whatever custom Contact fields you have added to those forms to this field set. (Note: only PatronManager and Custom fields will be selectable. Standard Salesforce fields are not available to add to this field set.)
Once added to the field set, these fields will now appear on the screen when you are qualifying contacts so you can see what data is being brought over from your custom form, integration, and import.
Not only did we make this data visible on the Qualification screen, but we also improved the way these fields are handled during the merge that happens when you qualify a record.
The data collected in these fields will be merged into an existing contact, overriding existing values in those fields. If they were blank on the existing contact, then we will populate the fields.
If you are using Emma for your email marketing, this feature replaces a workaround that our Client Administration team has implemented for you when setting up your Emma integration or creating your special form. That workaround will still work, but we will no longer be implementing it going forward.
Canadian Currency Display for Bluefin Customers
If you are a Canadian organization using Bluefin as your payment processor, you will notice an improvement to the display of currency. Canadian currency will now display as "CA$" or just "$" when processing transactions in the PatronManager Box Office.
We previously released updates to Account and Contact titling. You can now manage this information easily in the Patron Signup Settings tab. You can lean more about how to create Account Name and Record Type defaults in the following Help Tab article.
Bug Fixes
In addition to the new features above, we have also made improvements to existing features based upon your feedback. Here is an overview of design updates and bug fixes included in this release:
1. Phone number auto-formatting in PatronManager Box Office
We have updated the way phone number formatting works in the new box office. If a box office user enters a phone number without formatting (ie: 5555555555), it will now auto format to (555) 555-5555. This fix was implemented to maintain feature parity with the previous version of the box office.
2. Payment transaction error due to long cardholder names
We fixed an issue where payment transactions were not completing when the Name on Card character count was longer than 26.
3. Filtering event lists in the PatronManager Box Office
If you were filtering the event list in the PatronManager Box Office with a keyword, and you clicked the "clear" button, the event list updated properly, but the keyword remained in the text field. We have fixed this issue so now when you click "clear" it also clears the keyword text fiield.
4. $0 fixed price discounts are now allowed
In order to set up a discount code for comping items on-the-fly, you can now create a $0 fixed price discount code. You can also create a 100% discount code to accomplish the same goal.
5. Cloning Buy X, Get Y discount codes
We fixed a bug pertaining to discount code cloning, so you can now clone a "Buy X, Get Y" discount code in PatronManager.
6. Qualification improvements for clients using Emma for their email marketing
Several organizations that are using Emma for their email marketing reported an issue when qualifying contacts when they were merging a new Contact with an existing Contact who was synced with Emma. When they chose to merge a new TBQ Contact with an existing Contact and selected the TBQ Contact’s email field as the master during qualification, assuming there has been a change to the patron’s email address, the merge did not stick. The Email field and the Emma Member Id field would revert back to their values on the original existing contact. The system also created a new TBQ Contact with the email address of the TBQ Contact that just got merged. This resulted in a frustrating loop of contact qualification.
After several conversations with the engineers of the Emma integration with Salesforce, we identified a way to modify our qualification code so that this would no longer happen.