Compare active versions of flows (processes)
When comparing flows (processes) between environments, Gearset appears to try to match on flow version number, even though different environments are likely to have different numbers. It seems like it would probably be more helpful if the comparisons were between just the active versions.
Rob Alexander
shared this idea
This is no longer applicable now that v44 of the API is released:
https://docs.gearset.com/en/articles/2439855-changes-to-flows-in-v44-of-the-metadata-api
-
[Deleted User]
commented
not applicable to me anymore; we have long since moved past V43
-
Bob Hatcher commented
As a corollary to this it would be nice to be able to filter on active ProcessDefinitions only.
-
Pat Vachon
commented
Right now we have to copy the XML of each version into a separate online tool to do diffing on all Flows and Process Builders. Pain in the @#$%^!
-
[Deleted User]
commented
100% agree with this; flow versions can easily get out of whack with feature sandboxes created at different times and the compare against the integration environment typically throws 'differences' when there is no real difference except in version number