I've recently run into an issue exporting/importing workflows from one environment to another. When I import the jar file that I previously exported, after identifying the items to import from the conflict list, the process just hangs and never completes.
After doing some investigation it seems that the problem is that when the export is performed it is not complete. The org roles aren't included, even though they were identified, though I'm not sure why. It's actually two workflows. My main workflow calls another one, so it is pulled in when doing the export. In that called workflow I have a couple of approval nodes that use org role participants, which is why the org roles are dependencies in the export.
I've resorted to separating my workflow export from the other items that I have exported, as to isolate them. I get around the issue by changing the participant type then changing the participant back to org role after the import. This works, but is not optimal.
I have approval nodes in life cycle operations that also use org roles, but I don't have any issues exporting/importing those. The org roles show as dependencies during the export. On the import the org roles are identified as conflicts, so I have the option to not import them.
I'm not sure if the issue is the org roles themselves, workflows, dependent/called workflows, or even approval nodes. One of my co-works ran into a similar issue the other day as well, but these are the only two instances of this occurring in our environment. No patching of any kind has been done recently.
Does anyone have any ideas as to what the root issue might be?
Michael K. Craghead