Dropdown and Multiselect: Add the ability to have non-selectable messages in dropdowns

[Sovia]

Is your feature request related to a problem or use case? Please describe. We are using a paging model for dropdown/multiselects, as there are cases where we are getting thousands of records in the dropdowns. Because of this, we are no longer returning all the possible options with the source call, and would like to give the users a message about how to get more data. Also, when a multiselect has a max selected number configured, we would like to give the users a heads up about that too.

Describe the solution you'd like A way to configure a message to be displayed at the bottom of the dropdown (i.e. "Refine search for more results"), and a message about "x selected (y maximum)" when using multiselect with a max selected configured.

Describe alternatives you've considered Tried to do this with just read only options, but these only update when the source function is called (so the mutliselect message didn't update). Also, if move selected is configured, it would be nice to have this message in that section.

Additional context Multiselect message like:

Message at the bottom of the dropdown:

Infor Landmark UI

[Sovia]

And make sure we can set the messages thru ng and angular.

[pwpatton]

@tmcconechy I think adding the "3 select (maximum 4)" in the selected section could be an option if maxSelection is enabled and just automatically added by EP. what do you think?

[pwpatton]

for the "refine search for more options" we'd like to be able to add with something like <li class=readonly>Refine search for more options<li>

[tmcconechy]

Something with the phrasing seems off a bit but we can figure out some labeling settings.

[pwpatton]

Label settings would be great. Maybe for the current and max selected labeling we could chat with the designers.

[jamie-norman]

I think we had talked about not saying anything about maximum allowed unless the user actually hit that number. Assuming the max allowed is a high number, how often would a user encounter that scenario? So, something as simple as "3 selected" should suffice. In the edge case we could say "Maximum reached; 50 selected. Refine search for more options," or "Refine search for more options. Maximum reached; 50 selected."

[pwpatton]

@jamie-norman for landmark a typical limit would be the number of occurs in an array field that stored the multiple selected values. This is unlikely to be more than 10 chars in most cases.

[vonnyw]

@tmcconechy do you have this scheduled in a sprint?

[tmcconechy]

Im not 100% sure this is something we would want to do as it adds complexity and possibilities for worse accessibility. So not scheduled yet. But i will add it to the next grooming session to discuss further options.. Perhaps we can come up with a more usable way of conveying this.

[tmcconechy]

Is the use case for both the 3 of 4 selected and the label on the bottom or do you just need one of these if so we could add.

1. An option for a label at the bottom of the selected area
2. An option to make any item non/selectable (not disabled and no checkbox)

[tmcconechy]

Tthe design/ ux team didn't really like the proposal as it adds accessibility and usability issues. So its not prioritized until we can find a design that seems good to go.

Especially the message on the bottom that you can never see. But adding the count someplace else and refining the All text might make sense.

So might have to bring this through design.