Route JS files missing?
Using the route activity in Workflow 5.17.0. When I attempt to run the workflow it throws errors - network throws 404s when attempting to get the RouteParameter.js and RouteTask.js files. Path it is trying to reach is in the essentials web directory in /Resources/scripts/esri/tasks
Jumping on the server to this location and these files do not exist. Am I missing something on setup or the Essentials install?
-
Hi Andrew,
It does sound like an issue with the installation of the ArcGIS API for JavaScript in your environment.
There are two different files called RouteTask.js that are loaded. The first is the activity (located at https://apps.geocortex.com/workflow/latest/dist/runtime/activities/arcgis/RouteTask.js) and the second is part of the ArcGIS API for JavaScript. Can you confirm that the first one loads?
Also, it sounds like you are running this in the Geocortex Viewer for HTML5. Is this correct? If not, which application are you using?
Finally, the version of the application would also be helpful.
0 -
Yes this is for an HTML5 viewer. We are on version 4.13.3 for Essentials and Viewer template.
I do not see any calls to ....workflow/latest/dist/runtime/activities/arcgis/RouteTask.js
Only the two that are missing and where the workflow fails.
We recently - a week or so ago - updated to 4.13.3. During the update we overwrote the current template with the new one. I did not try the routing task pre update so can't confirm if they were their prior. I do take backups of the essential iis folders prior to the update and looking into the backups the files are also missing there. We also installed the 4.13.3 update on a dev machine and files are missing there too.
0 -
Hi Andrew,
It may be that the workflow is using a portion of ESRI's api that just wasn't bundled with this version of the viewer. Normally we'd download this directly from ESRI and proceed, but if you have 'geocortexUseLocalEsriApi' set to true in your Index.html this would prevent that from occuring.
In this case you can download the relevant api from ESRI's developer website, find the missing files, and place them in the correct location in the viewer installation to get things working. The upcoming 4.14 release will also include these files by default.
0
Please sign in to leave a comment.
Comments
3 comments