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.
enhancement
The tl:BulkIdLoad is used to load a large number of objects with as few database accesses as possible. The objects’ attributes are also loaded, but only those that are present in the object’s own table.
Improvement
The attributes in the FlexData table should also be loaded.
Implementation
The tl:BulkIdLoad now also loads the Flex attributes. To do this, the FlexAttributeFetch method is additionally executed for the objects in loadUncachedInRevision(long).
Related Tickets
The idea originated as part of #26910.
Test
No test. It can be tested manually in the Kafka demo with some effort:
- Disable the tl:KBDataProducerTask in the SchedulerGUI.
- Create many objects.
- Restart the application.
- Enable the SQL Monitor.
- Re-enable the task mentioned above.
- Wait until the task has been executed.
- Check the SQL Monitor to see how many queries were executed.