HCL Connections | Product Ideas Portal

Welcome to the HCL Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events, please visit our HCL Connections page.

Search - Enable Wildcards as first character in a query (e.g. *nections, ?onnections)

Users tend to search with a wild card as first character. Unfortunately this leads afaik into no results with the current search setup / engines. As a work around a search like "a*[remaining search term] OR b*[remaining search term] [...] OR z*[remaining search term]" - maybe there are better ways ;-) - can at least close this gap, but are not practical for a user.
For sure these kind of searches are a performance pain for the underling search engine/server. Still this is a user demand. Please help to get this implemented into both on-prem and cloud for search.

  • Guest
  • Nov 20 2018
  • Future Consideration
  • Attach files
  • Admin
    Adam Gartenberg commented
    27 Oct, 2021 06:37pm

    We agree this would make for a better user experience. While this seems like it should be a simple update, it would actually require a major update to our underlying search technology, which we do not have in the roadmap at this point.

  • Guest commented
    27 Oct, 2021 07:06am

    Almost 3 years have passed - Any Update on this?

    Our users constantly complain about not being able to search with wildcards as first character.

  • Guest commented
    3 Sep, 2019 12:25pm

    I think using wildcards also as first characters of a search string correspond to the current state of technology.