First Workflow Doesn't Work

Permanently deleted user

02 Augusti 2018 15:20

Specs:

 

GE4.10

 

HTML5 2.11

 

After our update a couple weeks ago, we've noticed that the first workflow that's run when you load the site doesn't work properly. 

 

The general workflows that we tested are forms with an autocomplete box, then a Query Task, and then a selection and zoom to selection. However; for the first workflow run, it zooms to a random place on the map, although it does display the correct results in the results panel.

 

I'm not sure why it does this, but I think it has something to do with how after the workflow is run, it then loads the modules "Selection", "Editing", "Buffer", and "Reporting" and also shows a couple "Request Canceled" errors. 

 

On the second run, it loads the modules "Markup", "Native", and "Pushpins" and there are no errors.

 

Is there a way to fix this behaviour?

 

Thanks

0

• 

  Permanently deleted user

  02 Augusti 2018 15:25

  I also noticed a similar behaviour with "snapping" when doing measurements.

  0
• 

  Permanently deleted user

  14 September 2018 18:49

  Still no response on this. For anyone with the same issue, it's the "Select" Task in our Workflows that was causing the issue. In order to make things work properly on the first run, we now have a startup workflow that runs a random Select that Subtracts from the results list and then uses an external command to quickly switch back to layer view. Not pretty in any way, but solves the issue for the moment.

   

  Would look into it further if we weren't moving to a new server.

  0
• 

  Permanently deleted user

  09 November 2018 19:51

  Hi Odiri,

   

  This behavior and similar ones can happen with the viewer due to the asynchronous load behavior on viewer startup.  We load modules asynchronously so that the user can do something with the map without waiting for every last module to load and initialize.  However, that means a startup workflow can start running before the rest of the viewer has loaded.

   

  Your solution should be fine.  I have also avoided startup issues by looping on a Get Map Service Info activity, repeating it until it returns with a valid service layer.  From there, I know that the service has loaded in the viewer and I can select features on it.

   

  Regards,

   

  -Malcolm

  0

Du måste logga in om du vill lämna en kommentar.