Help with Offline Workflow 5 Queries?

Permanently deleted user

20. Mai 2018 21:57

(Already told to refer this question to this place from Geocortex Support Center)

 

Hi,

 

This questions concerns the Geocortex Mobile Application Framework (GMAF).

GMAF is supposedly able to support Workflow 5, but how do I get the Query Layer activity to work?

 

That is, I'm trying to Query a layer that's already been included and synched onto the offline viewer. I've heard that the URL to the offline layers are cached and GMAF will know to route to them upon request, but those URL's aren't working for me when I tried including them in Query Layer.

 

Any ideas?

0

• 

  Permanently deleted user

  28. Mai 2018 21:51

  Hi David,

   

  When I need to test that scenario, here's some of the things I confirm first:

  • That the layer is being stored and can be queried offline. A quick way to do that is to enable the layer for global search in Manager, take the viewer offline, and use global search to find the same feature or features that the workflow would return. Make sure your future offline tests are with features that you've confirmed are accessible this way.
  • That the query is valid. The easy test for that is to confirm that the workflow works correctly when it's not offline
  • That security isn't part of the issue. If you can open up security on the service you're querying, do so and test. If that's not an option, you could pick or set up another open layer and test on instead to see if it's a likely cause.
  • That the workflow is running. Make sure there's a Display Form, Log, Alert, or some other visual activity at the start of the workflow that lets you confirm it has started correctly when you run it
  • That the layer url you're querying in the workflow matches the one in your site correctly (eg, don't use a /MapServer url for one and the equivalent /FeatureServer url for the other)

   

  Try to reduce the complexity in your Query Layer activity as well for testing purposes. Make the Where property a simple one, and return * for the Output Fields. I've seen some tricky "gotchas" in the past like spaces between the comma-separated output fields breaking the query offline but not online.

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.