This changelog is based on Keep a Changelog. Mambo adheres to Semantic Versioning.
For more information on how to upgrade your Mambo Platform, please see the Upgrade Guide.
Released on: 2025-02-14
Engine
Changed
- Newly created leaderboards no longer count past points: previously, new leaderboards included points from past activities due to automatic reprocessing, whereas now they only track points awarded after creation. To include past points, the leaderboard can be manually regenerated after creation.
- Upgraded to Servlet 6.x and Tomcat 10: Mambo Engine now supports Servlet 6 and Tomcat 10; earlier Tomcat versions are no longer compatible.
Fixed
- Templates failed to load under certain circumstances: templates with mechanics configured using HTML code could not be loaded. The underlying issue has now been fixed.
- Error when uploading malformed templates: uploading a malformed template ZIP files caused templates to indefinitely remain in the "uploading" state. The underlying issue has now been fixed.
- Error when creating Prizes or Points with very large values: Creating prizes or points with large numerical values caused an exception. The underlying issue has been fixed, and the maximum value of points and prizes has been set to 1,000,000,000.
- Rewards API could returned wrong mission progress: the rewards API could return a wrong mission progress when the request specified a filtering tag or when rewards tracked by the mission had not yet been awarded to the user. The underlying issues have now been fixed.
- Validation error when creating prizes with fractional points: creating a point prize where the number of points had a decimal component caused a validation error. The underlying issue has been fixed and it's now possible to create fractional prize points.
- Levels with 100% could be shown as not awarded: under rare circumstances, it was possible that a level was not awarded to a user despite the user having earned sufficient points. The underlying issue, which was linked to latency in DB replication, has now been resolved.
SDKs
Changed
- SDKs refactored for better usability and developer experience: Java, .NET, and PHP SDKs now use MamboClient as the main access point, support RequestOptions per request, and include detailed exceptions. See API and SDK docs for details and examples. The Java SDK also introduces individual method parameter classes. See API and SDK docs for details and examples.
- Java SDK improvements: the number of dependencies of the Java SDK was greatly reduced. In particular, the SDK no longer depends javax. dependency, minimized other dependencies, and introduced individual method parameter classes for better integration.
Documentation
Changed
- API Specification fully compatible with OpenAPI Spec v3: The format of Mambo API specification available from the API explorer has been upgraded to the latest version of the OpenAPI specification.
- API Explorer shows code samples for the pinned version: selecting a pinned version in the API and SDK manual now updates the API specification and SDK code samples accordingly.
0 Comments