Flow charts at first glimpse

[skiwi]

I needed a flow chart - http://www.sparxsystems.com/downloads/quick/strategic_modeling_with_enterprise_architect.pdf.

Some initial experiences (on build 1009).

On page 9 of the above document there are step by step instructions, and an illustration. In the illustration the stereotype bleeds through for Begin and Decision.

On page 10 the stereotypes have disappeared, how?
This is not covered in the steps.
<answer Diagram | Properties | Elements tab | untick Show Element stereotypes>

Trying to move a connector from a Process to InputOutput,
it will not connect to the new target!



Although in Settings I have set Alias usage "Alias and Name", and Diagram properties to  "Use Alias if available" adding an alias to a connector hides the connect name - both should show.

[AndyJ]

"Although in Settings I have set Alias usage "Alias and Name", and Diagram properties to  "Use Alias if available" adding an alias to a connector hides the connect name - both should show."

I can confirm that I'm seeing the same here.

Name and Alias are only both exposed for Classes, not Associations.

For associations, the "Use Alias When Available" setting seems to be a toggle, Alias or Name, not both.

Despite the setting in Tools|Options|Diagrams|Behaviour - "Alias Usage - Alias and Name"

[skiwi]

In EA 11.11 it still does not seem possible to change the source of a connector to another source

In the picture above the connector will not connect to the InputOutput entity.
reported

[skiwi]

Prompt and good response from Sparx, thanks

Our developers have confirmed that this is a bug and it is logged to be fixed. We cannot yet say when (in which build) the fix will be implemented.
 
Please note, typically you should not go from a start element straight to a data element (input/output); the data element should be the result of some kind of processing. If you do want to do this can switch off syntax checking of connectors via the "Tools | Options | Links | Strict Connector Syntax" option.
 
We plan to make the following changes to this behavior...
- EA's syntax checking shouldn't fire when elements from non-UML profiles are involved (i.e. for elements with metatypes) unless we specifically want it to (e.g. BPMN).
- When a connector move is illegal, EA should return an error/warning message, not just fail silently.