This is something that can be added to a future release?
I see two major benefits to this:
- First with real version control, it becomes very easy to see what has changed between versions, especially if there is some kind of diff’ing tool include. Much like modern Git or Subversion clients provide.
- (and personally most important) Prevent forcing of users to upgrade to latest version of a step template/script module to update settings.
#2 above has really forced us to re-evaluate how modifications to step templates occur on our systems; not just from a development standpoint but an impact to our customers standpoint. Essentially we’ve moved to a model where we artificially version the step templates with a version embedded in the name:
- My template (v1.0)
- My Template (v1.1)
In this model step templates become immutable (except to fix bugs). New features are added as a new version of the template, there by not disturbing those who are using the older versions but making the new one available to those who want/need to use it.
Adding a version control system under the covers and allowing users to choose which versions of a template to use, during process setup, would go a long way to helping with this issue.