We converted our 4.0 workflow assembly to 2011. This is a on premise multi-tenant app with many workflows and plugins. I imported one of the orgs to 2011 including the 4.0 workflow assembly. I need to unregister it so I can register the
new assembly. To unregister the assembly, I have to delete all workflows that reference it. To delete the workflows, I have to cancel all instances of those workflows. I have these questions:
1. Is there a faster way to find the workflows referencing an assembly other than using the Show Dependencies for each workflow in the assembly? We have many workflows like this on many orgs. This will be time consuming!
2. Each workflow can have hundreds of instances in the system jobs in a waiting state. Anyone know of a way to cancel them and re-run after registering the new workflow assembly? Through sql possibly? I imagine exporting all the regardingids
before deleting might be a way to re-run them. Seems like this is a common migration problem that should be addressed with a utility.
3. Any workflow that references a user or business unit must be re-linked to the new guid since these change during the import. After fixing the workflows we have the same problem in 2 above with needing to re-run them on the same regardingids.
Thanks!
Tim
