Major
Detail
Major
Detail
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
Bugfix
Detail
#27197
Missing component model for grid object initialization with multiple input channels
If a grid is configured in-app, a combination of different channels can be used as a model. The model of the grid is accordingly a list.
Improvement
If the button "New row" is configured, then a container object can be calculated from the model, which is given to the initialization function. This object must be a tl:TLObject, so that in this case the model of the component cannot be used.
The initialization function receives the so computed container object as well as the component model, so that during the initialization access to the complete context exists.
In the normal case however model == container is a tl:TLObject.
Code migration
In unfavorable cases, the assignment of the "link operation" parameter in creation dialogs changes:
- Previously, the operation received two arguments (the create context and the new object). Previously, this create context should actually be the object into whose composition relation the newly created object is to be inserted by the link operation. However, this create context was de-facto not the object that was also used as container for the object created transiently in the form, but the model on which the create handler was executed.
- Now the link operation receives three arguments. As before, the container object into whose composition relationship the newly created object is to be inserted, the new object, and now the model of the create command handler.
- If the creation form did not have a model before, but the context model was only passed to the create handler, it must now (preferably) be ensured that the context object is already present in the create form as a model. Alternatively, the third argument of the link operation (instead of the first) can be used.
Test
TestRegression27197.script.xml