Flexible vs Rigid Workspace Models
You’ll notice that one of these workspaces has the “Rigid” badge, while the rest do not. Those without the “Rigid” badge are flexible models – 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 model is rigid, components must be created in the hierarchy shown in the model preview. In this example, when context in a Manual Task component, new components created must be its siblings since there is no component type under Manual task in the model
Flexible workspace example
With the same model 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 model preview:
Converting a Rigid Model to a Flexible Model
If you have an existing rigid model 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 model back to rigid.