Search String Remains in Search Object

[#1]

Hi,

I have several search objects in my documents as they are a really useful way to group fields for selecting.  In the IE Plugin or desktop application you click on the search object, start typing and it does the normal gradually filtering your selection options based on what you type.  You then either press enter or select your choices and the search object returns to it's normal state with a little prompt (standard is "Search...").  All is well and you're free to make other selections. 

In AJAX however there's a problem.  You click, you type and you select ... but then what you have typed as a search remains in the search box.  This would be ok-ish if it made sense for the next search but when you have several grouped search object (for example: one holds property related fields, one client related fields) you need to prompt to return so that you know you're searching in the correct object.  If you do a screen refresh that sometimes works ... or if you click on another tab and then go back, that seems to do the job as well ... but that's not what you want to be doing in the middle of searching for answers in your data.

Has anyone else noticed this or heard of it being reported?

Thanks,

Emma

[ekech_infomotio]

Hi Emma,

I can't confirm this kind of behaviour - neither Chrome nor IE9 keep the search string.

(tested with two different apps in Chrome and IE, QV11Server)

regards,

Edgar

[#3]

Hi,

With the help of one of our IT ladies I've now tested with Chrome, IE8, IE9 and Safari and they all come out the same. 😞

I wonder perhaps if this may be due to our installation in some way (we're on V 10.00.815.6) but when I installed V11 desktop and looked at the webview this did exactly the same thing.  It's very frustrating as we'd far rather use the IT plug-in because of the better look and feel and functionality, but a client has been told they will be charged £1,800 by their computer outsourcing company to provide it and then £40 a time to download it (and the same again for any upgrades etc.). 

Very odd.  I will try and find some other examples and see if I can recreate in another environment.

Cheers,

Emma

[#4 · Accepted solution]

Hi,

Quick update ... can't remember the official bug number but this was due to our service release.  Now have V10 SR4 and it looks like it is fixed.

Cheers,

Emma