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
minor
#26259
Scriptrecorder template creation does not respond to new actions / Saves outdated work state
As a result of Ticket #26185, and in particular the change in r303564, the model type for the tl:TemplateCreateBuilder was changed from ActionContainer to tl:TLTreeNode.
If the user selects a node in the ActionTree and opens the dialog to create a template, the form with the actions uses the selected TLTreeNode as its model. If the user then creates the template or closes the dialog and records additional actions using the ScriptRecorder, the dialog for creating a template—which initially used the same selected TLTreeNode —does not contain the most up-to-date data. Specifically, the changes that occurred between the opening of the two dialogs are missing. The problem is that the FormComponent does not detect the change. Only the BusinessObject of the `TLTreeNode` has changed, but not the node itself. Consequently, the component assumes that its model has not changed and thus prevents the `tl:FormContext` from being rebuilt. This results in a potentially outdated state of the data.
Test
- Record a few actions
- Save the actions as a template using "Create Template"
- Record additional actions (do not close the Script Recorder window; just continue)
- Call up "Create Template" again
- Problem: The "Create Template" dialog box still contains the old values from the first save (path and actions). As a result, the current state of your work isn’t saved—instead, it saves something from before that (in this case, from step 2).