There are a couple of problems that you're maybe running into. I was able to get
HighlightEsriFeatureSet working through a
RunExternalCommand activity in Geocortex Workflow, but not
ZoomToEsriFeatureSet. Not sure why the zoom didn't do anything but zooming to the extent of a feature set is easily accomplished using an alternate approach (Get Feature Set Extent, then Zoom To Extent).
You may not be able to get
HighlightEsriFeatureSet working for a couple of reasons:
- you are executing
HighlightESRIFeatureSet (it's case sensitive)
- you are not supplying a valid Esri
FeatureSet to the command
The first is easy enough to verify. If the correct case still doesn't work, you can look at what you're supplying to the command. You mention a "SQL non-query" which I'm not sure is correct...since that doesn't give anything useful back (it's for updates, deletes, inserts - not queries). You may be using a
SQLQuery activity instead but that even will be problematic since it returns a data table from a standard database query. OK, you can convert a data table to an Esri feature set in Workflow...but that feature set almost certainly won't have any spatial information so nothing to zoom to or highlight.
Note that even if your data table from the SQL Query does have spatial information (i.e. you've selected a SQL Server Geometry or Geography column with the rest of your columns), converting this to a FeatureSet will not convert the spatial column into an Esri Geometry. Ultimately, if you have a DataTable from a SQL Query, you will not be able to zoom to it or highlight it on the map because a FeatureSet built from it will not have any spatial information.
I'd test your workflow out using the
QueryTask instead, against an ArcGIS layer, since that'll give you a proper Esri
FeatureSet that you can pass to the external command.
As for the
ZoomToFeatures, this uses a Geocortex
FeatureSet (with additional properties on it) that's pretty much useful only when actually in the client API, not from within Workflow. I'd just avoid that from workflow entirely.
Note that the commands in the API should all work when developing custom JS code in the viewer, but not all of them are available from workflow, depending on the parameter requirements of the command itself.