Major
Detail
Major
Detail
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
Bugfix
Deleting the selected element in the Model Editor detail view can delete the "wrong" element in the diagram. The delete action performs the following two functions:
- Deletion of the persistent model element
- Deletion of the client-side diagram element and updating the set of selected diagram elements.
Removing the persistent model element updates the "subject object types" tree. In particular, the selection of the tree is adjusted. If the deleted subject object type has a super type, it is selected, otherwise the enclosing module is selected. Then the set of selected diagram elements of the graph component is updated. The detail view receives a new model. This leads to the fact that afterwards the second function works with "wrong" objects and thus does not remove the element with the deleted object from the diagram, but that newly selected.
Test
- Create new module M.
- In M` create the type `A with the subtype B.
- Then delete B via the detail view or in the diagram itself.
- In both cases the element for B` should be removed from the diagram and the selection adjusted to `A.