While it is indeed a functioning versioning for the processes, the glossary is not auditable today. Once altered glossary terms can no longer be restored and changes will not be traced. This is especially due to the very rudimentary rights management for the Glossary a problem. Analogous to the processes should changes in the glossary will also be saved as a new revision and older versions should be accessible / restorable. ...more »
It would be convenient if the UML modeling would also be connected to the dictionary, so you can specify which (data) class in which process step addressed.
IS: when an icon is named with a run in the dictionary term, the dictionary entry is displayed, regardless of which category he comes.
TARGET: the user can define which category is addressed in naming a symbol. This must also be possible to sub-category but.
In the dictionary view is displayed by default, in which diagram a dictionary term is used. This list should be exported as an Excel spreadsheet while dictionary export.
It should be possible to assign the individual categories Glossary different permissions. Currently, only the entire glossary permissions are assigned.
The glossary should be able to define your own attributes of type URL / document (analogous to the own attributes for model elements).
(This idea was added as a feature request by a customer in the past)