Universal Type Without Model Definition
As a solution builder,
I want to create universal types without a model,
So that is not possible to create a model for elements of these types,
The benefits are that elements of specific types where model masters are used exclusively, cannot have a model, thereby avoiding the issue of creating unwanted models that mess up the model master functionality. Usually, 80-90% of the universal types we create in our solutions will never need a model, and we regularly have to remove unwanted models that interfere with model masters.
The benefits are also that we will no longer have to waste time figuring out why a model master is not displaying an element correctly, when the cause is that the element has a model by mistake.
The acceptance criteria is, in Manage Repository, when creating a new universal type, it will not have a model definition by default. Instead there will be the option to later add a model definition. It should also be possible to remove a model definition from a universal type.
Priority is normal.
This request is related to, but not the same as https://supportportal.moodinternational.com/hc/en-us/community/posts/360000894400-Query-Functionality-to-Find-Elements-With-Without-Models
-
Yes please! I thought this was an existing Story but I can't find it.
This often happens - a chain of stories all leading back to something like this. (Queries starting from primary elements --> Where has model condition --> Remove models from primary element aliases)
Also there's this one (another way of solving the same problem)
14856 Conditional Model Masters: Choose the priority of existing models on elements.
Matt.
-
I have not encountered it before.
You are right; we have been circling around this issue for a while without really grabbing it by the horns. I think it will be a good progression in MooD's development from Process/Object types to Universal types to Model-less Universal types (or rather Universal types with an optional model).
Could there be a performance improvement by not having all the unused model definitions...
-Peter
-
Hi Peter, data tables can be written to, they just default to having readonly permissions applied. I appreciate they are still not as easy as 'normal' elements to work with.
Soren, we were considering making models a thing that you can add to a type, just like a field. This would also allow you to have multiple model types associated with a given alias (or none).
Matt
Please sign in to leave a comment.
Comments
7 comments