Can't edit Direction of Information Flow in version 16.1.1623

[Mauricio Moya (Arquesoft)]

I have just installed version 16.1 build 1623 and now I note this behavior: if you create a connector of type "information flow", and then you double click the connector to open the connector properties, it doesn't allow to change the Direction of the connector.

Anybody with the same issue in the same version? (or recent versions?)

[jfzouain]

Hi Mauricio

Information Flow - Right-Click on connector - Advance - Reverse Direction
Voila

Regards

Jose Zouain

[Mauricio Moya (Arquesoft)]

Hi Mauricio

Information Flow - Right-Click on connector - Advance - Reverse Direction
Voila

Regards

Jose Zouain

Thanks, but what if I need to set it as bidirectional? or undefined? I want to be able to edit the connector, why not?

[Geert Bellekens]

Hi Mauricio

Information Flow - Right-Click on connector - Advance - Reverse Direction
Voila

Regards

Jose Zouain

Thanks, but what if I need to set it as bidirectional? or undefined? I want to be able to edit the connector, why not?

Can information flows be bidirectional, or undefined? I don't think so.
From the UML specs:

InformationFlows require some kind of “information channel” for unidirectional transmission of information items from sources to targets.

Maybe EA has been updated to only allow valid directions for connectors?

Geert

[Paolo F Cantoni]

[SNIP]Can information flows be bidirectional, or undefined? I don't think so.
From the UML specs:

InformationFlows require some kind of “information channel” for the unidirectional transmission of information items from sources to targets.

Maybe EA has been updated to only allow valid directions for connectors?

Geert

We make an exception for derived information flows (typically derived by the union of two -opposite- unidirectional flows).  They can be marked as bidirectional.  This allows us to create summarised views that aren't cluttered with detailed flows.

Paolo

NOTE: we use derivation relationships to link the derived to the more canonical flows.

[ahavey]

We are experiencing the same issue. Bi-directional flows were allowed in version 15. So this is a change made in version 16?

What is recommendation for modeling true bi-directional flows like HTTP?

[qwerty]

We are experiencing the same issue. Bi-directional flows were allowed in version 15. So this is a change made in version 16?

What is recommendation for modeling true bi-directional flows like HTTP?

HTTP uses different port to and fro. So it's not bi-directional.

q.

[ahavey]

Regardless of the example, did version 16 deliberately change this behavior?

[Eve]

did version 16 deliberately change this behavior?

Yes.

Release Notes for 16.1 Build 1621
*********************************
...
Diagramming
  ...
  Disallow change of direction for Information Flow

[ahavey]

bummer.

Thanks for the confirmation.