Author Topic: Cannot add object node to an activity with any relationship  (Read 1057 times)

an22_07

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Hello,

The issue, which appears in EA 13 and EA 14 (haven't used the earlier versions), is that after connecting an activity with any other element, it is impossible to add object node to this activity via context menu (New Child Element > Object Node) - nothing happens after clicking that option. The object node can be added only by using the Object Flow.

Has anyone also encountered this issue? Where/how can I report it, if it's actually a bug?

Thanks in advance.
« Last Edit: June 17, 2019, 06:02:20 pm by an22_07 »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 10418
  • Karma: +343/-30
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Cannot add object node to an activity with any relationship
« Reply #1 on: June 17, 2019, 09:25:02 pm »
You shouldn't try to add object nodes to Activities, or link Activities with other stuff.
On Activity diagrams you should only use Actions. This is similar to State Machines and States. You don't use State Machines on State Diagrams either.

Geert

michielper

  • EA User
  • **
  • Posts: 149
  • Karma: +2/-1
    • View Profile
Re: Cannot add object node to an activity with any relationship
« Reply #2 on: May 18, 2020, 10:25:10 pm »
You shouldn't try to add object nodes to Activities, or link Activities with other stuff.
On Activity diagrams you should only use Actions. This is similar to State Machines and States. You don't use State Machines on State Diagrams either.

Geert

Well, but what about interacting state machines? A very useful concept to model real-world situations. It would seem logical to be able to draw a diagram with state machines interacting through intermediate states, similar to what one does with Petri Nets. Wouldn't the resulting diagram be called a State Diagram?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 10418
  • Karma: +343/-30
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Cannot add object node to an activity with any relationship
« Reply #3 on: May 18, 2020, 11:41:22 pm »
You shouldn't try to add object nodes to Activities, or link Activities with other stuff.
On Activity diagrams you should only use Actions. This is similar to State Machines and States. You don't use State Machines on State Diagrams either.

Geert

Well, but what about interacting state machines? A very useful concept to model real-world situations. It would seem logical to be able to draw a diagram with state machines interacting through intermediate states, similar to what one does with Petri Nets. Wouldn't the resulting diagram be called a State Diagram?
I mentioned State Machines in the general sense since people generally use this correctly with State Machines, but incorrectly with Activities.
I do not have an opinion about the using state machines on a State Diagram since I haven't really looked at that.

Geert

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 7290
  • Karma: +84/-12
    • View Profile
Re: Cannot add object node to an activity with any relationship
« Reply #4 on: May 19, 2020, 08:23:23 am »
Well, but what about interacting state machines? A very useful concept to model real-world situations. It would seem logical to be able to draw a diagram with state machines interacting through intermediate states, similar to what one does with Petri Nets. Wouldn't the resulting diagram be called a State Diagram?
A State can be composite, which means the behavior of that state is described inline. This is the equivalent of a Structured Activity Node on an Activity diagram.

When you want a composite behavior to be re-usable, you can convert it to a StateMachine and reference it with a SubMachineState (a state with SubMachine set). As already mentioned, you use a CallBehaviorAction within your Activity flow to reference another Activity.

Interestingly, this dual/inconsistent ways of describing the same basic concept is one of the places where UML still shows its history as a unification of two different modeling techniques. State Machines don't have the same problem as Activities because a State can be structured, or reference another behavior without needing a new type of element.
Eve

support@sparxsystems.com