Pega out of the box control Auto-Complete gives you the ability to type in few characters and based on the characters it gives you back the results based on the Source provided which can be Data page, RD etc.
Auto-Complete as a control does not validate the value selected or typed in manually is valid according to the source list of values.
so as a scenario, I have a region dropdown coming from Data page which has following values:
with this configured in Auto-Complete, I can type in LosAngeles and submit the form and validation would not trigger for the Auto-Complete value. I have to explicitly do validation in post activity for every Auto-Complete I have on my screen.
The autocomplete feature is not designed this way. View it more as a smart predictive text box, rather than a drop down. If you need to restrict your users to a specific set of options, then maybe a dropdown will better suit your requirements.
Else, if an autocomplete is what you desire, you will indeed need to fire your own validation against the list.
The way the Auto-Complete look and feel is more of a dropdown rather than a text box(at least as user my vote is for that not sure about how many percentage of other folks will concur to me). The only difference between a Auto complete( up - down arrow image) and dropdown(down arrow image) is image by which I click and open dropdown and populate auto complete.
As a user I would feel it as a advanced dropdown rather than advanced text box because if it is a predictive text box(something like Google search) then it should not have that up-down arrow image to make the look and feel deceptive.
With my explanation, should I wait to hear something to be done from Pega or validating all auto complete in post activity is my option ?
If you had a dropdown with >5000 options, then no, I would say a dropdown is not a good choice of control.
At this point, if you wish to stay with an autocomplete, then you have two valid options.
1) Create your own validations
2) We can generate an enhancement request to extend or add a new feature to autocomplete to meet your business requirements. Just be aware, enhancement requests are evaluated to be considered in a future release, and there are no guarantees on time frames for their evaluation or their inclusion into the product.
This problem is not just to Akash. This is for every Pega developer when they choose Autocomplete over Dropdown due to the large list. Pega only suggest to use AutoComplete over Dropdown when the lis has >100 values but it could lead into wrong data. I feel like Pega should provide an option to restrict the user entry on on change event. I hope Pega will come up some kind of fix for this.
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread
We have also sent you a private message opening up a communication channel in case you have any further questions.