Home > Forum > User Voice > Visualizing historical versions of workflow models with a read-only designer and version comparison

Visualizing historical versions of workflow models with a read-only designer and version comparison
0

Hi,

when workflow models evolve over time, it becomes increasingly difficult to understand how a workflow model looked or behaved in earlier versions. Although version history exists, it is currently not easy to visualize or analyze previous workflow designs.

It would be very helpful if the workflow model history allowed users to navigate through past versions and view the corresponding workflow diagram exactly as it existed at that time.

Suggested features (for the new Web Studio):
1. Historical workflow visualization
From the workflow model history, users should be able to open and browse earlier versions of the workflow diagram. This would allow users to better understand how the process structure has changed over time.

2. Read-only workflow designer
Ideally, opening a historical version would launch a separate dialogue with a read-only version of the workflow designer.
In this mode, users could:
- see the full workflow diagram
- inspect steps and paths
- review configuration settings of elements
- analyze parameters and logic used in that version
This would allow devs to fully review previous configurations even after many subsequent changes have been made.

3. Visual comparison between versions
An additional feature would be the ability to compare two versions of a workflow model. The system could visually highlight differences, such as:
- added or removed steps
- modified paths
- configuration changes
This would make it much easier to identify exactly what changed between versions and to investigate specific workflow behavior.

Benefits:
- Better traceability and transparency of workflow changes
- Easier analysis and troubleshooting of past process behavior
- Improved documentation and governance for workflow development
- Faster understanding of changes during audits, reviews, or debugging
- Review and manual restore a previously correct configuration in cases where changes were accidentally saved or introduced unintended behavior, reducing troubleshooting time and minimizing the risk of workflow disruptions

This feature would significantly enhance the ability to manage and understand complex workflows that evolve over time.

Kind regards
Sébastien

Nobody has replied in this thread yet.