Access the attributes of a results list row in a workflow with {{context}}

Zack Robison

July 23, 2018 17:35

As Ian alluded to last October in an answer to the thread "Select a row from table view and execute custom workflow? (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&criteria=ALLQUESTIONS&id=906f2000000fxgNAAQ) " the 2.10 update to GVH should allow for access to a feature in each record of the Results List/Table.  Indeed, as seen in teh configuration for the "Feature" and "Results List and Results Table Set Element" context menus, activities such as "Cut" and "Run Report" are taking a context token parameter, but I haven't yet figured out how to take advantage of that myself.

 

I've tried to consume the incoming "{{context}}" token from the FeatureSetResultsFeatureActions view (i.e. the new button next to a record in the results lists/tables) as an Esri featureSet, featureSet[], Graphic, Graphic[], and Geocortex Client Feature[] and Feature as well, as indicated in the docs for ListReports (https://docs.geocortex.com/essentials/gvh/2.10/commands-help/#/commands/Reporting/ListReports) and CutFeatureInteractive (https://docs.geocortex.com/essentials/gvh/2.10/commands-help/#/commands/Other/CutFeatureInteractive) , which are themselves consuming the context from this menu config, but have not been able to get my workflow to see these objects in any way.  What am I missing here?  How do I feature into workflow??

0

• 

  Permanently deleted user

  October 31, 2018 20:16

  Hi Zack,

   

  Unfortunately, the documentation for the {{context}} parameter is quite limited:

   

  https://docs.geocortex.com/workflow/latest/help/Default.htm#wf5/help/run-workflows-in-gvh.htm

   

  It is much easier to use them in Workflow 5 than in Workflow 4.  I beleive this is because the viewer tries to determine if the {{context}} argument is an appropriate parameter to pass to the command, and the commands that run an Essentials Workflow do not know how to represent it.

   

  Please use the feedback icon in the upper-right of the documentation to suggest places where it can be improved - that feedback will go straight to the technical writers.

   

  Regards,

   

  -Malcolm

  0
• 

  Zack Robison

  October 31, 2018 20:25

  I didn't even notice that feedback button was there, thanks Malcolm! 

   

  You're absolutely right about workflow 5 being the way to go, though the reason in this case ended up being slightly different.  I ended up using WF5 to get that context which, aparently, avoids json serialization errors which were getting in the way between the viewer and the workflow (thank you Amanda and Ian for figuring that out for me).  I could then take the properties that I needed and pass them to the Essentials Workflow that I'd written. 

  0

Please sign in to leave a comment.