Hierarchy/Structure in Model Explorer

[mblum]

We propose to have the possibility to use a hierarchy for organizing models in Model Explorer.

Currently we only have “repository” and “project”. We have the need for more structure. This could be done by adding some meta information to the model and use this for the representation in model explorer. It’s not a big issue but it would help us a lot.

Using this structure for administrative things like setting access rights for a set of projects could be a further enhancement.

[PatrickOllerton]

hi Michael,

Thanks for the idea. Can you give examples of the kind of structure/representations and meta information you have in mind?

thanks,

Patrick

[mblum]

Hi Patrick,

Kind regards,

Michael

[PatrickOllerton]

hi Michael,

So you would like additional container type nodes within the hierarchy?

Would they represent company/organizational entities such as business units, departments, programs, projects etc? If you can provide more details that would help.

I think in general this does make sense and would be useful, but I suspect it would have a large impact on existing functionality that uses the existing paths for Modeler items. We will evaluate potential use cases as well as impact to existing functionality, and keep it under consideration for a future release.

regards,

Patrick

[PatrickOllerton]

This request has been captured with the ID ART10-18613191 and will be considered for a future release

regards,

Patrick

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.