The scenario metamodel merge workflow is a part of the Ardoq Scenarios feature. The purpose of the metamodel merge section is to align the metamodels between the scenario and the mainline. Having compatible metamodels is a prerequisite to be able to merge the data, including the components, references, and tags. This part of the workflow is documented in the scenario data merge.

Steps in the Metamodel Section

This workflow will take you through a series of steps for the metamodel structure, component types, reference types, and fields where there have been changes. 💫

ardoq metamodel section

Metamodel Structure

The very first step handles the case where a metamodel is changed from being rigid to flexible.

Component Types

Delete component types

This step lets you accept deletions into your scenario. If the component type to be deleted is in use, it will not be possible to delete. To do so, you first have to exit the merge workflow and change the components using that type to use a different type.

Ardoq delete component types

Create component types

Component types that are created are required to be accepted before continuing. This is to ensure that new components have the necessary types available.

Ardoq create component types

Update component types

For properties that have changed on component types, either on the source or the target, you can choose which version to keep. You'll also see the original value that the property had when the scenario was created or the last time you merged.

Ardoq update component types

If only the source or the target has changed, the status is green, and the changed value is preselected. If both source and target have changed, the status is red, and there is no preselection. You can override the preselection by either selecting everything from the mainline or from the scenario or cherry-pick the changes you want.

Reference Types

Delete reference types

This step lets you accept the deletion of reference types into your scenario. Similar to deleted component types, the reference type needs to be unused to be possible to delete.

Ardoq delete reference types

Create reference types

Reference types that are created are required to be accepted before continuing. This is to ensure that new references have the necessary types available.

Ardoq create reference types

Update reference types

For properties that have changed on reference types, either on the source or the target, you can choose which version to keep. You'll also see the original value that the property had when the scenario was created or the last time you merged.

Ardoq update reference types

If only the source or the target has changed, the status is green, and the changed value is preselected. If both source and target have changed, the status is red, and there is no preselection. You can override the preselection by either selecting everything from the mainline or from the scenario, or cherrypick the changes you want.

Fields

Delete fields

When merging fields, you can choose which fields deleted in the mainline you would like to keep, or also delete in your scenario.

Ardoq delete fields

If you have made changes to a field value on a component or reference in your scenario, and this field is deleted in your mainline, there will be a warning message informing you that you will lose data if you choose to accept the deletion.

Create fields

Fields that are created in the mainline can be created in your scenario when merging changes to the metamodel.

Ardoq create fields

Update fields

Changes to fields, such as list options, default values, and where the field applies can be merged into your scenario.

Ardoq update fields

Scenario Data Merge Workflow

When the metamodels in the scenario and the mainline are compatible, you can continue merging the data - changes to references, components, and tags. Here's where you can learn how the scenario data merge workflow works.


If you still have questions about Metamodels, browse our Knowledge Base or reach out to us using the in-app chat. 💬

Did this answer your question?