BPMN items are bigger when dragged from the solution browser than when new

[P Robert]

Hi,

I'm using Sparx 15 (latest version) and creating a new BPMN 2.0 business process diagram.
When I create a new item (dragged from the toolbox directly into a diagram) the item shape has a default size but if I drag an existing item from the item browser into the same diagram it shows bigger than originally set when created from the toolbox. That is super annoying as I'm constantly resizing stuff to make it constant... What's the issue?
Example:
https://drive.google.com/file/d/1ZnfrBjjx-0CGfgRH1lLjAM9oSUWjDZHA/view?usp=sharing

[qwerty]

Makes me wonder how you manage to get the same element on the diagram twice. EA prohibits that.

I did the same (deleting the existing start from the diagram first). Yes, it resizes differently (and as oval too). But then again: the start event should be used only once in a single diagram. You create it from the toolbox and you're done. So why drag it from the browser and to where?

q.

[P Robert]

Who said it was the same element twice? Look at the screenshot I provided: it is two different elements, created in two different ways (one from the toolbox and another previously existing one dragged from the project browser). Fact is I'm not duplicating items if they already exist in a previous diagram, I reuse them (which is the right way to use building blocks). And yes in some diagram I may have more than one "input" therefore more than one start event, may it be a good or bad BPMN practice is off topic (and so what if it helps me illustrate my message well...). But regardless of the type of objects, it does the same for gateways, end event and most of the BPMN shapes and it is annoying.

[qwerty]

Well then. This is a user forum. You better send a bug report instead. Good luck with that.

q.

[Geert Bellekens]

Fact is I'm not duplicating items if they already exist in a previous diagram, I reuse them (which is the right way to use building blocks).

I don't think that is how BPMN is supposed to be used.
Each node in a BPMN diagram is owned by only the business process that is represented by the diagram.
Re-using existing nodes on different diagrams is not done. Nothing you see on a BPMN diagram is supposed to be used on any other diagram.

In BPMN reuse is done using the calledActivityRef (which is conceptually the same as CallBehavior Actions in UML Activity Diagram)

Geert

[Eve]

Each node in a BPMN diagram is owned by only the business process that is represented by the diagram.
Re-using existing nodes on different diagrams is not done. Nothing you see on a BPMN diagram is supposed to be used on any other diagram.

Exactly right. You will sometimes see the elements expanded to show their contents though.

In BPMN reuse is done using the calledActivityRef (which is conceptually the same as CallBehavior Actions in UML Activity Diagram)

In the case of events, the re-use varies based on the eventDefinition. Signal you re-use a common Signal by setting signalRef and so on. You will then be able to see all places where that signal is sent or received using the traceability window.

EA won't stop you from using elements like that though, but you will have trouble if you try to export the resulting model to BPMN XML.

Having said that... I am able to reproduce the behavior that the two methods of adding the element produce a different size. I note that when dropping from the toolbox it briefly shows at the larger size and then shrinks. If I 'autosize' any BPMN events they all go to the larger size.

I would say it is an issue, but not a very high priority one.

[P Robert]

Thanks for your answers.
1) Qwerty suggested that I should open a bug, am I not in the bugs and issues forum? Is there another way to "submit a bug"?
Yes indeed it is not a high priority bug (I mean the soft still works) it just makes my diagram look less professional am I'm the picky kind

2) Eve: you said if you "autosize" it regulates the size (to the bigger one which is fine for me as long as they all have the same size): can you explain how you do that? Pretty sure it is less of a pain than manually sizing each

Thanks

[qwerty]

The link is below in the page in the support section.

q.

[Geert Bellekens]

2) Eve: you said if you "autosize" it regulates the size (to the bigger one which is fine for me as long as they all have the same size): can you explain how you do that? Pretty sure it is less of a pain than manually sizing each
Thanks

Alt-Z autosizes an element to the smallest size possible/allowed.

Geert

[Paolo F Cantoni]

2) Eve: you said if you "autosize" it regulates the size (to the bigger one which is fine for me as long as they all have the same size): can you explain how you do that? Pretty sure it is less of a pain than manually sizing each
Thanks

Alt-Z autosizes an element to the smallest size possible/allowed.

Geert

I'm having issues with it recently.  Doesn't always work for me.  Haven't figured out why yet.

Is it working OK for others?

Paolo

[Eve]

Anything with Alt gets eaten by the ribbon.

It's still in the context menu for multiple selection and in the ribbon under Layout > Diagram > Select. You could also change the keyboard accelerator.

[Paolo F Cantoni]

Anything with Alt gets eaten by the ribbon.

It's still in the context menu for multiple selections and in the ribbon under Layout > Diagram > Select. You could also change the keyboard accelerator.

Ahh...  That explains a lot!

OK, I'll change the accelerator.  It's too useful!

BTW, is that machine-specific, repository-specific or what?

Paolo

[Eve]

Custom keyboard accelerators are saved as part of the user profile on your machine.

[Geert Bellekens]

I found that pressing Alt-Z twice usually works.

Geert