Enhancement
Critical
Major
Detail
Detail
Detail
#26220
Transaction with input: button order inconsistent
If you create a new transaction dialog with input, 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 for creating a new object is rendered first, followed by the button for canceling. The "Close" or "Cancel" action should be placed as far to the right as possible.
The problem with the order in the Transaction with Input dialog is in the configuration of the handler for the transaction. It belongs to the clique main, the command "Close" to the clique close of the group basic-edit. The group of the clique main is located before the group basic-edit. For the ButtonBar, commands from cliques of the same group are sent as ordered, but commands from cliques of different groups are "inverted", i.e. the order is reversed. Commands from cliques of the last groups are rendered first and commands from first groups are rendered last.
Code migration
In layouts that use the transactionAssistent.template.xml, the clique must be changed from main to apply.
Test
Configure a "Transaction with input" dialog for e.g. a table and check that the "Close" button is on the far right.