Maintaining version numbers across environments for a workflow definition
We never build workflows directly in the production environment, but rather in a test environment first and after testing then export our workflows to the production environment. Since versioning for the workflow definition is based on the number of times the workflow is published in a environment it is difficult to know if my test environment workflow or the production one is the latest version. It would be advantageous if a versioning number is tracked inside the workflow definition itself.
I think I have a similar idea. Essentially, that the version number of the running workflow should be available as a common property such that it could be included in the details of things like tasks and email notifications e.g. in the footer of a notification.
This would be really useful to in situations where workflows might run for a long time and a user might receive a task or notification that appears to contain a bug or old information for something which has been marked as fixed or updated. It would be good to be able to say easily that, for example, your notification was generated by a workflow which is still running under v6.0 and the issue you report was fixed in v7.0.
I don't believe there is any webservice call we can make to get this info but happy to be corrected.