add a version field in the workflow entity and create a new version in the database after the save button pressed
this will solve a big problem with data migration between development and production environments
new versions are not active by default
switching an activity to another version automatically removes the activity from the previous one
Thanks, @bookvik — this is definitely a useful feature. We have it on the roadmap but it definitely needs some careful design, so any further thoughts on how you’d like it to work (or other tools that do it particularly well) are welcome!
where can i see your roadmap?
I could see a huge use case for this and would love to have something like it. Hope it’s still something you guys plan to implement!