Workflows not opening in Workflow Designer 2.20.0.605
Anyone else seeing a problem opening old workflows with the recently released workflow desiginer (2.20.0.605)?
On my dev machine I can't open any of my previous workflows. It gives me an error that the workflow is 'could not be loaded or is not a valid workflow'.
On our production machine, it is working, so I am not clear what the difference is.
Marc
-
As a follow-up on this, I uninstalled WD and reinstalled via both the Essentials installer and the standalone versions. Still the same problem. I could create a new workflow and save it, but then I get the same error when trying to open. Very odd. I can at least use the production server install for now, but it would be nice to have it work locally.
Marc
0 -
We have the same problem, workflows from previous versions do not open in the new workflow designer. Is there some settings or update work we should be doing? this is a serious problem???
J
0 -
Hi Jeff and Marc, would it be possible for you to upload one of those workflows to the forum? Thanks, -Alejandro 0 -
Hi Ryan, Thanks for the workflow, I was able to open it in Workflow Designer 2.20. Please, check the following: in Windows Explorer, right click on the workflow and in the "general" tab, check if the file is being blocked by windows (in the bottom of the tab you'll find a message saying something like "This file came from another computer and might be blocked to help protect this computer". If that's the case, click the "Unblock" button and try opening the file again. -Alejandro 0 -
Alejandro,
Thanks for the info. I don't see any message like that at the bottom of the General tab in the properties of the .xaml file. Any other ideas?
Ryan
0 -
I think we have it working...
Jeff and I were tring to open a file on the server by using the server path (\\myServer\Geocortex\REST Elements\Sites\Resources\Workflows), as opposed to the C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\.... path
Using the latter path, the files are all able to open.
0 -
Thanks for the information Ryan. We've reviewed this and the issue is that the version of the Microsoft Workflow Foundation used in Essentials 4 won't allow you by default to open a XAML file from an "untrusted" source (like a network share for example or downloaded from the "Internet" zone). This was different in previous versions of the MS Workflow Foundation, so that's why older versions of designer work.
This will happen to any workflow, regardless of the version it was created on. We will work on changing this for the next version of Essentials.
-Alejandro
0 -
Since our windows server only allows 2 users to login at a time, we have been using the stand alone version of workflow designer to allow more users to build workflows. With the "trust" feature in play at 4.0, the stand-alone versions of the designer are pretty useless now. Is there a way to create a "trusted" location so we can use the stand alone version of designer and access centralized xzml files over the network to edit.
J
0 -
Folks--
I think i have a work around for the problem.
I did some searching on the web and came up with this idea. Under your C:/user/username there are several "trusted" library folders, documents, downloads, etc. if copy the geocortex ~/resources/workflows directory to the documents area, it will work, you can open and edit the workflow.So,
basically the user would edit the copy in their documents directory, then upload it in the essentials manager workflow wizard and overwrite the version in the ~resources/workflow directory, instead of editing the file in the ~resources/workflow directory directly.
Can you suggest a more elegant solution or can you see any inherent problems with this solution.
Jeff0 -
that still involves an upload or copy....
why is this not an issue with report designer?
0
Please sign in to leave a comment.
Comments
10 comments