Change Log - SAT

Updated 1 hour ago by admin

23rd March 2026

New Feature

Flexible recipient targeting

  • Journeys can now be sent to specific audiences, including Users, Groups, Departments, Locations, and more - KB Article
  • Recipient selection is handled via a dedicated selection modal with resolved names

Batch sending

  • New delivery method to spread sends across a date range instead of sending all at once
  • Supports time windows and optional weekend exclusion
  • Visualised directly on the calendar as ranged items

Content Packs in Journey Builder

  • Content Packs can now be added as a course-based content type
  • Fully supported in calendar and preview flows

Improvements

Delivery processor performance and logging

  • Improved pre-processing before business hours to ensure faster sends
  • Enhanced logging and tracking for delivery visibility and troubleshooting
  • Per-item tracking now includes attempts, timestamps, and errors

Preset template upgrades

  • Templates now support batch sending, new content types, and recipient selection
  • Added an option to adjust weekend scheduling when applying templates

Last sent visibility

  • Content items now show the last sent date during selection
  • Helps avoid over-sending and improves planning

Calendar and UI enhancements

  • Improved calendar scaling and layout for better visibility
  • Clearer handling of past dates and read-only states
  • Updated modals to support new functionality
  • Improved previews for Content Packs and Random Simulations
  • General UI polish and consistency improvements
Infrastructure

Delivery processor reliability improvements

  • Reworked the delivery processor to correctly pre-queue batch sends
  • Prevents batch sends from overflowing beyond their configured end date

On-demand service optimisation

  • Improved on-demand processing to reduce load on the courses database
  • Enhances overall performance and stability during send operations

Random Simulation Collections

  • Added support for randomised simulation selection from collections at send time

23rd March 2026

New Feature

Metadata-based content pack assignment

  • Content packs can now be assigned using metadata attributes, including Group, Location, Department, City, Country, Company, and State.
  • Administrators can select multiple recipients within the chosen metadata category, allowing content packs to be distributed more precisely across organisational structures.

Annual refresh for recurring training

  • Added an Annual Refresh option when assigning content packs.
  • When enabled, the content pack will retrigger once per year for all users who are part of the pack, reassigning the courses contained within it.
  • This supports recurring training requirements such as annual compliance or refresher training.

Immediate assignment during setup

  • Administrators can now choose to send the content pack immediately to all currently selected recipients when configuring the pack.
  • This allows existing users who match the criteria to receive the content pack instantly.

Improvements

Microsoft Teams course visibility

  • Fixed an issue where courses within the Microsoft Teams integration would not appear for some users when signed in with alternate accounts or email aliases.
  • Courses will now display correctly regardless of which associated account or alias the user is signed in with.

Upload Your Own Course interface

  • Updated the edit banner to align with the action button wording, changing “Update course” to “Save” for clearer consistency.
  • Saving changes will now keep administrators on the course edit page, preventing them from being redirected away during editing.

Infrastructure

Content pack system rework

  • Reworked the content pack infrastructure and assignment logic to support metadata-based targeting and future scalability.
  • The underlying data model and assignment processing have been redesigned to allow content packs to dynamically evaluate user metadata rather than relying on tenancy assignment methods.

Existing pack migration workflow

  • Organisations with existing content packs will see a one-time conversion banner prompting them to either convert existing packs to the new system or cancel the migration.
  • This ensures existing configurations can be safely transitioned to the updated infrastructure without disrupting current assignments.

How did we do?