Multiselection attributes

We also have similar examples like Veronika. e.g. clients, protection needs, etc. These cases could of course be modeled. But the effort involved in modeling is very high compared to the maintenance of an attribute by the person responsible. This also applies to exchanges with other systems in which such information is represented via a multiple attribute.

We can only support the use case of Veronika. We also have processes that are not used in all countries and currently have to make do with a "battery" of 35 Boolean attributes. In addition, the creation of a new attribute and the adaptation of numerous workflows and reports are required for each additional country. Otherwise, only the next country would be entered into one attribute as a text or, even better, ARIS artifact.

I'll illustrate it with an example; I want to:

Have one attribute for validity - so instead of creating n true/false/not set attributes (for each country individually), I want to have 1 attribute for which I can store n values, each of which can contain true/false/not set.

I would like to be able to do assessments on this attribute on object & model level via query/report without querying n attributes and be able to display/evaluate it in dashboards just as easily.

Thus, it should be available at model level and also at object level.

It would also be cool if it were possible to fill it with a macro.

Today:

n Attributes

Germany True/False/not set

Switzerland True/False/not set

Austria True/False/not set

...

Multiselect

1 attribute

Validity

- Germany True/False/not set

- Switzerland True/False/ not set

- Austria True/False/ not set

I think there could be almost limitless use cases? Being able to assign multiple trade desks, asset classes, products, fund types etc to either a model or object. Being able to capture multiple project names where different change projects are affecting the same processes. Being able to capture multiple locations to indicate where the process is applicable. Capturing where a data sub domain may belong (at the moment) in multiple domains.

The following use cases:

1) In connection with ARISELAD1-I-264

ARIS artifacts (groups, models, objects) can be assigned to other elements mapped in ARIS so that they can be evaluated and maintained. For example, departments (general organizational units), sustainability structure elements, document objects from ARIS, risks, etc., which cannot be represented in a meaningful way by attachment or as occurence copy

2) Information objectives: Who should be informed, e.g. in the event of changes

3) Responsibilities: Which user, which user group is allowed to release the process in a workflow

4) Affected departments

Call for use cases.

Dear community,

for what cases do you want to use multi-attribute values?

Regards,
Philip

ARISELAD1-I-84 Creating a Combined Data Type Attribute

should not be mixed up with multiselection, s. comment