[ https://issues.jboss.org/browse/WFCORE-2283?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-2283 at 3/23/17 3:57 PM: ------------------------------------------------------------------- Some random thoughts... One is if I'm looking for something and it isn't proposed, I'm going to be confused and, if it happens a lot, eventually mad. So how to mitigate that? * If they hit tab twice, show them all? * If the list is short, show them all? I think this is particularly relevant if the user has typed something before hitting tab. * Some kind of text output before the list that indicates the list is filtered? Another thing is there are other useful relationships besides whether an attribute is required. For example A -- required, alternative is B B -- required, alternative is A C -- required D -- not required, requires A If I added A to the operation, and then hit tab, I'd want to see D even though it's not required. I configured A which means I've expressed interest in the "A functionality" and therefore the related D should be shown. (I also wouldn't want to see B since it is illegal now.) The downside to all this stuff I mention here is there's no longer any obvious to the user rule to explain when stuff appears. So it could seem a bit mysterious. Having an easy way to get an unfiltered list (e.g. second tab) would help mitigate that. An easy way to get the unfiltered list is also a built-in workaround to the bugs that are likely to crop up with this. was (Author: brian.stansberry): Some random thoughts... One is if I'm looking for something and it isn't proposed, I'm going to be confused and, if it happens a lot, eventually mad. So how to mitigate that? * If they hit tab twice, show them all? * If the list is short, show them all? I think this is particularly relevant if the user has typed something before hitting tab. * Some kind of text output before the list that indicates the list is filtered? Another thing is there are other useful relationships besides whether an attribute is required. For example A -- required, alternate is B B -- required, alternate is A C -- required D -- not required, requires A If I added A to the operation, and then hit tab, I'd want to see D even though it's not required. I configured A which means I've expressed interest in the "A functionality" and therefore the related D should be shown. (I also wouldn't want to see B since it is illegal now.) The downside to all this stuff I mention here is there's no longer any obvious to the user rule to explain when stuff appears. So it could seem a bit mysterious. Having an easy way to get an unfiltered list (e.g. second tab) would help mitigate that. An easy way to get the unfiltered list is also a built-in workaround to the bugs that are likely to crop up with this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)