- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2021 07:29 AM
Hi,
Newbie question here, probably. I can't make the navigation sidebar appear, working on the UI Builder on a Workspace app shell. It should work with a simple configuration, reading here:
https://docs.servicenow.com/bundle/rome-application-development/page/administer/ui-builder/task/portal-navigation-menu-settings.html
And this is what i've done:
But the results are always like this, without left navigation sidebar:
What could be?
Solved! Go to Solution.
- Labels:
-
Now Experience UI Framework
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2022 07:09 AM
Hi Luca,
I have struggled with the same thing lately, and I think I may have found a solution/work-around.
The problem for me was that the UX Page Property "chrome_toolbar" was not configured correctly (as Ashley sniffed out too). For whatever reason, the property was set to type "string" for me. Please see my below checklist for a possible solution.
Solution:
- In the navigation filter, go to Experiences and open your experience.
- Under the related list "UX Page Properies", find the property called "chrome_toolbar".
- Make sure that it is Type "json" and formatted like the following example:
[ { "id":"home", "label":{ "message":"Home", "translatable":true }, "icon":"home-outline", "viewportInfo":{ }, "routeInfo":{ "route":"home" }, "group":"top", "badge":{ }, "presence":{ }, "availability":{ }, "order":100 }, { "id":"list", "label":{ "message":"List", "translatable":true }, "icon":"list-outline", "viewportInfo":{ }, "routeInfo":{ "route":"order-lists" }, "group":"top", "badge":{ }, "presence":{ }, "availability":{ }, "order":200 } ]
I hope this can be of some help!
Regards,
Simon

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2022 08:36 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2021 08:59 AM
I'm hoping someone else has a better answer, but I've never been able to get the Workspace sidebar when using the manual app shell method, only when spinning up a new Workspace via App Engine Studio.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2021 09:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2022 07:09 AM
Hi Luca,
I have struggled with the same thing lately, and I think I may have found a solution/work-around.
The problem for me was that the UX Page Property "chrome_toolbar" was not configured correctly (as Ashley sniffed out too). For whatever reason, the property was set to type "string" for me. Please see my below checklist for a possible solution.
Solution:
- In the navigation filter, go to Experiences and open your experience.
- Under the related list "UX Page Properies", find the property called "chrome_toolbar".
- Make sure that it is Type "json" and formatted like the following example:
[ { "id":"home", "label":{ "message":"Home", "translatable":true }, "icon":"home-outline", "viewportInfo":{ }, "routeInfo":{ "route":"home" }, "group":"top", "badge":{ }, "presence":{ }, "availability":{ }, "order":100 }, { "id":"list", "label":{ "message":"List", "translatable":true }, "icon":"list-outline", "viewportInfo":{ }, "routeInfo":{ "route":"order-lists" }, "group":"top", "badge":{ }, "presence":{ }, "availability":{ }, "order":200 } ]
I hope this can be of some help!
Regards,
Simon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2022 09:19 AM
Hi Simon,
Really thank you for your answer. The post above talking about the properties was mine, not Ashley's: this just to say that after that post i tried to change that property in a JSON, but probably i messed up something in the process, or there was another issue in that workspace, because it didn't work.
Now i tried again with a clean workspace and it worked. I'll mark the answer as correct.