#28288 Dynamic visibility requires fields for dependent attributes

Enhancement

Major

#26586

Direct updating of calculated attributes in forms and grids when editing input values

#26702

TLScript: sendMail() function

#27216

Attribute annotation "fallback value" as replacement in case of empty value

#27457

Conditional formatting in tables/grids/forms

#27784

Java 17 as a development environment

#28122

Layout editor: Generalized form templates

#28151

TLScript: new ParseCSV function

#28263

Allow to specify the deletion policy for a reference in the model

Detail

#27920

Removal of old themes and adaptation to the core theme

#28144

Display button line via template, no more button lines in administration views

#28214

Update pac4j-oidc

#28292

Set tl-license-professional version in tl-parent-all

Nice to have

#28282

tl-demo: Example for TreeGrid with synthetic root node

Bugfix

Major

#28197

Sorting a composition table by a column with SelectField leads to ClassCastException

Detail

#27787

Missing context suggestions for TL script functions with underscore in the name

#28071

Deletion of inline composition elements in the form fails if deleted object triggers further deletions

#28175

Script Recorder: Saving scripts does not display the file name field

#28184

Eclipse settings: Update of the webfragment version to 6.0

#28283

Migration processor for cleaning up multiple references to the same composition

#28288

Dynamic visibility requires fields for dependent attributes

Bugfix

Detail

#28288

Dynamic visibility requires fields for dependent attributes

InAppDevelopment

The annotation Dynamic visibility can be set for an attribute. For example, a field can be shown or hidden depending on another attribute.

In a settings component, this only works if a field is displayed for the dependent attributes.

Test

TestDynamicVisibility.script.xml