Metamodel path from Application object to Flow?

[BenAvdicevic]

Hi,

I am using the new Dendrogram instant report feature in Aquila 6.1
Many of our users are interested in quickly knowing inflows and out-flows for their assets.
However, I am not able to figure out how to create a dendrogram showing a relationship between an Application and its Flows.

I tried using the target object type as "Message Flow" but it doesn't show any flows for an application I know has many flows connected.

Also, I tried searching for "Exchange" as target object type. but that is not possible.   For example, I thought to use "owned Exchange" relationship.
When I look at the Application object Properties, the Exchange section of the Characteristics page - I do see many Sent and Received flows.    What is the metamodel path to those?

[PBessodes · Accepted solution]

Yes there is. The more generic objects to use concern the sender/receiver agents. Using the abstract object (where application flow is defined) gives you all type of sender/receiver.

Attached is an example to import. You need to activate "Display Abstract MetaClasses" option and not pay attention to error message (due to lock on standard Hopex objects but no change is necessary - just the export/import process implying standard Hopex data)

NB : From 6.2 this can be done more easily by using the new "Flow" object that is automatically synchronized with application flows used in diagrams but is not contextualized. It identifies a flow between agents directly (no scenario of flows, no environment, no participant/partner etc.)

[BenAvdicevic]

Thanks for that @PBessodes .

In my testing - using  Application -> Participant Application -> Sent/Received Flow  only returns flows from Application System scenario of flows.

But, Flows from Scenario of Application Environment Flows are not.

Is there a more "generic" flow concept that captures "ALL" scenario flows - no matter the source diagram?

[PBessodes · Accepted solution]

Hi,
Dendrogram presentation is very limited and will not fulfill your requirement (only one branch is possible from a node when you need at least 2 for sender/receiver). BTW the path is Application -> Participant Application -> sent Application Flow/received Application Flow.
To obtain what you want I recommend you to use a tree set definition. It will allow you to do exactly what you want and create a report template that any user will be able to instantiate for its own purpose. It will even allow you to use queries, thus replicating behavior of application property page in the "Echange" section (which is calculated).

[BenAvdicevic]

@PBessodes Any recommendations appreciated.