Use this link to share with your colleagues:
March 2021 Release Notes: https://help.pm.leapevent.tech/a/1360517
Welcome to the first major release of 2021! In this release you'll find a range of box office updates geared toward modernizing and standardizing the box office interface. This includes updates to:
- Exchanges
- Membership sales
- Subscription sales & fulfillment
As always, we've also got a few Bug fixes.
Ready? Let's dive in!
Recording of the Release Notes Webinar
We recommend setting the video quality to 720p (click on the gear at the lower-right of the embedded video) and watching the video in full-screen mode, if possible.
PatronManager Box Office Updates
Some parts of PatronManager Box Office hadn't yet been updated to the new interface when it was modernized a few years back. With this release, all aspects of the box office now share the same design, making it easier to learn and more intuitive to use.
You'll also find some long-requested improvements to flexibility in subscription fulfillment, which will continue to improve with subscriptions sold following the release.
Ready to learn more? Head over here for a complete overview!
Bug Fixes
With each release, we tidy up bits of unexpected behavior and make incremental improvements to PatronManager. This release fixes a few intermittent bugs:
When transitioning off the legacy Public Ticketing Site to the new PTS, one of the steps involved "extracting venues" so that reserved seat maps would display correctly on the new site.
However, if you cloned an Event Instance from an old one that pre-dated this extraction process, sometimes the new Event Instance was unable to correctly display the venue's seat map unless you extracted the venue again.
Now, cloning an Event Instance will also ensure that the seat map is correctly displayed on the Public Ticketing Site, without requiring any extra steps.
When you import Donations to PatronManager en masse, the system sometimes decided to create (or not create) payment transaction records for the whole batch based on the first record it evaluated in the list. If that Donation met the criteria for a transaction record, all the Donations in that import received one, and vice versa.
Now, the system will evaluate each imported Donation record independently, and create Payment Transactions only for those that meet criteria.
That's it for this release!
Want to be part of the product development process? Stay tuned for upcoming announcements about ways to make your voice heard, and be sure you're logging in to the Client Community to keep up to date on the latest news and opportunities!
