Topics

1

General Board / Can we display name of the arrow next to source rather than destination?

« on: March 31, 2020, 05:38:04 am »

Hi,

I'm writing BPMN process daigrams and wondering if we can determine where the name of an arrow is displayed on the diagram? Currently it is next to the destination end of the arrow (on sequence flow arrows) and was serching for a way to show them next to the source end of the arrow instead? This would make it more readable when using gateway elements since the "yes" and "no" text would be next to the gateway element rather than at the end of potentially long sequence flow arrows...

suggestion: it should be that way by default when writing BPMN diagrams...

Thanks

2

Bugs and Issues / BPMN items are bigger when dragged from the solution browser than when new

« on: March 31, 2020, 02:55:22 am »

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

3

Automation Interface, Add-Ins and Tools / "Clean" way to get MDG technology info

« on: June 12, 2019, 01:28:52 am »

Hi,

I'm trying to create a connector using an MDG Technology stereotype (Archimate in my case).
The stereotype defined in the MDG technology "maps" to a base connector type in the MDG tech XML file.

Example:
<Stereotype notes="" name="ArchiMate_UsedBy" hideicon="0" borderwidth="-1" bordercolor="-1" fontcolor="-1" bgcolor="-1" metatype="UsedBy">
  [...]
  -<AppliesTo>
    -<Apply type="Dependency">
      [...]
    </Apply>
  </AppliesTo>
</Stereotype>

So (if I'm getting this right) when creating a connector with the "Archimate_UsedBy" stereotype EA will create a "Dependency" type connector.
I want to be able to set the right "base type" (Dependency) when creating a new connector based on the "stereotype" (Archimate_UsedBy).

Problem is, this mapping does seem to exist only in the MDG XML file, so it cannot be accessed (or at least I haven't figured out how) from the automation interface... Unless I parse the XML myself, which seems to be troublesome (would need first to figure out where the XML is, then parse it manually )

Before I jump into this I was wondering if there's a cleaner way to achieve getting access to the MDG technology info from the automation interface?

Thanks

Phil

4

General Board / Archimate elements used multiple times

« on: June 12, 2013, 05:29:17 am »

Hi,

I'm trying to put together a Archimate 2.0 diagram in which I would like to have multiple instances of the same element.

A good example is a data element: I have multiple systems in my whole IT landscape which use the part data object. So for each system, I would like to display that the software either realizes (create) or uses (consume a local copy of the data) the part data object.
However, when I try to drag the Parts data object more than once on my diagram, I'm getting an error message saying:

 "The diagram already contains an instance of the element you are trying to paste. Currently, only one instance is supported, so you cannot paste the element here."

I don't want to have the element only once and linking all systems to it for 2 reasons:
1) it will quickly become unreadable
2) I want to be able to show the difference between a system which gets a local copy of the data and system which accesses the part data directly into another system

I've seen that I can create local copies of an linked element which allows me to have it multiple times, but they really are distinct element afterward... This does pollute the model a lot and prevents traceability afterward (I wouldn't be able to do an analysis of what systems are using part data because I would then need to check each copy of the part data object to see what it is relating to, so this becomes a nightmare to manage).

Any idea how we can (or if we can) change that setting to allow multiple instances of the element in the same diagram?