Create Versions of an Object

To guarantee a smooth roll-out of updates to any object without immediately affecting or even breaking fact models, consumption models, or perspectives, you can derive versions of objects.

The versions exist in parallel and are mostly independent from each other. The definition gets cloned once a new version is derived. As a consequence, changes in the new version have no impact on older versions. Older versions can still be adjusted, but likewise, changes to these are not automatically carried over to newer versions.

When several versions of an object exist, you are informed which properties are version-specific, which means that they apply only to the current version, e.g. the mapping of fields for the key definition, or if they are cross-version, which means that they are valid across all version, e.g. the title.

When you add an object to a model, a selection for the version is offered.

There is no activation process for versions which means that models are not auto-upgraded to a newly created version. Instead, you can decide whether and when a model adopts the new version.

Each version has its own life-cycle depicted by a status. This status in combination with the version's description indicates if a version is recommended for usage and signals the user to switch to another version. A wizard assists you in the migration process.