Administrate General Release Notes
Available for Essentials, Essentials Plus, and Enterprise.
Coming Tomorrow
We're introducing hour-level precision for Triggers, giving you more control over when communications are sent.
What's coming?
You'll be able to:
- Set Triggers using hours, days, or a combination (e.,g 1 day and 2 hours before)
- View precise timing details like "2 hours before the event" or "Jun 8th at 8:00 am" in the Event Communications tab.
- Clone Existing Triggers to save setup time
- Continue using all existing day-based Triggers without disruption
Why does this matter?
With more control on timing, you can send communications exactly when users need them most, increasing the chances they'll see, act and engage.
- For Webinars or virtual training, reminders sent 1-2 hours before help reduce no-shows by reaching attendees right when they're likely to check their calendars or inboxes
- For feedback surveys, sending them shortly after an Event ends captures responses while the experience is still fresh.
- For global events, hour-specific scheduling ensures messages are sent out at a relevant time in each user's timezone, not a 3 am by mistake.
- For expiring subscriptions or passes, timely alerts just before expiration can drive last-minute renewals.
For more information, check our documentation on Triggers.
Defects Resolved
- We added the Learner Status to the Student Email Event Communication table.
- When transferring a Learner to a different Event via the Registration page, the Transferred From and Transferred By fields are now recorded.
- You can now view Triggered Emails created by Manual Triggers with all merge fields fully populated.
- You can now report on Credential Username when creating a Report under the Contact Credential entity.
- You can now include and filter on LMS Notes when configuring a Report under the Event entity.
Administrate Essentials Plus
Available for Essentials Plus Edition only.
What's New?
Developer Experience
-
We have introduced a new mutation createdExternalIntegrationLogs in the externalLog namespace, so that multiple external integration logs can be created at once with a single request.