Hi,
Does any have idea, how search will work in dropdown. I can see, there is only an option to show or hide a search box. I think it's a default behaviour.
Sometimes it works and sometimes it don't work. I'm posting one weird result from search.
Please let me know, if anyone had any idea.
Discussion posts and replies are publicly visible
If the dropdown has more data in list e.g 12 or more options then search box comes up by default. If you have less options like 4-5 then search box doesnt shows.
my question is not about search box showing up, I wanted to understand how the search is working. I did type 'monkey' in the search box. Expectation is no results found, but I got one record, not sure, how it filtered?
Dropdown search uses substring matching to filter choices based on text entered. It searches anywhere in the choice labels, not just the beginning.
If possible, can you explain how the search is performed in the picture, to understand me better.
Interesting for me!!Appian algorithm appears to be doing a scattered character matching where it finds all the letters of your search term distributed throughout the text, regardless of order.All six letters (m-o-n-k-e-y) exist somewhere within that sentence.
m from "timeout" or anywhere it's available.
o from "timeout" or anywhere it's available.
n from "backend" or anywhere it's available.
k from "backend (the 'k' sound in 'ck')" or anywhere it's available.
e from "user" or anywhere it's available.
y from "they"Try changing y from "they" of this it will not appear.I would recommend you to open Support Case with Appian with this behavior to understand more.
Maybe that "monkey" is hiding somewhere ... without seeing your full code, hard to say.
Good one!
Rahul Gundu Have you tried doing this?
Got reply from Appian Support Case.
So for a search term like "monkey" the entry matches due to the characters showing up in that order in the entry found (matching characters highlighted in bold):
(Improve complet) Upon timeout, send partial results to the backend and then ask the user if they want to move to the next one
This isn't the expected result, right? So is this an issue with the search algorithm mentioned by the support team, or is this behavior actually expected?Also my assumption regarding scattered character matching is correct?