Enhancement
Critical
Major
Detail
Detail
#25907
Layout editor: inconsistent behavior of unfold state, selection and reaction to object creation
#25951
Application tests: CheckLabeledExecutabilityOp fails to assert non-executability of literal ResKey reasons.
#25952
Model Editor: Enum default provider does not work for enum references for which singleton link storage was explicitly selected
#26002
ConfigurationItem-valued properties with format annotations may cause an attempt to create abstract config items when deserializing null values
#26012
Help editor crashes when a user has chosen a language that is not in the supported languages of the application
#26039
Gridcomponent: Display of context menu for new (transient) row object leads to UnsupportedOperationException
#26085
An attribute of type tl.model.search:Expr is not displayed in the form above a TL script editor
#26111
Context menu commands for table rows are erroneously executed on the table model when opening the context menu in the background of the table
#26153
Migration: Replay fails if string values with line breaks are contained in the dataset where a line ends with a semicolon
#26171
A TL script expression entered in a wizard template is reformatted when transferred to the final template
#26223
TL script: Under unfavorable conditions wrong parameter values when evaluating local functions
Enhancement
Detail
#26195
Introduce "commons" classifier for in-app implementations.
Classifiers can be specified for in-app implementations. When this happens, they can be found specifically when using "tl:InAppImplementations".
Implementations classified in this way are then not displayed in places that do not require classifiers.
Especially for command implementations, another classifier "commons" should be introduced, which selects implementations that can be used sensibly at all components. This is necessary, because in other places only very special commands can be selected, which are nevertheless also generally usable.
Code migration
- In-app implementations of tl:CommandHandler where a classifier is set and which are also generally useful, the additional classifier "commons" must be set.
- Uses of acceptable-classifiers where a classifier is set, and generally useful implementations are to be used, the additional classifier "commons" must be set.
Test
An example:
- Switch to Technical Demo > Components > Tables and Trees > Tree
- Edit view.
- Expectation: The button Custom transaction is available.