Useability of Glossary model elements

[timconinx]

Hello

Very interested, we started using the new feature of modelling glossary items, as explained in https://www.sparxsystems.com/enterprise_architect_user_guide/15.2/modeling/glossary_package_struct.html

But after a few tests and cases we noticed this feature completely separates the glossary-items-as-elements from the 'normal' glossary items:

• Glossary model items cannot be found in t_glossary, but should be found in t_object... this seems normal, but worse
• Glossary model items cannot be found (automation-wise) in Repository.Terms
• Finally, it's not possible to generate a report containing glossary model items... if a glossary category is not used outside model elements (so as classic elements), the category doesn't even 'exist' for the purpose of reporting

For us, as for now, this feature is pretty useless because we can't create definitions in different parts in the repository and at the same time integrate/export them as a complete glossary-list, even though such a list-view does exist in EA itself.

I'm not sure whether this is a bug or a feature...

Greetings
Tim Coninx
EA at De Lijn

[qwerty]

It's EA design. Rather than replacing something less useful with something more useful they leave both live side by side. With no relation. Because of reasons...

q.

[Geert Bellekens]

Hi Tim,

Yeah, too bad they didn't integrate both methods more, but there are workarounds.

With an SQL fragment you can combine both glossary sources and present them as one list (use a union between the select on t_object, and the select on t_glossary

Geert

[Modesto Vega]

I can see the advantages to the new method - i.e., it would be possible to have more than glossary in a repository. Do we know if Sparx is planning to deprecate the old method?

[qwerty]

They almost never deprecate anything. Just moving stuff from A to B (like when I want to clean up my room).

q.