nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FTA: Dragging an existing event from model browser onto gate

medini_1036016653

Dear medini, as of v2019R1.1 it seems to be not possible to drag an event from the model browser on a gate that is displayed on the diagram. It is only possible to drag the event onto an empty area of the diagram, then select "connect" and then to do the actual assignment. Use case: We want to clean up the model browser by adding our events (which may contain subtrees) below a helping event named "collecting event". Best regards Peter

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024120963

Hi Peter, the way of modeling is not intended behavior currently. Therefore I have created the ticket "FTA: Dragging an existing event from model browser onto gate (#8802) " BR Joël

All comments

medini_1036016653

Feature request: When multiple events are selected the "connect" function shall be able to connect multiple events to the target gate (or vice versa): I obtained that view after I dragged&dropped four events from the model browser onto an empty area of the diagram. Current behviaor: "connect" merely is able to connect a single event with the gate. Best regards Peter

medini_1024120963

Hi Peter, in order to clean up an existing FTA, I would recommend you to use transfer gates. Undo the connection to the upper level element not gate. Copy and past the disconnected part to a new diagram. Delete the element source from the old diagram. Create a transfer gate below the upper level element and point to the new diagram. BR Joël

medini_1036016653

Dear Joel, what you are describing is only partially adressing my issue. We have so many "loose" events in the model browser, as each of them reprents a top level event of a diagram (we have many child diagrams). We want to further clean up the model browser bei collecting the TLE's below a helping event, the "collecting event". You are describing an approach for splitting a tree from a single diagram to two diagrams into two "sub-trees". This process is not efficient itself... May I wish that "Copy and past the disconnected part to a new diagram. Delete the element source from the old diagram. Create a transfer gate below the upper level element and point to the new diagram" were a single step :-) "create part of a tree and drag&drop it to another diagram" -> a modal dialog asks if the highest moved event shall be linked by a transfer gate: yes -> create transfer gate in the source diagram no -> disconnect the moved sub-tree from the source diagram What do you think? Best regards Peter

medini_1024120963

Hi Peter, the way of modeling is not intended behavior currently. Therefore I have created the ticket "FTA: Dragging an existing event from model browser onto gate (#8802) " BR Joël