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.
Bugfix
Detail
#26928
Hidden component does not appear anymore, although it gets a supported model
If a component does not derive its authorization object from its model but from another component channel, its visibility may not be adjusted correctly when the model is changed. When the model is changed, the component tries to calculate whether its visibility state has changed. To do this, it calculates the visibility with its old model and with its new model. Only if the state differs it informs about a visibility change. But if the visibility does not depend directly on the model at all, this check is wrong and possibly too few events are sent for a visibility change. As a result, a component either does not fade out or does not fade in again.
Test
- Configure view with security master component that gets its authorization object from a component channel.
- Check that the view fades in or out depending on the object on the channel.