major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
defect
If you add a default value provider via an expression for an attribute in the customizations, the user must enter two expressions to calculate the default value—specifically, one for the GUI.
Suppose the user has entered different expressions—for example, "test" as the expression for the default value of a string-type attribute and "testGUI" for the expression displayed in the GUI— then, as expected , “testGUI” is displayed as the default in the form of the creation dialog for a new object. However, after the object has been created, only “test” is displayed in the form—that is, **not** the specific expression for the GUI. This is inconsistent.
Code Migration
The configuration of `tl:DefaultByExpression` has changed. It now contains only an expression for the default value. In particular, the additional expression for the default value displayed in the UI has been removed.
- The configuration in the *.model.xml model files must be adjusted accordingly (remove the*default-for-ui* configuration option).
- Annotations on attributes in the database are automatically migrated the next time the application is started. The application model in the TLProperties table is also updated.
Test
Verify that the default value in the creation dialog and the value in the editor are the same.