Note: If you are upgrading from a version of Engine before 23, please see breaking changes in Engine 23 . Everything in that article will apply as well.
Things Changed or Removed in Engine 24
Removed: Non-API integrations with Engine
This means using a custom in-process integration class loaded by the LogicIntegrationClassName setting or calling public methods on Engine's internal libraries (e.g., using ScormEngineManager to import courses)
Removed: The ability to disable StoreRuntimeDataAsLob
All registration details in the future will be stored as a LOB in the database, which will make running queries for reporting directly against Engine's tables impractical
InspectToken API Endpoint Change
In order to keep the token being inspected out of web server access logs, the InspectToken API has been changed from GET /appManagement/token to POST /appManagement/token/inspect. Consumers of this API will have to modify the call, or use an updated client library.
Stricter validation of characters allowed in tenant names
Since tenant names can be used in paths and urls in Engine, there are some inherent restrictions as to what characters can be allowed. To make that more explicit and to prevent errors at runtime, Engine will now return an error when creating a new tenant if the name includes characters that are not allowed.
There is now a setting that controls what is considered valid: TenantNameValidationRegex. The default for this is the following regular expression: ^[-_a-zA-Z0-9]+$ . This allows only alphanumeric characters and the hyphen or underscore in the names.
.NET 8
Engine will now support .NET 8 instead of .NET framework
Jakarta EE (Tomcat 10 and above)
Support for Java EE (used in Tomcat 9 and below) has been dropped in favor of Jakarta EE (Tomcat 10 and above)
Updated System Requirements
Engine now has the following updates to its system requirements for self-hosted customers:
- MySQL 8 or above
- MS SQL Server 2019 or above
- PostgreSQL 12
- Oracle 19c