We would like to have the ability to add notes to an ARIS Cloud model that functions like a Post-It Note (sticky note). We would like this to function like a object but contain only descriptive information. Our approach is to create a custom symbol and add only description and links attributes. Has anyone tried to do this? We used the freeform text capability but that has significant limitations. Our team feels that creating an object that can be associated with existing objects would provide the functions we need. Unfortunately, the help information on how to add a custom symbol and object type is somewhat cryptic.
Has anyone attempted this before or developed a better way to add comments? We are aware of the comments and discussions capabilities off the portal interface but they are too general. We need to provide very specific annotation to specific objects (symbols) in the models. Basically, we need the ability to create a "Notes" relationship to objects.
If there is a better was to do this, please point us in the right direction. Thanks.
Dear Michael
Would the object type 'information carrier' with symbol 'document' help on?
An information carrier is a means to keep (store) information. It exists in the form of a card file, form, or computer file, for example.
To create a new symbol:
Open ARIS Cloud Administration --> Configuration --> Method --> Symbols
Select a symbol which should be base symbol of your new symbol and which is associated with the object of your choice
--> right mouse button on the symbol
--> new
--> derive symbol
Now you can maintain the name of the new symbol and select a new graphic for the symbol
Best regards
Christoph
Dear Michael,
a very common way to place "meta information" like "@Peter: please review this object, looks fishy to me (MZ)" is using the attribute type "Remark/Example" of any object (just a very common convention, if you prefer, make up your own attribute type). Like any other attribute you can place an occurrence of the attribute in the model graphic and it's part of the object the comment is intended for.
The charm of Christoph's solution with an extra object is that you could make them unreadable for some people using a different method filter. The risk is potential reuse of comment objects ("Fix this"). When someone inadvertently changes the text to "Fixed" it appears to be fixed in all occurrences.
In BPMN models you have the annotation object, of course, but I'm not particularly fond of them. They clutter the models with unstructured information instead of following clear conventions what is to be modelled.
Regards, M. Zschuckelt
