Good Way to Compare Published Workflows in Different Environments

[jmiskey]

Is there a good way to compare the published workflows in different environments to identify the differences?

I have a published workflow in one of my sub-environments that is newer than the one in our Prod environment.  I would like to know what the differences are.

Hoping there is a semi-easy way to do this and see the differences.

Thanks

[Jace Benson]

I think the only way is to look at the specific workflow version that is published and compare either the diagram, or the activities.  What are you trying to do with this comparison?

[jmiskey]

The thing is, it could be a single word in an Advanced Script (or something like that that has changed).  So it could be difficult to spot without doing some very cumbersome checking between the two.

Basically, I need to make some changes to the Workflow in Prod, but have to test them first in the sub-environments.  If I try working off of the current Published Workflow in the sub-environment, I risk promoting some other change I am unaware of.

Maybe one other option is to delete the Published Workflow version from the sub-environment, export the Published one from the Prod environment, and then import it into the sub-environment so the different environments are then "synched-up".

Does that make sense?  Does it seem like that should work?

[Jace Benson]

So workflows are versioned, and they should match version to version from Prod to whatever environment.  If you skip a version, you should get errors on the code promotion that there's some problem with the workflow.  I don't think there's an easy way to compare each line of code in each activity.  One way you could abstract this in the future is use script includes for any code in workflow, then the differences should be apparent.

[jmiskey]

I am not sure I follow your comment regarding abstracts and script includes.   

Let's try going about this a different way:

If I want to update the Workflow version in the sub-environment so that it is running the same version as in the Prod environment, what is the best way to do that?  I tried looking at the Create/Update times in the past few versions, but they do not match.  Note that all workflow changes to Prod and promoted through Update Sets from the sub-environments.  So the current Published Version in Prod will NEVER be newer than the Published versions in the sub-environments.