Author Topic: own Toolbox: CallBehavior: nothing, ActivityInitial&Decision: something  (Read 2305 times)

Shegit Brahm

  • EA User
  • **
  • Posts: 98
  • Karma: +1/-0
    • View Profile
I created an UML Profile for individual stereotypes and a Toolbox based on that.
- create in ToolboxBase.eap, use in TboxUse.eap

need sync for full definitions from myProfile:
- constraints will be added only after syncing the element (User Guide already says so:

my problem with ActivityInitial:
- creating an element from original UML and adding stereotype myInit does nothing: neither tagged Values nor constraints added. And stereotype is visually wrong: instead of "<<myInit>> it shows <<myProfile::myInit>>
- syncing the stereotype from myToolbox: does nothing
- adding stereotype using drag'n'drop from myToolbox: impossible, creates always new node
- only solution so far: creating ActivityInitial from myToolbox, sync it, re-connecting & transferring everything from now-old node, delete now-old node.

my problem with Decision:
- creating element from original UML: adding stereotype myDec using properties page is impossible, myProfile is not offered for selection
- solution: drag'n'drop from myToolbox, adds everything or create from myToolbox

my problem with CallBehavior:
- defining toolbox needs "special skill": the metaclass is called "BehaviorCall", the toolbox attributes need full qualifier with "myProfileTB::myCallBehavior(UML::BehaviorCall)" (other stereotypes need only myProfileTB::myAction, guess it is because of CB vs BC)
- drag'n'drop from myToolbox on empty activity diagram does nothing
- drag'n'drop from myToolbox on default action does nothing
- creating action from default toolbox, changing kind to CallBehavior, drag'n'drop myCall from myToolbox: I get choice "apply myCall/ add myCall" - but nothing happens.
- only solution: create action from default, change kind to CB, select stereotype in properties

So all in all everywhere a different kind of workaround exists - but is there nothing to achieve a consistent work flow?

files for example:  profile definition as UML profile  entire stuff as MDG technology  toolbox definition as UML profile   eap where MDG is used eap where profiles got defined

Thanks, Shegit
« Last Edit: July 14, 2017, 12:41:34 am by Shegit Brahm »

Shegit Brahm

  • EA User
  • **
  • Posts: 98
  • Karma: +1/-0
    • View Profile
Could solve CallBehavior that it "does something useful".

Extend metaclass "action" and set the generated attribute "kind" to the initial value "CallBehavior".
Define in myToolbox this stereotype in short form (myProfileTB::myCallbehavior) - that results in an action.

If I drag'n'drop now from myToolbox into an activity diagram, I will get an action of kind CallBehavior.

Only disadvantage: If I create an clean UML action and add in properties page the stereotype "myCallBehavior" - the kind on subpage "Advanced" will stay unchanged, but anything else looks like it should.

Works too with ExpansionRegion to set mode on iterative, e.g..
Stays only the annoying Initial and Final that resist any setting of stereotype, they still need creation from myToolbox.
« Last Edit: July 26, 2017, 11:24:04 pm by Shegit Brahm »