Content Controller V4.2.535

What's New in 4.2

Multi-Course Upload

We've been working on new ways to make managing your learning content faster and more efficient. Today, we're rolling out a completely redesigned upload experience in Content Controller.

A More Powerful Way to Upload

Our new upload view is your essential first step for adding and organizing content. Before your files even begin uploading, you can now perform key organizational tasks in one place:

• Stage Multiple Courses: Queue up multiple courses for a single batch upload.
• Apply Edits Instantly: Add crucial tags and create custom IDs for better content organization.

Control and Visibility

Once you begin the upload, you can monitor everything in the new Upload History tab. This provides a clear audit trail of all activity, allowing you to see which courses have been successful and which may have encountered an issue. For any failed uploads, a simple Retry button is now available, saving you the hassle of starting the process from scratch.

Engine 23 Support

Content Controller's backend has been re-architected to leverage Engine 23. This integration provides a direct enhancement to xAPI statement processing performance, scalability and storage.

PLEASE NOTE: Important Changes with Engine 23

Version 4.2 of Content Controller introduces a significant architectural upgrade, integrating Engine 23 as the new backend. This upgrade provides foundational improvements but includes critical breaking changes that require administrator action.

[CRITICAL] Data Migration and Downtime Requirement

• Downtime Required: The upgrade to v4.2 requires a data migration process. Administrators must schedule a service outage to perform the upgrade.
• Reversion Warning: The data migration is a one-way process. Downgrading from v4.2 after the migration is complete is an unsupported action and will likely result in data loss. For self-hosted customers we strongly advise reviewing the upgrade documentation and creating a full database backup prior to initiating the update. 

[BREAKING CHANGE] Deprecation of PlayerFinishCausesImmediateCommit Parameter

• Description: The PlayerFinishCausesImmediateCommit configuration, previously available via the API, has been deprecated and removed in Engine 23.
• Endpoint: POST /course/{courseId}/advanced
• Behavior Change: Calls to this endpoint that include the PlayerFinishCausesImmediateCommit parameter in the request body will now return a 500 Internal Server Error instead of a successful 204 No Content response.
• Required Action: All API integrations utilizing this endpoint and parameter must be updated to remove it. We recommend auditing your code for its usage prior to the v4.2 upgrade.

Recommended Upgrade Actions:

If you are interested in upgrading to 4.2 we recommend you reach out to your support representative first, so we can give an estimate of down time and coordinate the upgrade with your team. Here are the basic steps that will have to be taken to finish the upgrade.

1. Schedule a maintenance window for the upgrade.
2. Perform a complete backup of your environment.
3. Notify development teams to audit and update API integrations.
4. Proceed with the upgrade.
5. Contact support@rusticisoftware.com if you have any questions.