So SVYFRMWK-592 is seemingly not a bug, it is a design decision. Also the guideline, if I understand the framework design decision correct is, don’t use “own tabpanels with relations” on forms.
My use case is the following:
I have a form for created documents.
On that form I use 2 tabpanels:
On the first tabpanel I have 1 tab that contains a form that used for defining time periods.
On the second tabpanel I have 2 tabs for adding and deleting positions.
The first tab contains a form for adding / deleting commissions.
The second tab contains a form for adding / deleting other positions.
The problem is if, something is added or deleted in the tabpanels and dc_cancel is called, no restoring / rollback from the framework for the old values is available. Also no question dialog, if fields in tabpanels are edited, is showed.
Further the documents consists of the informations in the tabpanels, so if I created a new one, it should be possible to have the tabpanels in edit mode for adding, editing and deleting things. Also if I edit a document, it be would great to have all tabpanels in edit mode for adding, editing and deleting something.
If I understand the framework design decision correct, I should have for every form in a tabpanel an own program, use the desired layout and add it as register in navigator using the desired relation.
Problem now is, if I edit the head data for the document, I have to click the save button after every new record / add for the time periods, commissions and other positions. Further the time periods and positions not used anywhere else. These are document specific things.
It is possible to modify this usability?