major
minor
major
minor
#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.
defect
minor
#27197
Missing component model for grid object initialization with multiple input channels
When configuring a grid in-app, you can use a combination of different channels as the model. The grid's model is therefore a list.
Improvement
When the "New Row" button is configured, a container object can be derived from the model and passed to the initialization function. This object must be a `tl:TLObject`, so the component’s model cannot be used in this case.
The initialization function receives both the container object calculated in this way and the component model, ensuring that the full context is accessible during initialization.
Normally, however, the model == container is a `tl:TLObject`.
Code Migration
In some cases, the parameter assignments for the “Link Operation” in creation dialogs change:
- Previously, the operation received two arguments (the create context and the new object). Previously, this create context was supposed to be the object into whose composition relationship the newly created object was to be inserted via the link operation. However, this Create context was not, in practice, the object that was also used as the container for the object created transiently in the form, but rather 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, newly, the model of the Create command handler.
- If the creation form previously had no model, but the context model was only passed to the Create handler, you must now (preferably) ensure that the context object is already available as the model in the Create form. Alternatively, the third argument of the Link operation can be used (instead of the first).
Test
TestRegression27197.script.xml