Adding a scoped workspace to the Workspace menu in San Diego

[Michael Storgaa]

Hi everyone,

We are about to embark on the San Diego journey, but as we have several workspaces made in scoped applications already, I am planning on how to migrate them into the Next Experience UI.

When following the guide https://docs.servicenow.com/en-US/bundle/sandiego-platform-user-interface/page/administer/navigation-and-ui/task/add-workspace-unified-navigation.html I seem to get in trouble, because it will at all times add a /now/ to the URL, which is wrong when it comes to my scoped applications workspaces, they are all in a /x/xxxx/ prefixed URL. Also the Unified navigation setup only allows 2 levels, but my workspaces sits at 3 /x/xxxx/my-workspace.

How can we achieve this?

[Brad Tilton · Accepted solution]

Hi Michael,

Are these workspaces Agent (legacy) or Configurable workspaces (created with the newer version of UIB introduced in Quebec)? The scope doesn't matter when it comes to the unified navigation/next exp ui, but only configurable workspaces can be shown within the unified navigation so if these are the older agent workspaces you've created within an app that won't be possible.

[Chad Peterson]

Hi @Brad Tilton  

We are facing the same issue as original poster and we created our Workspace in Rome version of UIB . Any thoughts ? 

we've tried adjusting the path in both the UIB Experience settings for the workspace and the advanced settings page and doesn't seem to change anything.  The same behavior just keeps happening. 

Thanks!

Chad P.

[Brad Tilton]

It could still be a legacy agent workspace. Does the workspace exist in the (legacy agent workspace) sys_aw_master_config table or the (configurable experience) sys_ux_page_registry table?

[Chad Peterson]

Hey Brad, 

Thanks for the reply and suggestion,  it is indeed in the sys_ux_page_registry  table.  We created it in UIB in Rome release and have pushed it into a San Diego release test environment. However did not expect there to be any issue with it moving up in Release since the rest of our app associated with the workspace is operating as expected. 

[Chad Peterson]

FYI we have recreated the workspace in San Diego and this works now , despite it already existing in the correct table before. It looks like for the Workspaces link to work in the Workspaces dropdown that has to be the solution