Previously, if you had enabled both Calendar view and one of the list views (Expanded or Condensed), the Events page on the PTS always defaulted to the list view.

Now, a new setting within the Theme Builder allows you to choose the default view:

We've adjusted the display on the calendar view so that you can see the full name of the Event on large screens, with the time clearly marked on its own line. The calendar cells will also expand vertically to fit multiple performances and Events with longer names.

Mobile devices will clearly show the available performance times in the limited available space on the screen:

And clicking on a day brings up all Event Instances for that day (on any screen size), with links to purchase:

The calendar will also now utilize the brand colors you specify in your theme:

We want your new PTS to look great! When you click the "Manage Content" button on a Ticketable Event to add images, you'll now see the recommended image dimensions on the upload page:

As of the last release, you could embed video from YouTube or Vimeo in rich text fields on the new PTS (for example: the Events Content field, the Ticketable Event Detail, and the Donation Landing Copy).

This release allows you to incorporate audio files from Spotify, Bandcamp, Soundcloud and Apple Music in the same way, to better support our clients who are music-first.

Previously, the Buyer Info page in the checkout flow displayed all fields in a single column, which led to lots of scrolling. Now the layout on that specific page gives more space to the fields the patron needs to fill out, so that they can more easily see what's needed from them:

The last PatronManager release included PatronPortal functionality on the new public ticketing site. This release improves that functionality, so that Portal is cleaner, clearer, and easier for your patrons to use.

We've also resolved some issues that were specific to the new public ticketing site.

One of your more frequent requests! Previously, Subscription Orders that hadn’t been fulfilled showed up in the “Awaiting Fulfillment” dropdown view in the PatronTicket Orders tab, even if those Orders couldn’t be fulfilled because they’d already been refunded.

This meant that most clients could never empty that view / complete that task, because the list would include old refunded Orders, often from previous seasons.

Now everything in that list will need attention, making it more useful for keeping on top of subscription fulfillment.

Previously, if a user created a Ticketable Event, Event Instance, or Discount Code and then left the org and had their user deactivated, another user could not clone that record and would receive an error.

Now users can clone these records regardless of the status of the original record's owner.

Prior to this release, a user could change the Contact on a To Be Qualified Ticket Order without actually qualifying the Order. This would leave the Order 'stuck' in an unqualified state; attempting to qualify the Order led to an error message that the Contact had already been qualified.

Now, users must first qualify the Order before they can associate it with a different Contact record.

While the Order is connected to the placeholder To Be Qualified Contact, it is possible to correct Contact information (e.g. misspellings) by editing the Buyer Info fields.

After the Order has been qualified, changes to those fields affect only that Ticket Order.

The CRM Snapshots tab previously included a sub-tab called "Campaigns" with Snapshot options that were specific to PatronMail, our legacy email marketing tool retired in 2017. We have removed that section of CRM Snapshots to avoid confusion with other kinds of Campaigns.

If you need to report on legacy PatronMail data, this is still possible via the standard Reports tab.

Previously, PatronManager Box Office was not compatible with custom Ticket Order "Phone"-type fields. This mainly affected clients who use integrations like Mogli to text their patrons, and therefore wanted to collect mobile phone numbers during checkout. It has been fixed so custom phone fields will work.

To learn more about Mogli and other recommended apps, click here.

Previously, clicking the link to group the Event Summary Report by Allocation resulted in an error in Lightning. Now it works.

In PatronManager Box Office, if you added Events that didn’t have a common delivery method (for example, one Event only allowed Emailed tickets and another only allowed Shipped tickets), you couldn’t complete the Order, but there was no explanation as to why.

Now this scenario gives a clear error message so that the user can solve the problem (by processing separate Orders, or adjusting the selected delivery methods on one or more of the Events).

Previously, any time you switched from Salesforce Classic to Lightning, you would always land on the Lightning home page. Now you can switch into Lightning from anywhere in PatronManager, and land (in Lightning) in the same place you were before you switched.

Previously, the ability to create HTML email templates and letterheads with images, a standard header/footer, organization information, etc. was only possible in Salesforce's Classic interface. Now admins can create enhanced templates and letterheads in Lightning, too. Note that your existing letterheads (ones created in Classic) will be found in a new place in Setup, under the renamed menu option "Classic Letterheads". You can create new letterheads by typing "Enhanced Letterheads" in the App Launcher.

Virtual confetti is a fun way to celebrate your success when a Major Gift or Grant comes in. This feature works with the Sales Path in Lightning, and is triggered when an Opportunity/Donation is set to a certain "Closed Won" Stage.

You can enable this feature by searching for Path Settings in the Quick Find box in Setup. Once there, you can enable Path if it's not already enabled, or edit your existing Paths to control the conditions for when and how often the celebration happens (always, or only sometimes, to keep the element of surprise!).

This valuable reporting feature allows you to get notified (or notify others) when report results meet certain conditions. Previously this was only possible in Salesforce Classic, but now it's possible to set up your conditions in Lightning too.

If you've used Conditional Formatting in Salesforce Classic (where it's known as "Conditional Highlighting"), or even in Excel, you know how great it is to have a visual indicator that certain value breakpoints have been met. Now that this feature is available in Lightning, you can apply up to five formatting rules to a report (in Classic it was only three).

You can also use either a standard color palette to highlight your data, or customize your highlighted cells with colors of your choosing. Conditional formatting rules can still only be used on summary or matrix reports, where they are applied to summaries, like totals or subtotals, or custom summary formulas.

This feature lets you search for specific records and values in the results of your report.  A new search icon will appear on the report's run page, and the results of your search will be highlighted in yellow directly on the report.

Quick filters let you find the information you need in a long related list on a particular record more quickly. Just open the related list and select the funnel icon to add your filters. This is great if you're on the phone with a patron who lost their tickets and needs you to resend them, or wants to do an exchange.