Product Updates
Event Audit Tab Update - The Audit tab on an Event is now a single table of everything that has happened to the Event, in date order: changes to the Event with their before and after values, task history, ad-hoc emails, and emails sent by Communication Triggers. Each row shows when the activity happened, its type, the user responsible and the details, and you can sort the table, filter it by type or user, search the details and page through the results.
- Bookings and Accounts can now name a Billing Contact, so invoices and booking emails go to whoever handles billing. A Booking uses its own Billing Contact if it has one, otherwise the Account's, otherwise the booking Contact, and a new Billing Contact audience makes that person addressable from a trigger and its template.
- Import columns for ID fields now accept the numeric IDs shown in the app, so you no longer have to look up an encoded ID before importing.
- Initials can now be set when creating or updating a User, and fall back to the initials of the first and last name when none are given.
Bug Fixes
- Fixed previews of Communication Templates failing when a macro contained a pipe character, which showed the whole macro as plain text instead of the expected table.
- Fixed previews of unsaved reports showing rows from every company, rather than the company the report will be saved to.
- Fixed three Learning Path issues: auto-registration on optional Event objectives, an unclear message when registering on an Event that has ended, and already-completed Courses not showing as complete.
- Fixed the Learner registration modal showing a nested Learning Path as an option group instead of listing its learning objectives for registration.
- Fixed four unexpected errors: generating Sessions for a Course Template with no schedule, signing in where no password has been set, opening an Account you do not have permission to see, which now shows a Not Found page instead of an error, and a price tooltip on a grid row that had already been removed.
- Fixed three API requests returning an unexpected server error instead of a clear message: an Event statistics date range that is out of order or longer than 13 months, a custom field ordering direction that is not lower case, which is now accepted whatever the case, and two Custom Field labels that collide once punctuation is stripped, which now returns a validation error.