run workflow without viewer
Hello all,
Is it possible to run a workflow by url without opening the viewer? I have a workflow that run several queries, returns info to a dataset, creates a pdf and emails it. There is no part of this that really requires the client to interact at all except that some of these commands (e.g., export map?) are client-side only?
Is this crazy?
Thanks,
Bobbi
0
-
This might be off topic, but based on that description, it sounds like something that a geoprocessing service might be able to do. Depending on your specific steps, Python could do all of the things you described.
Using a gp service would let you run the script independently or in a GE viewer if you connected it and wanted to run it on demand, too. I haven't done that before, but I seem to remember that you can run gp services via a workflow in a GE viewer.0 -
This is possible, if there are no client activities.
There are different options.
You can run the workflow from the REST endpoint.
We use an internally developed RunWorkflow executable to run a workflow without a site.
A geoprocessing service would I use mainly in the case of the need of the use of ArcGIS tools. Yes you can run them with a GeoProcessor activity.0 -
Thanks everyone.
The troublesome thing is that there are client activities. The workflow makes a map image.
For now, we are using curl/powershell that opens a browser on the sharepoint server (and closes it!). It's a little weird, but it works. Seems a little silly though and there MUST be something better!0 -
Hi Bobbi,
Maybe it would be possible to replace the Export Map activity with Extract Feature Map, Export Map Service, or Web Request? It would depend on how it's being used right now. Are there any other client-side activities that are holding you back?
-Amanda0 -
Hi Amanda,
Thanks for this! Sorry I didn't see it sooner. I'll begin looking into that ASAP!0 -
Oh wow, I really think this could work. Silly question - How do I initiate the workflow if not from a url (eg. https://blah.blah.bh...&runworkflow=whatever&argument=...)
What we did as a workaround was programatically open and close a browser on a server. That seems silly now, but it worked.0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
6 kommentarer