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
When problems occur with Kafka or TL-Sync, they often overflow the application log. This can happen even when everything is working. To prevent application log overfilling, Kafka and TL-Sync should write to their own log files.
Code Migration
The naming scheme of the log files has changed:
- Old: top-logic.main.log.1
- New: top-logic.main.1.log
- Custom log configurations may need to be adjusted to make all environments behave the same.
- The company should be informed. There tools for monitoring the logs may have to be reconfigured because of the naming scheme change.
Test
- Start an application that uses TL-Sync.
- Check that a .kafka.log file is created and used.
- Check that the log messages there do not show up in the .main.log file.
- Check that the other log files are still created and used correctly.
- Check that DEBUG messages are still not logged.