Community
Participate
Working Groups
The list of representation kinds available in the wizards may need to be filtered in some contexts. For example, having some diagrams present are not relevant from the root of the model, and may be more confusing for users than not having a choice there. In Neon, there was a trick (giving the wrong language to a diagram was sufficient to not have it in the list), but that was more a workaround than a real solution, and as models are describing now strong relationships, it is not possible to give a fake language. One possible solution I see is to add a boolean in the architecture model, to indicate if the representation kind should be filtered from wizard.
The list of representationkinds depends on the chosen architecture context. If the architecture context refers to some representationkinds that shouldn't be shown to the end user, then may be the context should not reference it. However, what I understand is that you want to add an additional filtering to the available representationkinds from an architecture context because you want in the wizard to have only one or two representationkinds to start with while during modeling, all reprensentationkinds available in the architecture context. Can you precise your use case and thoughts because I'm not sure it is an architecture framework matter but rather a wizard customization matter.
(In reply to Florian Noyrit from comment #1) > The list of representationkinds depends on the chosen architecture context. > If the architecture context refers to some representationkinds that > shouldn't be shown to the end user, then may be the context should not > reference it. Yes, but as Rémi indicates, there are some representation kinds that does not make sense to create directly at the root of the model during the time you create the model. In this specific case (see Bug 517485) there are two representation kinds for UML-RT that does not makes sense to create at the root of a model, i.e. the UML-RT capsule structure diagram and UML-RT state machine diagram, since they are always contained within a capsule respectively a state-machine (which in its turn always are contained within a capsule). So I assume that they still must be referenced by the context, since these diagrams are fundamental to the UML-RT architecture context. The only aspect is that they does not make sense to create at the root of the model during model creation. > > However, what I understand is that you want to add an additional filtering > to the available representationkinds from an architecture context because > you want in the wizard to have only one or two representationkinds to start > with while during modeling, all reprensentationkinds available in the > architecture context. > Can you precise your use case and thoughts because I'm not sure it is an > architecture framework matter but rather a wizard customization matter. I cannot really judge whether this is customization of the architecture framework, i.e. annotate that a representation kind that does not make sense to show in the new model wizard, or if it shall be considered a wizard customization, i.e. out of all the representation kinds defined for the selected architecture context do not show this set of representation kinds in the new model wizard. In the end, the result should be the same, i.e. they shall not be included in the list of representation kinds available for creation in the root of the created model in the new model wizard. See Bug 517485 for more information about the use case, and Bug 475805 for the original issue that was solved with the work around mentioned in Comment 0. Please also see Bug 514322 Comment 68 regarding more discussions on this topic and additional problems that arises if the diagrams would be possible to be created directly from the new model wizard.
