Author Topic: Something in UML that limits us to use a decision node after a callBehavior?  (Read 1149 times)

adeebulhafiz

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Hi,

I am trying model a simple activity diagram that invokes another activity in it. Once the invoked activity is completed, I want to take a decision on the returned ActivityParameter Value from it, by adding a decision node just after activity diagram.

However, I see if I simulate this activity, at the decision node the control cannot evaluate anything and get stuck at that point. The moment I add an atomic action between the decision node and call behavior everything seems to work fine. So I am wondering if I am missing any detail about CallBehavior?
Note: Since both atomic action and CallBehavior are subclass of Base class BasicAction, it seems they both should work fine. then, this might be a bug in the EA.

Best,
Syed Adeebul Hafiz

adeebulhafiz

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Update:  I sent the issue to Sparx Support, they have confirmed this as a bug.