Enhancement
Major
Detail
Bugfix
Detail
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
Bugfix
Detail
#25322
Form field for mandatory DateTime attribute incorrectly marked as changed
Declared a DateTime attribute as a required field and then placed a corresponding field in the form for the subject object.
Problem
When filling the field, it is still marked as "must not be empty". I still managed to save the value. Nevertheless, the field was still displayed as "must not be empty". This made it impossible to leave the view, because the Check-Changed dialog prevents this. There are no changes to "Apply" or "Discard", so the only option left is "Cancel". After logout / login again, the field was marked as "must not be empty" again directly when the mask was displayed and leaving the mask is then no longer possible.
Workaround
Do not mark DateTime attributes as "mandatory".
Test
- /com.top_logic.demo/src/test/java/test/com/top_logic/demo/scripted/model/attribute/TestMandatoryDateTimeAttribute.script.xml