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
(User-visible)
Detail
#27180
Default label for components in the Inspector
When the Application Inspector is opened Administration > Technical Administration > Views the labels of the components are written. If a component does not have a label, a "missing resource error" occurs.
Improvement
If there is no label for a component, the name of the component is used:
Test
In the demo:
- Switch to Administration > Technical Administration > Views
- Selection of "Technical Demo
- "Open Inspector
- Expectation: At the component (e.g. parent) either a label or the technical name of the component is displayed.