- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2025 03:25 AM
According to this article, all you have to do is add the sys_id of the portal record to the glide.sp.portals.language_selector_enabled property.
https://www.servicenow.com/docs/bundle/yokohama-platform-user-interface/page/build/service-portal/ta...
However it doesn't seem to be enough. Some other articles mention you have to include the language picker widget to the header widget, but that requires cloning the widget. This is not included in the article above.
Which is a terrible practice for such a fundamental core widget.
Does anyone have any more insights to this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2025 03:53 AM
there is no OOB configuration for this, you will have to customize it
You will have to clone this widget "Employee Center Navigation" and then make changes to the newly created one
This link has approach for the same
Language picker on the Megamenu bar in Employee center Pro
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2025 01:23 AM - edited 03-17-2025 01:27 AM
Thank you Ankur 🙂
So in other words it's not supported, even though it says so in the documentation..
Cloning a critical widget like this just to get a language picker is not acceptable.
I'll create an Idea for it.
For now, the better approach is to create a custom widget and embed both the OOTB header widget as well as the language picker widget into it. To avoid cloning any widgets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2025 03:29 AM
Hi @Vegard S
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2025 01:24 AM
Hi @Vegard S
Did you check the link.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2025 03:53 AM
there is no OOB configuration for this, you will have to customize it
You will have to clone this widget "Employee Center Navigation" and then make changes to the newly created one
This link has approach for the same
Language picker on the Megamenu bar in Employee center Pro
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2025 01:23 AM - edited 03-17-2025 01:27 AM
Thank you Ankur 🙂
So in other words it's not supported, even though it says so in the documentation..
Cloning a critical widget like this just to get a language picker is not acceptable.
I'll create an Idea for it.
For now, the better approach is to create a custom widget and embed both the OOTB header widget as well as the language picker widget into it. To avoid cloning any widgets.