The version is released in minor version 2024.9.1.3545, since an unpleasant bug caused by development of the new feature was discovered after release.
.NET 8.0
The version 2024.9 doesn’t bring any metamodel changes, but it is the first Origam version built on .NET 8.0. In case of hosting application behind IIS, you need to download and install appropriate hosting bundle.
Removal of stack trace in server responses
The version 2024.9 marks beginning of our journey to remove stack trace information from server failure responses. Unfortunately validation errors are also treated as exceptions, thus the process is complicated. The system behaves as before (meaning returns the same responses) only in Development environment. By default system is set to be in Production environment, this also goes for our docker images. The theory behind this system is described here. If you’re facing complications resulting from this change you can default to Development environment as a temporary solution until the issue is resolved.
How to set docker container as Development environment
Set environment variable ASPNETCORE_ENVIRONMENT of the container to Development
How to set IIS hosted application as Development environment
Add following element under aspNetCore element in web.config file.
It is now possible for each user to configure the screen to always start with the filter UI enabled. The focus is also set to the first field of the filter UI.
We’re continuing with removing stack traces from the server responses. As a side effect of the stack trace removal, the rule exceptions weren’t returned in API calls. This patch solves also this issue.
Front end contains solution for setting time in fields with full month name date format.
Same as 2024.8.2, this patch contains fix for deployment script generation in Architect.
Dragging and dropping between input controls could inadvertently copy partial values, leading to incorrect states. This issue has been resolved by disabling drag-and-drop functionality for input values.
Selection Dialog Behaviour Consistency
When opening a screen with a selection dialog from search results, the selection dialog was displayed. This behaviour differed from opening the same screen via Ctrl+Click on a lookup control, where the selection dialog was skipped, and the screen results were shown directly. The behaviour is now consistent across both scenarios, with the selection dialog being bypassed, and the screen results displayed immediately.
An issue caused checklist filter options to fail to load correctly when another field already had a filter applied. This has now been fixed, ensuring smooth functionality.
Copying Text Fields
Previously, when copying a record, models configured to modify a field value (e.g., prepending "Copy of ") could result in a generic error if the concatenated text exceeded the maximum field length. The engine now trims the result from the right to comply with field length limits, avoiding such errors.