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
Bugfix
Detail
#26260
Error message in ObjectTreeNaming if the searched label is correct
In the implementation of #26096, a tl:TLObjectTreeNaming was introduced to identify a node in the tree by its label. Starting at the root, it navigates along its children until the node it is looking for is found. In each of these steps, it checks if the next node along the tree path is valid. This happens based on its label. However, this check throws an exception if the searched label and the node's label are the same. This is meaningless.
Test
/com.top_logic.demo/src/test/com/top_logic/demo/scripted/layout/inapp/TestDragAndDrop.script.xml