|
Hallo Stevek,
thanks for this fast response.
i think i tried already the table has 3 templates all of them with same collection property and the "use subobjects as ports". the dots are taken from symbol lib.
The Table has a attribute "Fragen" which is a collection of "Frage [Tabelle]"
This attribute us used in the "Tabellen" Object to show some information and where the 3 templates are that are showing as ports.
And in the Binding for example the "Validation" relation is linked to the Table Object and there with the
collection base "Frage [Tabelle]" as a dynamic port.
But Problem is that connection from any of the Relations ( either "Validation" or "Abhängigkeiten" ) connects only to one of the 3 visible ports. ( doesnt matter which its automatically jump to one of them ( maybe in my case yellow because it was the first created, i don´t know !)
The semantics is "easy" we have a system where users are getting "questions" in an app (tablet) and this questions could have dependences ( "abhängigkeit" ) to other questions -answers if the questions are shown or not and they questions have validations rules where the answers checked against (if not messages are shown). there is also a relation which gives the shown order.
APF are only some kind of same relations as a subgraph which where shown in diffent ways like in a popup , different page or immediate after the connected question.
Every tables cells defined here (header of a column) you can immagine as "questions" as well with all same dependencies and validation rules. that is why there are 3 "ports" in the table to let users connect to each cell a APF , Dependency Rule or Validation Rule.
(for example a "Abhängigkeit" relation could mean a column or even a cell is shown or disabled depending on the answers of other questions )
What i want to achive is from this visualisation a generated output to fill our configuration tables in db with it. Our system will taking this configurations and some runtime data and transform it first to json which is send to => app which is render them to => end user.
In this case the question rules inkl. all other stuff could be more easily developed by our business itself and need less programming support.
br
|