Release Notes: 12.5.0
Description | This release contained many internal improvements needed for updating to DotNetCore, improving security, and providing the foundation for moving away from Razor. It also contains all the improvements from 12.4.1 and 12.4.2 |
---|---|
Release Date | January 2025 |
Marketing | N/A |
12.5.0
Category | Description | Internal documentation |
---|---|---|
Other Improvements | ||
Cosmetic / Defect | Improved padding and spacing through LearningBuilder Throughout the system spacing between icons and buttons became smaller or misaligned from recent browser updates. We resolved these issues for an improved user experience. | |
Cosmetic / Defect | Fixed Application Pathway Format Changes in Chrome 130 caused layout issues with our CSS grid. Those issues have been corrected. | |
Configuration Enhancement
| S3 File Upload Improvement In 12.4.0 we added the ability to upload directly into a File Library from the File Library page. For this feature to be offered, there must be at least one S3 library that has its If none of the S3-backed libraries have those settings, then no upload button is offered, and it can be confusing to admins why the option isn’t given. We added a banner at the top of the page (visible to Sys Admins only) that displays a link to the documentation in this scenario. | |
Usability Enhancement | Updated merge feature to resolve blockers The merge account feature did not fully support all merges if the account had certain unique characteristics. We now allow merges in the below conditions:
| |
Configuration Enhancement | Allow templates to be source of a PickList Picklist and Multi-Select attribute allow Custom Lists as well as Multi-Select and Tag Lists to be the source of the list. There are times when a Template attribute is needed to dynamically control the content of a list. | |
Defect | Behavior chain of LPI -> Bulk Activity Action -> Linked Learning Plan Action fails (cyclical loop) We have configuration scenarios where a workflow action triggers a Bulk Activity Action which triggers a Linked Learning Plan Instance Action. We resolved a defect where it fails running the Linked Learning Plan Instance Action because the first behavior does not adequately release a hold on the workflow instances inconsistently. | |
Defect | Activity added via API creates application error when deadlock occurs We resolved a defect where applications are unable to be opened and generate an error when activities are added via the Activity GetOrCreate API Endpoint that fail due to a deadlock. |