enhancement
critical
major
minor
minor
#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
defect
When creating a new dialog transaction with input fields, the order of the buttons in the ButtonBar is not consistent with the rest of the application. The button to close the dialog is rendered first, followed by the button to execute the action.
For example, if you create a dialog for creating an object, the button to create a new object appears first, followed by the button to cancel. The "Close" or "Cancel" action should be positioned as far to the right as possible.
The issue with the order in the “Transaction with Input” dialog lies in the configuration of the transaction handler. It belongs to the “main” clique, while the “Close” command belongs to the “close” clique in the “basic-edit” group. The “main” clique group is positioned before the “basic-edit” group. For the ButtonBar, commands from cliques in the same group are rendered in the order they are arranged; however, commands from cliques in different groups are “inverted,” i.e., their order is reversed. Commands from cliques in the last groups are rendered first, and commands from cliques in the first groups are rendered last.
Code Migration
In layouts that use transactionAssistent.template.xml, the clique must be changed from “main ” to “apply.”
Test
Configure a "Transaction with Input" dialog—for example, for a table—and verify that the "Close" button is positioned on the far right.