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.
Enhancement
The tl:BulkIdLoad is used to load a set of objects with as few database accesses as possible. The attributes of the objects are also loaded. However, only those that are in the table of the object itself are loaded.
Improvement
The attributes in the FlexData table should also be loaded.
Conversion
In tl:BulkIdLoad now also the Flex attributes are loaded. For this purpose, the FlexAttributeFetch for the objects is also executed in loadUncachedInRevision(long).
Related tickets
The idea originated in the context of #26910.
Test
No test. Manually it can be tested in the Kafka demo with some effort:
- Disable the tl:KBDataProducerTask in the SchedulerGui.
- Create many objects.
- Restart the application.
- Turn on the SQL Monitor.
- Reactivate the above task.
- Wait until the task is executed.
- Check in SQL Monitor how many queries were executed.