"typeahead" search widget not displaying in employee center portal

Ken Rempe
Tera Expert

Hi all,  Given the new employee center header has a search bar (image below) and the older kb_view2 has a typeahead search widget on the page.   What we have observed was that if we use the older kb_view2 page with the employee center header, the KB page typeahead search widget on the KB page will not display.   We would like both search bars to be visible.  Is there a setting to  turn this on/off in the widget or header or is this coded somewhere? 

 

Thanks, Ken

 

Employee Center header with search bar

KenRempe_2-1667505516383.png

Employee Center Homepage (ec_dashboard) page.  The EC header search does not display on EC Homepage. 

KenRempe_1-1667505419585.png

older KB home page kb_view2. 

KenRempe_0-1667505360515.png

 

1 ACCEPTED SOLUTION

Hi Susan, thank you for the tidbit as we may use that to condense our homepage.  But we were looking at keeping the user experience of the old kb_view2 page and the typeahead search on it to search only the KB. i.e. we would have ended up with 2 search fields, one in the header with AI search and one on the page for KB search only.    Just now, we set up the EC portal with the AI's ESC Portal Default Search Application which does not have/use facets OOtB.   Once set up, the new facets on the new page behave close to the old user experience but using the header search field and "filtered" results.

Ken

View solution in original post

3 REPLIES 3

Ken Rempe
Tera Expert

We have the same issue with the older Catalog Categories (sc_category) page and typeahead widget also

Ken

Susan Britt
Mega Sage
Mega Sage

You can enable it (search bar) to appear on the EC homepage header too.  

  1. Navigate to Service Portal > Portals
  2. Open the correct EC record
  3. Open the EC's "Main Menu"
  4. Update the additional options, JSON to set "exclude_search_on_homepage" to false

SusanBritt_0-1667589611957.png

 

Hi Susan, thank you for the tidbit as we may use that to condense our homepage.  But we were looking at keeping the user experience of the old kb_view2 page and the typeahead search on it to search only the KB. i.e. we would have ended up with 2 search fields, one in the header with AI search and one on the page for KB search only.    Just now, we set up the EC portal with the AI's ESC Portal Default Search Application which does not have/use facets OOtB.   Once set up, the new facets on the new page behave close to the old user experience but using the header search field and "filtered" results.

Ken