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
minor
#25866
Layout-Editor: Layout-Export scheitert bei Layout mit Fehlern in der Datenbank
When developing layout templates, it often happens that you adjust a template’s parameters in a way that makes them incompatible with existing layouts in the database. Such a layout can then no longer be loaded. If you subsequently hide such a defective layout and create a new component, the application appears to be working again, but the application layout can no longer be exported to the development environment.
Test
- Add a meaningless new Boolean property to table.template.xml.
- Create a new table and check the box for the meaningless property.
- Reset the table template.
- Export the layout.
- Log in again.
- An error message appears; the new table view is empty.
- Remove the table view again.
- Log in again.
- Create another layout.
- Export layouts.
- Expected: A functional layout is exported. A message appears stating that not all layouts could be exported successfully. You are asked whether the layouts in the database should be cleaned up anyway. If you answer “Yes” to this prompt, no error message will be displayed when you export the layouts again.