Different object name in view
Not planned
Currently, if one object is being used in multiple views, the object name will inherit from the property and thus it carries the same value across all views.
Sometimes, an object would be better represented in a name different from the one defined in the property but it cannot be done at the moment.
I hope we can amend the name of an object in a view so that we can retain all the relationship but presenting the name differently.
-
Official comment
Hello all,
While it is an interesting idea, an alias for objects feature is not planned.
Thanks,
Team ValueBlue
-
Would be very nice indeed!
0 -
Hello Ronnie, Thanks for your input, we'll get back to that soon.
0 -
Wilbert Goes : What is soon? :)
I'd like to have this wish implemented as well (both in Archimate and BPMN). Sometimes you want the full name for an actor / organisation / whatever, but sometimes you would want the acronym. Sometimes it just doesn't serve your stakeholders to have all kinds of technical names for objects (application layer mostly), and would like to use a more common name without creating a new object (which has more downsides than presenting your stakeholders with a lesser known name for an object).
0 -
How would you decide which name to show, what would set the switch for one of the available values?
Instead, what about integrating webservices / ontologies into BD so that you can use an external dictionary for synonyms and translations?
Link the dictionaries to functionality where a role defines which synonym you're presented with. This would be a role just for viewing purposes.
0 -
I didn't mean it to be that difficult.
Use case:
Just hoover or right-click any object on a view and give that object another name (=alias), while not changing anything in the object repository.Extra:
If you'd like, there could be a list (somewhere) that shows all given aliases of the object across (all) views.0 -
I'm not really sure different names for the same object is a good idea: calling the same things by the same name could prevent a lot of catastrophes - inside and outside companies!
On the other hand do I find the idea of a 'hovering information box' interesting. Not only gives it the possibility to show an alias for an object, but it could also be used for additional information (owner, cost, ...). However, the ability to select items in questionnaires that will be shown in such a 'hovering information box' is necessary.
2
Post is closed for comments.
Comments
7 comments