Versioning and Publishing

Workflow versioning lets you publish stable releases of your workflows, track changes over time, and roll back to previous versions if needed.

Publishing a workflow

When your workflow is ready for use in dashboards, you publish it. Publishing creates a snapshot of the workflow's current state - its queries, parameters, and enrichments - and assigns a version number.

Each time you publish, the version number increments (version 1, version 2, etc.). Dashboards that reference the workflow automatically use the latest published version.

Why versioning matters

Versioning provides stability and traceability:

• Dashboards stay stable - dashboards reference published workflows, so in-progress edits to a workflow do not affect live dashboards until you publish again
• Change history - you can browse previous versions to see how a workflow evolved
• Safe iteration - you can edit and test a workflow without impacting anything until you choose to publish

Impact analysis

Before publishing a new version, Kogenta Connect shows you an impact analysis that identifies:

• Query changes - which queries were added, removed, or renamed
• Schema changes - whether the output columns of any query changed
• Affected dashboards - which dashboards reference the modified queries and may need attention

This helps you understand the downstream effects of your changes before committing to a new version.

Rolling back

If a published version introduces issues, you can roll back to a previous version. Rolling back:

1. Restores the workflow to the state of the selected previous version
2. Shows you which dashboards will be affected by the rollback
3. Optionally pauses affected dashboards during the transition

Use rollback as a safety net when a new version causes unexpected problems in your dashboards.

Version history

You can browse the full version history of a workflow to review past changes. Each version records the date it was published and the state of the workflow at that point.