Symphony versions
What is a Symphony version?
Each Symphony version represents a point-in-time definition of the orchestration and is assigned to a specific state, such as Draft, Approved, or Archived.
The versioning system supports iterative development and controlled deployment. Only one draft and one approved version can exist at a time. Up to 50 Archived versions can be stored for historical reference or rollback.
Version actions are controlled by permission. Users with EO-MODELER role can create drafts, approve or activate versions, and delete versions or entire Symphonies.
Versions lifecycle
Each Symphony can have multiple versions; however there are limits to the number of versions per type. Version control ensures that changes to orchestration logic are traceable and managed in a controlled manner.
This table shows the available version types and their purpose:
| Version type | Description |
|---|---|
| Draft | An editable version under development. Only one draft can exist at a time. |
| Approved | The version used during execution. Only one approved version can exist at a time. |
| Archived | A read-only version retained for reference. Up to 50 archived versions are supported. |
You can view, edit, approve, or delete versions based on your assigned permissions and the current state of the version.
Example
You can edit or submit a draft for approval. An approved version can only be archived. Neither approved nor archived versions can be modified.
To restore an archived version, select the version and create a new draft from it. For more information, see Creating a draft Symphony from an existing version.