Release Updates June 2025

You asked for more structure around learner timelines, and now it's HERE with the launch of Course Due Dates!

Available in Labs, you can enable the Course Due Dates feature to help ensure timely completion of critical content across a range of use cases, from compliance and onboarding to role-based certifications and product rollouts. By setting clear deadlines, admins can drive learner accountability and keep training aligned with organizational goals.

Due dates can be defined within an auto-assignment rule, to apply due dates at scale when specific user criteria are met. Alternatively, the due date can be set at the content-level when the same timeline applies to all learners.

Here's what you can expect with this release:

• Configure Due Date
  • Add a due date at the auto-assignment rule-level (applies to all content types)
  • Add a due date at the content-level (applies to all content types)
• Learner Due Date UX
  • View due dates for content
  • Get marked incomplete and/or complete content past due
• Learner Access Widget
  • New “Required” tab consolidates all content with a due date in a single place
• Reporting
  • View learners' due dates in content + # completed days late (if applicable)

  Subsequent Labs Releases Will Include:

  • Trigger learner notifications based on the content due date
  • Additional user experience optimizations

  For more details, see this article.

  Note

  Note to BI 2.0 customers: As part of the report updates, an additional duedate column has been added to the usercourses table in Ti’s production database. If your queries are currently constructed in such a way that they depend on the order of columns (uncommon; not a recommended best practice in SQL), we advise you to review and update them after this release to ensure continued accuracy and reliability.

Out of Labs, Into Action: Quiz Enhancement Is Now Standard

The Confirm Quiz Answer feature, introduced last month, is now out of Labs and part of the default quiz experience, no feature flag required! This update adds a confirmation step for learners after selecting an answer, providing a more deliberate and user-friendly quiz flow.

See this article for full details on how the new experience works.

One of our upcoming releases will include an item that may impact your custom assessment reports if you are performing any question-level analysis in NRT BI Connector or custom Looker reports in Reporting Hub.

Limited Scope

The scope of this update is very limited to custom reporting and it will have no affect on:

• Learner experience or the actual behavior / logic of your assessments.
• Reporting for overall assessment scores / grades / passing / completion criteria in any system (BI Connector, Looker).
• Any default Looker dashboards.
• The JavaScript-based question analysis found within the platform's "Analyze Question Responses" tool.

Planned Impact

In cases where an assessment question is left unanswered, question-level reporting will reflect a NULL value for all quiz attempts completed after this update is released. Quiz attempts completed prior to this release will be unchanged.

Reporting Hub: This update will impact the correct field in the Assessment Attempt Responses view. Any custom look and/or dashboard utilizing this field should be calibrated to expect this response. This field is available in the following explores:

• Assessment
• Attempt Responses (Site)
• Assessments (Site)
• Assessments (Client)

Allow Panorama Learners to Sort Catalog by Relevance When "Always display detail page" is Enabled

If you have customized the settings for your catalog widget to set the Default Sort Order to Relevance, today’s release introduces a change that may have a minor effect on the order of catalog items displayed as the catalog first loads.

• Existing behavior: When the catalog is sorted by relevance (and no search term is entered), content is be sorted by start date. Once a search term is entered, content will be sorted by relevance.
• New behavior: When the catalog is sorted by relevance (and no search term is entered), content will be sorted by title. Once a search term is entered, content will be sorted by relevance.

If you’d prefer the catalog to default to sort by start date when the page loads, you can change the catalog settings to set the Default Sort Order to Start Date.

We’ve released an updated version of SCORM Connect, built on a modern, secure driver to support reliable cross-domain course delivery and reporting. This enhancement ensures ongoing compliance with evolving technology standards, while preserving seamless content updates and uninterrupted integration with third-party LMS platforms.

Any SCORM Connect packages that were exported before the release will continue to run on the legacy driver. Any new SCORM Connect packages that are exported after the release will run on the new driver.

No action is required from you in response to this release. You can optionally export new SCORM Connect packages for use in your third-party LMS systems if you’d like to ensure that your SCORM Connect courses are supported by the most up-to-date technology. The process for exporting a SCORM Connect package for use in your third-party LMS will be unchanged by this release.

What are the differences between legacy and new SCORM Connect?

• New SCORM Connect runs on a modern driver that is more robustly supported and more compatible with a wider variety of third-party LMSs.
• The functionality of new SCORM Connect doesn’t otherwise differ from the legacy version, aside from one change to how we report interactions to the third-party LMS:
  • With legacy SCORM Connect, if a learner has multiple attempts on the course, the old attempt is always overwritten with the new.
  • With new SCORM Connect, we’re able to track multiple attempts; each attempt is recorded and returned to the third party LMS.

  For more information, see this article.

If you have customized the settings for your catalog widget to set the Default Sort Order to Relevance, our upcoming release will introduce a change that may have a minor effect on the order of catalog items displayed as the catalog first loads.

• Existing behavior: When the catalog is sorted by relevance (and no search term is entered), content is be sorted by start date. Once a search term is entered, content will be sorted by relevance.
• New behavior: When the catalog is sorted by relevance (and no search term is entered), content will be sorted by title. Once a search term is entered, content will be sorted by relevance.

If you’d prefer the catalog to default to sort by start date when the page loads, you can change the catalog settings to set the Default Sort Order to Start Date.

Stay tuned for more details as we prepare to roll out this enhancement to the learner experience.

• Asset Library functionality not available for custom roles without all 3 sub permissions being granted

• New Panoramas have their default language set to English instead of inheriting the default language of the Company.