Release Updates February 2025

• If Learners have a Credly Badge for deleted Content, the Credly Widget will never load, and the Admin will see the Processing Error in the Activity Tab.
• Scorm Standalone content can be launched from the Catalog Widget regardless of the Access Dates.
• Tags that are not assigned to at least 1 piece of content do not show up in the search screen for bulk tag assignment.

Tags Reporting Update

A reporting fix has been released which partially addresses some of the limitations that were previously communicated, regarding tag reporting.

Assigning Content Tags - after assigning a content tag(s) to any piece of content, users will now be able to see those tag(s) correctly reflected in reporting. Any edits to those tags (e.g. changing the label in the Tag Manager UI) will also be reflected accordingly in reporting.

While this is significant progress in tag reporting, other limitations still remain and additional improvements to current tag reporting functionality are forthcoming.

• Content Tags in NRT BI Connector - While we have addressed the limitation above in platform reporting, additional work remains to reflect the same updates in the coursetags table in Redshift, affecting NRT BI Connector. This means that there will be a discrepancy between the data in platform reporting and Redshift, in the short-term. More info will be shared shortly on how content tags in Redshift will be addressed.
• Removing Content Tags or Deleting Tags via Tag Manager - These actions are tied to our ongoing Deletion Governance Project, which addresses how deleted or updated data is handled across systems. Improvements will be implemented once the coursetags and tags tables include the new Status Group column and this updated data is available in Reporting Hub.

• Bulk Purchase: Upon selecting Remove/Restore on the Checkout Page, the # of seats is not restored and user is charged wrong price for 1 seat.
• When clicking the "New Session" button from the Release tab on an ILT, a duplicate meeting is created and synced to the Reporting Database.
• Using the Bulk Client & License (Panorama) Assignment API endpoint does not set the users.updated_at timestamp correctly.

New Ecommerce Engine: Bulk Purchasing Release

This release brings the New Ecommerce Engine bulk purchasing functionality to parity with legacy ecommerce. No changes to bulk purchase functionality should be expected. Note: Bulk purchase is not currently compatible with Multicurrency.

New GraphQL API Meetings Endpoints

We’ve created three new GraphQL endpoints to make it easier to manage meetings via API.

• The Create Course Meetings endpoint allows you to create new meetings for an existing course.
• The Update Meeting endpoint allows you to update details of an existing meeting.
• The Destroy Meeting endpoint allows you to delete an existing meeting.

See our API documentation for more details.

Sunsetting the Social Share Cards Page Type

As part of our ongoing efforts to focus on features that bring the most value to our customers, we have discontinued support for the Social Share Cards page type as of today's release.

What this means for you:

• Existing pages will remain functional in your courses, so there’s no immediate impact.
• However, we recommend removing Social Share Cards from your courses since we will no longer maintain or upgrade this functionality.

Alternative solutions:

We offer several other ways to enable social sharing for your users, including:

• Social share buttons at the end of each course.
• Sharing Certificates on LinkedIn to showcase achievements.

This change allows us to dedicate resources to developing impactful features that better meet your needs.

• Ensure star buttons on the course review page communicate state information (checked or unchecked) to screen readers so that learners using screen readers are able to navigate the page.
• On the sign-in page, ensure that any error messages are associated with their corresponding field so that screenreader users can understand and handle any errors (like an invalid password).

• When using the GraphQL API “CreateInPersonEvent” mutation (for recurring and non-recurring ILTS), although the ILTs with meetings are created, the course group is null
• Course title still attached to Asset Library item after being deleted from course outline if the Asset Library Item was added to the SCORM/xAPI types of pages