Relationship matrix with multiple types

[Geert Bellekens]

I'm doing an excercise where we want to map all activities in a BPMN process to an application component.
To facility this I wrote a script that creates a Matrix Specification artifact containing the
- source package: the package containing my process
- source type: "Activity"
- target pacakge: the package containing all application components
- target type: "ApplicationComponent"

If now a user doubleclicks this artifact, they get the matrix with the correct selections.

So far so good; But we have a requirement to also trace all sending and receiving events to an application component. (a message could be sent or received by a different component than the activities in this process)

So now I need both "IntermediateEvent" as "Activity" as source types.
I tried setting source type to "Activity,IntermediateEvent", but that didn't work.

When the matrix is opened, I can select a model search to be the source. I can write a model search that return the Activities and Intermediat Events I need, but unfortunately I don't seem to be able to store this selection in a matrix specification. These only allow source/target Packages, not searches.

I also haven't found any way to open and manipulate the relationship matrix view.

So now the only option I see is to create two matrix specifications; one for the Activities, and one for the Intermediate Events.

Anyone know of a more elegant solution?

Geert

[BobM]

Like this?




I have to start with BPMN should be application agnostic, but to each his own interpretation of models.

With above Profile saved you have all elements in the source (including, but not limited to intermediate events and activities), with an alias and check (use alias if available it is easier to determine which is which (intermediate events somehow don't support aliases in the matrix view and will show the element name), most other  elements without an alias will become blank.
It's not clean, but it is a workaround.

[Geert Bellekens]

Yes, I know about the <All> filter, but that leaves way too much elements that aren't supposed to be linked to components (pools, lanes, messages, data objects, gateways, end nodes,...)

In that case I prefer two separate matrix specifications, one for Activities, and one for Intermediate Events
It would be so nice if I could simply select multiple types, or if the matrix specification supported specifying a search.

Geert