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
- If an enum or a classifier is created in-app, there are no constraints on the names in the dialog:
- If the enum name is empty or ends with a '.' there will be an error in the log.
- If the name contains a space or is completely empty " ", there will be no error. This is probably not a good idea.
- If the classifier name is empty, a KB error occurs.
- If the name ends with a '.' there will be an error and the GUI is totally broken.
- Furthermore it comes to errors if a classifier is deleted and then a new one is created. In such a case the index of the classifier is not updated.
- If a module is created with "." at the end, errors occur.
Solution
- The name of an enum and a classifier must match the pattern [a-zA-Z_\-](\.?[a-zA-Z_\-0-9])*. '.' is still necessary for historical reasons. The name of an enum may not be changed after it has been created.
- After changing an enum, the index of the classifier is adjusted.
- The name of a module must match the pattern [a-zA-Z_\-](\.?[a-zA-Z_\-0-9])*. The name of a module may not be changed after it has been created.
Test
TestEnumerationCreation.script.xml or
- Create an enum in APP
- Expectation: The name must not be empty or end with a dot, for example.
- Create a classification
- Expectation: The name must not be empty or end with a dot.
- The names of the created enumerations and classifications must not be changeable.
- Create a module in APP
- Expectation: The name must not be empty or end with a dot.
- The names of the created module must not be changeable.