As a Solution builder
I want the ability to set a model master as the model found when no model is defined for the element type
So That i can more easily implement a default model master for any and all elements in the repository that don't need or warrant a specific handcrafted model master.
Benefits one of the benefits of MooD is the ability to easily extend and expand on the meta model, however if each new type created needs it's own custom model master or navigation turned off whenever included in a web application, the associated effort and maintenance resulting from expanding the meta model becomes signifiant over time.
The current no model found functionality retains the primary id of the element in the navbar, so there's currently a workaround for this where the user is simply redirected to a model master for the element, but it would really be preferable to not have to solve this kind of thing with scripting. Moreover one could also go through each element type and simply apply the model master, but again it's much easier to keep track of which element types have specific defined model masters if everything else can just use a default model master.
Acceptance Criteria when setting the No Model Found option in Web -> Settings -> Pages the solution builder is able to choose model masters as well as models.
Customer / Originator Solution builder
Please sign in to leave a comment.