I’d like to share two stories and what I think might resolve them.
We have a few Losant applications that share the same code base, both on Workflows/Experiences etc.
We have them split for security/seperation at the moment, but are looking long term into a multi-tenant approach.
As we develop new features and pages, we come up to a release window where we manually move the newly developed/modified Workflows and experience resources from Development into the Production applications.
Sometimes for these nested workflows, you are only 75% certain something change, maybe in some four level deep loop on a function node. You’re not sure, so you copy it anyway, and then have to go fix all the GUID references to Data Tables, and callouts to other Workflows.
It would be nice if there was a hash visible of the workflow file itself, not dependent on the Application it is loaded into, but that I could compare and know that if I see hash: adx776542 , and I know I have a workflow with hash: ffg453444, then I know for sure there is a difference that I need to swap out the whole thing.
If I had two workflows with the same hash, then I would know that internally they are the same.
Right now you can only kind of surmise that based on the Last Modified Date, but even then they wont be exactly the same, as it gets updated when imported into an application.
Secondly, when a Workflow is saved, the option could be set at the Application level, to prompt for a Commit message. That way a developer could enter his/her notes about what was changed.
This may be annoying for rapid development, so potentially turned off at some level.