Route Activity
Hello all,
I am not a developer; and I want to develop a workflow that finds the shortest route between two points selected by the user. I started with DisplayCaptureGeometry activity (The user uses to select points), its result is geometry variable (geometry1) then I want to stick this result to a Route Task activity, which needs a “route parameter” variable, how can I translate the “geometry1” variable to a route parameter variable? Simply from ESRI.ArcGIS.Client.Tasks.RouteParameters to ESRI.ArcGIS.Client.Geometry.Geometry
Any help is appreciated.
Hani
-
Dear Michael,
Thank you very much for the help,
I copied the code to notepad and saved it as xaml file then tried to open it with Geocortex Workflow designer and the attached error appeared, I plugged it in the site, but when starting the site the button that runs it is greyed out. Shown below with screenshots.
Please consider that I am not a developer, and not able to customize the code with my urls. Could you please elaborate more how can I make it run?
Thank you again!
1- opening xaml in Workflow Designer
/customer/servlet/servlet.FileDownload?file=00P6000000elzlIEAQ
2- Adding the xmal file to the site's workflows
/customer/servlet/servlet.FileDownload?file=00P6000000em1U6EAI
3- Adding the tool as a button
/customer/servlet/servlet.FileDownload?file=00P6000000eluK9EAI
4- The button is greyed out
/customer/servlet/servlet.FileDownload?file=00P6000000eluKYEAY
0 -
Hello Hani,
I do not know why you are getting the error that you are.
Regardless I have temproraily uploaded the xaml file whcih can be downloaded here:
http://expirebox.com/download/bd4f867ecc73a7291edb80ae5cffc33b.html
The link is valid for the next 48 hours.
Make sure that the workflow can open in Workflow Designer, if it cant then I suspect it wont run in the site. When you do import the workflow in Essentials Manager, you have to input one parameter, that is the URL to your routing server. It should end in something like "/NAServer/Route"
Hope this works for you!
0 -
Hi Michael and Hani
another thing to clarify between the two of you is what version of Geocortex that workflow was written for. If, Hani, it is for a newer version than you have you will have issues.
The fact that you cannot open it in Workflow Designer without issues is a pretty bad sign as far as this goes.
Regards
Ralph
0 -
Hey Hani,
Ralph raised a good point. I copied the text I posted into notepad, saved it as a .xaml file and opened up the Workflow in Workflow Designer in 4.1.0 and it opened fine. Any version of Workflow Disgner 4.1.0 or above should be able to open it.
-Michael
0 -
Dear Michael,
Thank you very much for your time, I downloaded the .xaml file, opened it using Workflow Designer, added it to workflows, and plugged my route service url parameter, but when clicking the tool nothing appears; I just click two places on the network and get an error (shown below with screenshots). By the way, what was the problem wtih the previous .xaml file?
1- Defining my route url in the workflow.
/customer/servlet/servlet.FileDownload?file=00P6000000em23CEAQ
2- Running the workflow, and choosing two stops.
/customer/servlet/servlet.FileDownload?file=00P6000000elzo2EAA
3- The error appears.
/customer/servlet/servlet.FileDownload?file=00P6000000eltkfEAA
0 -
Dear Ralph,
Thank's a lot for the advice, I am using GE 4.1.4 and Michael's new .xaml file can be opened properly in Workflow designer.
0 -
Hello Hani
If you use a program called Fiddler, it captures web traffic so you can see requests and responses. If you are running Fiddler while running the workflow, you should see the request go out to your Routing server along with tha parameters it is sending. You might be able to see in there why it is failing.
Also, you could try going to your routing server through arcgis manager and manually putting in the arguments (the format of these can be easily grabbed from Fiddler) to see if you can get a valid response.
I hope everything works out for you!
0 -
Thanks Michael, your input is very helpful, I'll install Fiddler, and track the source of the problem.
0 -
Heloo, for me helps settig params in this case:
routeParams.OutputLines="esriNAOutputLineTrueShapeWithMeasure"
routeParams.UseHierarchy= False
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
9 kommentarer