Customize New Tab Behavior Now Experience Workspace

[Mark Endsley]

Hi Everyone!

I'm creating a Now Experience Workspace for my custom app. When the user clicks the (+)

To customize this as far as I have I've edited the chrome_tab record in the sys_ux_page_property table where I found this nice little JSON file.

{
    "contextual":[
       "record"
    ],
    "newTabMenu":[
       {
          "label":{
             "translatable":true,
             "message":"New Request"
          },
          "routeInfo":{
             "route":"record",
             "fields":{
                "table":"x_g_jhu_transport_request",
                "sysId":"-1"
             },
             "multiInstField":"sysId"
          },
          "condition":{
             "tableDescription":{
                "table":"x_g_jhu_transport_request",
                "canCreate":true
             }
          }
       }
       
    ],
    "maxMainTabLimit":10,
    "maxTotalSubTabLimit":30
 }

I've been able to modify the routeInfo and condition objects to get it to open a record for my custom app instead of incidents and interactions. However what I truly want to do is open a record producer in the service portal. I know this can be done, because in the main Agent Workspace I've been able to have an interaction redirect users to the Service Portal via client script within the Workspace.

Are there any valid inputs to this JSON to achieve this? What are the valid inputs? Is this really how ServiceNow intends me to do this? Or am I missing something?

[JagjeetSingh]

Hi,

You can achieve it with some customization.

The route in JSON is the page route and parameters for the pages in experience.

You can create a page in your experience using UI builder. Here you can use Iframe component to display the record producer. To make it dynamic you can accept the sysId of record producer using page parameters. Page parameters are "fields" defined in JSON and "route" is basically page name.

Once you create that page then you can modify the JSON with page and parameters. You can get to the route from UI builder using Menu > Developer > Open Variant Collection.

Mark helpful/correct if it works for you.

[Mark Endsley]

Hi Jagjeet,

Thanks for the suggestion, I have created the page with the iFrame. However when I go to Menu > Developer > Open Variant Collection I arrive at a page like this

Where do I find the JSON needed to accomplish the route?

[Brad Tilton · Accepted solution]

The route should just be the name of your page, which I'm guessing is something like 'home' based on your screenshot. You can replace the record route in your original JSON with the route of your new page and clear out the fields property unless you're passing parameters to the page. It would be something like:

{
    "contextual":[
       "record"
    ],
    "newTabMenu":[
       {
          "label":{
             "translatable":true,
             "message":"New Request"
          },
          "routeInfo":{
             "route":"home",
             "fields":{},
             "multiInstField":"sysId"
          },
          "condition":{
             "tableDescription":{
                "table":"x_g_jhu_transport_request",
                "canCreate":true
             }
          }
       }
       
    ],
    "maxMainTabLimit":10,
    "maxTotalSubTabLimit":30
 }

If this format doesn't work you might try removing the fields and multiInstField properties entirely.

[Mark Endsley]

Yay this worked! The one thing I do notice is that the View Details button after submitting doesn't work. Any way of fixing this?