BimlFlex supports management of changes in metadata over time. These changes are managed in Versions.

A version is part of a BimlFlex Customer, and a Customer can contain zero, one or more versions of the metadata.

Versions can be used to manage changes in metadata, for example to develop certain releases for internal use. A common use-case in a DevOps context is to configure a 'development' version where the teams can work on, and a 'build' version that is deployed in a DevOps process / pipeline.

Additional information on how versions are used in a concurrent development and DevOps context is available in the build and deployment sections.

In the BimlFlex Application, there are options to manage versions for a selected Customer. This can be done in the Administration section in the application, using the Version Editor.

You can switch between versions directly in the BimlFlex Toolbar, or in the Database Settings menu.

In addition to regular versioning as described in this section, BimlFlex internally also records history of changes within each version so that a full audit trail is always available.