In HOPEX V5, Application object has a built-in report called "Application Exchange Density".
It is documented on this page like this:
If you open Application A and open the "Exchange Density Report", it will show you ALL known flows between Application A and other agents.
The problem is - looking at the report - there is no way to know which exchanges represent CURRENT state and which represent TARGET state..
There is no "Context" filter, for example, so that I can select either CURRENT or TARGET state flows.
Wouldn't it make sense to add "Context" filter to this report , to help with the above described scenario?
Is there a better way of looking at this?
Solved! Go to Solution.
Thanks for confirming @DaveM .
yes - working with "time dimension" in HOPEX is not trivial. there doesn't seem to be a great approach -however you manage it.
I think its generally hard thing to do. Architecture models are not code. Git-like management of objects is not the answer also.
I feel if I could add a "time dimension" to the metaassocitations or maybe objects also - it would be helpful.
LIke, If I draw a flow or an interaction between objects - select "target state" or "candidate 1 state" or "currrent state". for that object.
Then - you can generate reports like Exchange Density and filter by time dimension.
I realize this is likely too simplistic.
Hope there is a better way in future to manage this...
This is the ongoing dilemma of how to show Current vs Future State in HOPEX. To make your scenario work you would need to have Application A Current State be a separate object to Application A Future State - maybe by Duplicating it and keeping versions (version2.0) and/or having it reside in a different Library (or anywhere else that can "namespace" it).
You could also potentially use Logical Applications to describe Future State but then it is more difficult to show the differences.
Appreciate any input on this.
WARNING We have changed our authentication method to support single sign-on (SSO).
To learn how SSO will affect your access to the MEGA Community, please read the FAQ here