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
enhancement
Creating application views currently takes place in a "what-you-see-is-what-you-get" mode. In other words, you create a view and see that view. To edit the view’s parameters, you must view the view in order to modify its configuration.
This approach is a great solution in many cases because it eliminates the need to navigate through a large configuration tree to find the specific location where a particular property can be set or changed. Instead, you can navigate to the problematic location in the application and display the subconfiguration there. However, this approach reaches its limits if you’ve made an error that prevents a specific view from being displayed at all. In this case, the only option so far has been to export the layout to the development environment and edit the XML there.
This can happen quite easily if you make a mistake in an executability rule that causes a button not to be displayed at all or to no longer be displayed.
Improvement
A Layout Editor view in the Development area where you can view, edit, and create the configuration of all the application’s layouts without having to display the corresponding parent view at all (or switch the application to design mode).
Test
Navigate to the Administration > Development > Layout Editor view, and edit and save a legacy and a template layout.