Why does my ResultsTable not populate on the first run of a workflow, but work correctly every time after that?

Sean McClurkan

February 02, 2017 20:52

Essentials 4.6.3 HTML5 2.7.2

 

I have several workflows that SelectFeatures into a named collection, then I do a ShowResultsTable to display the named collection.  The first time the workflow executes in a browser session, the queries run, the selections occur, but the ResultsTable opens up empty, or only showing the first set of SelectedFeatures.  

 

If I execute the same workflow immediately, the same process occurs except now the ResultsTable pops open before I have executed the ShowResultsTable command and sits open and empty until the SelectFeatures are done, whereupon it displays all the results correctly.

 

Any subsequent workflow executing any QueryTask will open the ResultsTable empty even if there is not a DisplayResultsTable command in the workflow.  Additonally, now that a workflow has opened the ResultsTable once, all subsequent executions of any workflow using the ResultsTable will get the correct results displayed.

 

What is preventing the first execution of any workflow from showing the named collection correctly, and why -WHY - does the ResultsTable always open for every QueryTask under the sun after that?

0

• 

  Amanda Frech

  April 08, 2017 00:17

  Hi Sean, 

   

  It seems that the different results view commands were designed assuming that when a user picks one, they're going to want that decision to stick until they change it back.  The current description for the ShowResultsTable, "Displays the list of features in the given FeatureSetCollection in a tabular view" is thus misleading.  It's more that it opens the features and then switches to the tabular view mode.

   

  You should see similar results if you run a workflow that selects some features, and then you manually use the context menu to switch from list to table view.  When you run the workflow again (or another one that selects features), your preference for the table view will be remembered.

   

  I've made a request, GVH-14706, to make the API documentation clearer.  If you'd like to see a command or activity for the behaviour you're looking for, I would recommend posting to the Ideas section.  Since some of our users might rely on the command working the way that it does, I think it's more likely that we would want to add a new command than change the existing one.

   

  For your first question about the table not populating the first time, I can't be certain without seeing the workflow.  When I did a quick test on my end I didn't see that behaviour, but it might just be that I don't have enough features selected or enough collections in memory.  It might help to try switching to the results table before opening the selection (eg. SwitchToTabularResultsView then ShowResultsTable, or SwitchToTabularResultsView then SelectFeatures).

   

  I hope that helps,

   

  Amanda

  0

Please sign in to leave a comment.