Hoppa till huvudinnehållet

How to change the behaviour of the global search results list.

Stefanie Wenker

We have a need to have multiple layers turned on in our global search. But now when you search and a results pops up in two layers, the results list automatically goes to the layer that only has 1 result. To see the results in other layers, you have to click on the back-arrow to see the results per layer. This is not user-friendly.

 

The desired behaviour is to stay on the results pane that shows how many results exist in each layer for which there are results and have the user click on the layer they want to see the detailed results for. Is this something we can configure?

0

Kommentarer

6 kommentarer

Datum Röster
  • Pairin Mason

    Hi Stefanie,

     

    Which Geocortex Web version are you currently using and seeing the issue?

    Is it possible to share your app/layout and screen recording of reproducible steps?

     

    Cheers,

    Pairin

    0
  • Cam Barnard

    @Stefanie Wenker? ... I'm guessing you are describing the Geocortex Viewer for HTML5 as part of Geocortex Essentials. The 'auto go to a single result' behavior is something that exists there but doesn't exist in Geocortex Web.

    0
  • Stefanie Wenker

    Hi,

     

    Yes that is correct, I am using the Geocortex Viewer for HTML 5. I continued looking at this issue on Friday - is my only option to change automaticDrillInDelay to 0 in the config file? (in the ResultsModule). I guess in that case the user would always have to choose the layer that they want to see the results in?

     

    Or is there another option? We are not ready to move to Geocortex Web yet.

    0
  • Permanently deleted user

    I have the same question. It jumps automatically into the address locater result and takes a few clicks to get back to the Search Results list so they can choose the parcel result.

    0
  • Deep Bhari

    We are having similar issues and use GCX Viewer for HTML5. Hope it gets resolved in the upcoming releases.

    0
  • Deep Bhari

    This mostly solved our issue, I decreased the default value from 300 to 10 miliseconds for automaticDrillInDelay:

     

     "description": "@language-common-query-results",

          "configuration": {

           "automaticDrillInDelay": 10

          }

    Thanks,

    0

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

Hittade du inte vad du sökte?

Nytt inlägg