Skip to Main Content
HCL Connections 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.

Status Under Consideration
Created by Guest
Created on May 31, 2019

Change API utilized by ICEC PeopleFinder widget

The PeopleFinder widget is using a different API then the Advanced Search. PeopleFinder widget fails to return results if the term includes a "-" character or string followed by any character i.e. "intra-kummi". However, the API used for Advanced Search does not have this problem as it returns results for the same term.


Here is API used by PeopleFinder widget:






and here is API used by Advanced Search (entering term in Tag field and w/ Profiles checkbox selected):




As we can see, the PeopleFinder widget is using the Profiles Search API and the Advanced Search is using the Search API.

The Profiles Search API respects the dash character as a NOT operator which excludes results that contain anything after the dash character.

Customer requesting to fix the code within the PeopleFinder.js to utilize an API which will support typeahead search and not recognize the dash character as a NOT operator.

Not sure if the Search API would be best candidate as it is not recommended to be used to support a typeahead experience.

The Social People Finder seems like a good candidate as it is a form of typeahead search, but it returns JSON instead of Profiles Feed (xml enry).



  • Attach files
  • Guest
    Jan 27, 2021

    @Rene Schimmer: Shouldn't this idea be set to "Planned" or something, as we have built a solution for this issue in case CS0085159 > "fuzzy search option" (built in Connections Engagement Center