How Metamodel Conflicts Are Resolved During Library Updates
In this chapter, you will learn how ADOIT handles metamodel conflicts when updating a library that contains custom local changes.
When you update your library and the current library contains custom metamodel changes (applied on the Properties page), ADOIT merges these changes with the new version of the library. The table below outlines how conflicts are resolved:
Custom change | Product change | Resolution |
---|---|---|
Add a new attribute and assign to a chapter | Delete group | The group is retained |
Delete chapter | The chapter is retained | |
Delete preceding element | The new attribute is added at the last position in the container | |
Delete class | The class is deleted, and the attribute is unassigned | |
Rename attribute | Rename attribute | Custom name is retained |
Delete attribute | The attribute is retained | |
Change attribute infotext | Change attribute infotext | Custom infotext is retained |
Change attribute position | Change attribute position | Custom position is retained |
Delete preceding element | The attribute is moved to the last position in the container | |
Change position of preceding attribute | Custom attribute is moved after the newly positioned attribute | |
Rename chapter | Rename chapter | Custom chapter name is retained |
Delete chapter | The chapter is deleted | |
Change chapter position | Delete chapter | The chapter is deleted |
Delete preceding chapter | The chapter is moved to the last position | |
Change position of preceding chapter | Custom chapter is moved after the newly positioned chapter | |
Change group position | Delete preceding element | Group is moved to the last position in the chapter |
Change position of preceding element | Custom group position is retained | |
Rename group | Rename group | Custom group name is retained |
Delete group | The group is deleted | |
Change relation name | Change relation name | Custom relation name is retained |
Change relation position | Change relation position | Custom relation position is retained |
Delete preceding element | The relation is moved to the last position in the container | |
Change position of preceding element | Custom relation is moved after the newly positioned relation | |
Add enumeration value | Add enumeration value | Values are merged, with the custom value placed before the product value |
Remove enumeration value | The product change is retained | |
Rename enumeration value | Changes are merged; both custom and renamed product values are retained | |
Rename enumeration value | Rename enumeration value | Custom name is retained |
Change enumeration order | Keep or change enumeration order | Custom order is retained |
Change "Mandatory" setting | Change "Mandatory" setting | Custom value (Y/N) is retained |