Can't drop elements on a diagram

[MatthiasVDE]

I created a BPMN2.0::StartEvent through a script and add it to a pool. In my project browser the StartEvent is created within the pool, but when I try to drag it to my diagram, I got the following error message:

When dropping embedded elements (Ports, Object Nodes, etc.) on to a diagram, you must drop them on their correct owner. For embedded elements fixed to a parent edge, drop them near the desired edge

The activities that I created in the same way, are perfectly possible to drop onto the diagram in and outside the pool.

The StartEvent is only dropable on the edge of the pool, and then appears a blue startEvent right on the border/edge of the pool element. Very strange...

[Eve]

The BPMN events extend two different UML metaclasses, it sounds like your script has created one using the other one from what you normally use.

[MatthiasVDE]

The BPMN events extend two different UML metaclasses, it sounds like your script has created one using the other one from what you normally use.

I queried the element object type with an external database viewer, and it seems I created a 'Node' instead of an 'Event'. When I query the element with the model search, the event is an 'Event'.

         dim startEvent as EA.Element
      set startEvent = poolElement.Elements.AddNew("Start", "BPMN2.0::StartEvent")
      startEvent.Stereotype = "StartEvent"
      startEvent.Update()
      poolElement.Elements.Refresh()

[Geert Bellekens]

Mathias,

You might need to create the object type explicitly and then set the stereotype

Code: [Select]

dim startEvent as EA.Element
set startEvent = poolElement.Elements.AddNew("Start", "Event")
startEvent.StereotypeEx = "BPMN2.0::StartEvent"
startEvent.Update()
Geert

PS. The lines in your current to set the stereotype, and to Refresh() are probably not needed.

[MatthiasVDE]

Mathias,

You might need to create the object type explicitly and then set the stereotype

Code: [Select]

dim startEvent as EA.Element
set startEvent = poolElement.Elements.AddNew("Start", "Event")
startEvent.StereotypeEx = "BPMN2.0::StartEvent"
startEvent.Update()
Geert

PS. The lines in your current to set the stereotype, and to Refresh() are probably not needed.

Tanks Geert,

I always read that is was necessary to refresh the parent where you create the element, this can be a package or another element. But this is not necessary? even if you create (child) diagrams?
 

[qwerty]

The Refresh is only needed it you want to re-iterate the collection later on. In almost all cases you won't do that. So Refresh is a rather superfluous operation.

q.

[Geert Bellekens]

Not sure where you read that about the Refresh()

What it does is reload the EA.Collection from the database.
Not needed, unless you want to iterate the same collection after adding or removing items.

Geert

[MatthiasVDE]

Not sure where you read that about the Refresh()

What it does is reload the EA.Collection from the database.
Not needed, unless you want to iterate the same collection after adding or removing items.

Geert

In the example scripts:

      dim testElement as EA.Element
      set testElement = elements.AddNew( "Login to Website", "UseCase" )
      testElement.Stereotype = "testcase"
      testElement.Update()
      thePackage.Elements.Refresh()

But I thought that is was necessary to put the changes to the database or refresh the project browser

[qwerty]

Nope. Update is doing everything to get changes to the database (except where I remember some weirdness with operations/attributes and stereotypes).

q.

[MatthiasVDE]

Thanks Geert and Qwerty to make this clear.

[qwerty]

Just an update regarding the weirdness. Operation/Attribute seem to be ok (at least with a quick test). But it was a package which showed its Janus face. In order to apply a stereotype you first need to create (and Update) the package before you can access it's Element backside where the stereotype is stored. So you need a two-phase-commit (haha).

q.