Flexible vs Rigid Workspace Metamodels
Workspace metamodels dictate what types of components you can create in a workspace. When you create a new workspace, you will see the models that you can choose to use for it:
You’ll notice that one of these workspaces has the “Rigid” badge, while the rest do not. Those without the “Rigid” badge are flexible metamodels – this means that there are no rules about component hierarchy, and you can create any component as a child of any other. It also means that you can have multiple levels of component hierarchy without having to explicitly define them.
Conversely, rigid workspaces have a strict component hierarchy that you must follow.
Rigid workspace example
When a metamodel is rigid, components must be created in the hierarchy shown in the metamodel preview. In this example, when the context is a Manual Task component, new components created must be its siblings since there is no component type under Manual task in the metamodel
Flexible workspace example
With the same metamodel as above, but converted to flexible, we can now create any component type as a child (or sibling) of any other type. You can also see in the screenshot below that there are multiple levels of components that are not shown in the metamodel preview:
Converting a Rigid Metamodel to a Flexible Metamodel
If you have an existing rigid metamodel that you would like to convert to flexible, you can do so.
Before doing so, understand that this action is irreversible. You can not convert a flexible metamodel back to a rigid one.