Classic UI, Polaris and URL generation

davidhomer
Tera Contributor

Hello,

 

We're working on integration with ServiceNow and want our software to generate a URL to a ServiceNow configuration item.

 

We're looking to use the following format to generate the URL - is this standard across the different releases of ServiceNow and safe to use?

https://<baseURL>/nav_to.do?uri=<table name>.do?sys_id=<identifier>

 

Also I notice that this resolves to a URL like this

https://instance.service-now.com/now/nav/ui/classic/params/target/cmdb_ci_win_server.do%3Fsys_id%3D6a054cabxxxxxxxxxxxx


What does the URL have "classic" in the name? We are using a Tokyo developer instance, and glide.ui.polaris.experience is set to true. Have ServiceNow just upgraded the UI but not the configuration item screens?

 

Thanks for everyone's help so far this forum is very useful!

 

Thanks,

 

Dave

1 ACCEPTED SOLUTION

Sebastian L
Mega Sage

Hi Dave,

Yes, ServiceNow has upgraded the user interface from San Diego - but I don't see many customers that have switched, The property you refer to controls if they have the new UI or the old one. Since you are using /nav_to.do?uri=<table name>.do?sys_id=<identifier> in your URL, it will convert it to a view within polaris, if the property is set to true. It will however not do that, if the instance is not on Polaris.  So you should be fine as it should automatically redirect, but if you can provide the correct link up-front it would of course be best 🙂 

 

If your customers are using workspaces, then your URL should maybe reflect that as well. e.g: https://instancename.service-now.com/now/cmdb/record/cmdb_ci_computer/{sys_id}


Best regards,
Sebastian Laursen

View solution in original post

2 REPLIES 2

Sebastian L
Mega Sage

Hi Dave,

Yes, ServiceNow has upgraded the user interface from San Diego - but I don't see many customers that have switched, The property you refer to controls if they have the new UI or the old one. Since you are using /nav_to.do?uri=<table name>.do?sys_id=<identifier> in your URL, it will convert it to a view within polaris, if the property is set to true. It will however not do that, if the instance is not on Polaris.  So you should be fine as it should automatically redirect, but if you can provide the correct link up-front it would of course be best 🙂 

 

If your customers are using workspaces, then your URL should maybe reflect that as well. e.g: https://instancename.service-now.com/now/cmdb/record/cmdb_ci_computer/{sys_id}


Best regards,
Sebastian Laursen

OK interesting that second URL shows a different user interface, we'll have to determine which people would want to see linked from our system. Thanks!