Seeing as this is a popular free widget in the community, I thought some might benefit from this info since the issues described with page routing are related to Paris and newer.
A ServiceNow KB that explains the issue - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0867532
An updated version of the client controller/client script in the widget that will address this issue. The only catch is if you use the option it will place the sys_id of the page instead of the display value in the url. Less pretty, but functional.
function($rootScope, $location) {
/* widget controller */
var c = this;
$rootScope.$on('data_table.click', function(event,obj) {
console.log(obj);
var link = {};
link.sys_id = obj.sys_id;
link.table = obj.table;
link.id = c.data.page;
//$location.search(link);
//location.search = '?id=form' + '&table=' + link.table + '&sys_id=' + link.sys_id;
if (c.options.page) {
var page = c.options.page;
}
if (!c.options.page) {
var page = "form";
}
location.search = '?id=' + page + '&table=' + link.table + '&sys_id=' + link.sys_id;
})
}
