Support Central Data Model in DNG

Currently a central Data Model is maintained and it needs to be individually deployed to every single stream. This operation has many limitations, which leads to a high effort for updating the data model of each existing stream.

Problems:

Component Template does not contain all data model entities (Link Validity)

Component Properties do not contain all data model entities (Folder Structure, Views, Preferred Module Content) -> critical

Import Component Properties in Doors Next does not Import Artifact Templates-> critical

On Import Component Properties change of Multivalued Picklist to Single values Picklist not possible -> blocker

Changing Attribute Type not possible. -> critical

Not possible to Update all components in all streams with a component template configuration. > critical

Discrepancy between Template and Properties: When updating a stream via Import Component properties, some of the data model entities are not updated ( e.g.: workflow for new artifact types), Component Template on the other hand can only be applied once.

On Import Component Properties, Deleted Attributes are not taken over. Also removal of attributes from types is not taken over.

When changing a Doors Next data model version X to version X+1 by removing an attribute and reintroducing the attribute with a different type (e.g. old type: enumeration, new type string), the data model version X+1 cannot be imported to other components containing the data model version X anymore.
The enhancement request is: If a data model in Doors Next changes, the import of a new version of a data model should always be possible to components containing the old data model version. The update of the data model shall include also: folder structure, artifact templates (with preferred views).