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
(User-visible)
If you create a new tab in-app and then create a new form without specifying the model (and type), the tab will no longer be visible after logging in again.
The visibility calculation for a component—especially a tab—checks throughout the component tree to see if any of these components are visible, i.e., whether supportsModel(..) == true.
An in-app form without a model is not supported. However, this results in the user not seeing the tab and thus having no way to fix the problem. This is undesirable, since the problem can usually be easily resolved by editing the form configuration.
Test
- Create a new tab.
- Create a new form without specifying a model (type).
- Log out, log back in, and check whether the tab is still visible.
- Set a model in the form configuration and check the displayed form.