Version control workflow

Overview

Applications and data sources in the Portal can have one of three statuses: Draft, Published, or Archived.
Each status defines how the version behaves and whether it is visible or used by other parts of the Portal (such as dashboards or reports).

Draft

A Draft is a version that has been modified and saved, but not yet made active across the Portal.

When an application or data source is edited and saved, its status automatically changes from Published to Draft.
The Draft version allows users to make and test changes safely, without impacting dashboards or reports currently used by end users.
Once the changes are validated, the user can publish the draft to make it the active version across the Portal.

Example: Data Source

When a data source is in Draft, connected applications continue to use the last Published version.
If you want the applications to use your latest modifications, you must publish the draft.
You cannot link a newly created data source (version 1) that is still in Draft to an application.

Example: Application

When an application is in Draft, only the last Published version is visible in the Portal menu and accessible to end users.
To make the latest changes (such as updated dashboards or reports) available, the user must publish the application.

Published

A Published version is the active and visible version used throughout the Portal.

It is the version referenced by dashboards, reports, and connected applications.
Only one version of an application or data source can be published at a time.

Archived

An Archived version is a previously published version that has been replaced by a newer one.

Archived versions are kept for reference and rollback purposes.
They can still be accessed by users if needed, for example by cloning them to create a new application or data source.
Archived versions are not used in dashboards or reports.

Status	Editable	Visible to End Users	Used in Dashboards/Reports	Can Be Cloned	Description
Draft	✅ Yes	❌ No	❌ No	✅ Yes	Work-in-progress version, not active yet.
Published	❌ No	✅ Yes	✅ Yes	✅ Yes	Active version used across the Portal.
Archived	❌ No	❌ No	❌ No	✅ Yes	Older version kept for reference or cloning.

Versioning

Each time an application or data source is updated and saved, a new version is automatically created.
Versions are identified by a sequential number (e.g., v1, v2, v3, etc.).

This versioning system allows users to track changes over time and, if needed, revert or reuse an earlier configuration.

Restoring an Archived Version

If you want to revive or reuse an archived version of an application or data source:

Open the BI Manager application.
Navigate to the specific application or data source you want to restore.
Open the Versions tab to view all available versions.
Locate the archived version you wish to use.
Click the “+” icon on the right-hand side to clone the archived version.

This action will create a new draft version based on the archived one, allowing you to modify and republish it as needed.