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
enhancement
major
#25421
Customizations für mehrere Typen in in-app Formular
An in-app form component displays either the default form for objects of any type, or a "special form" for objects of exactly one type.
It would be better if, instead, the component displayed the object’s standard form for objects for which it has no form customization, and if form customization could be applied to more than one type.
Test
- Configure an in-app form next to a DemoTypes tree.
- In this form, customize the display for Type A.
- Select a C in the tree—the standard form should be displayed for this object.
- Then customize the form for C as well.
- Select an "A " again—the custom form from Step 2 should still be displayed.
Code Migration
- Schema change in layouts. For workspace files in the project (followed by normalization):
find webapp/WEB-INF/layouts -name \*.xml -print0 | xargs -0 -n 1 -I{} xsltproc -o "{}" ../com.top_logic/webapp/WEB-INF/kbase/migration/tl/Ticket_25421_multiple_forms_inapp.migration.xsl "{}"
- Layouts in the database are migrated automatically.