How additional parameters (such as 'sysparm_record_list', 'sysparm_query') gets added in the URL when clicking on a record form a table list. - Support and Troubleshooting

How additional parameters (such as 'sysparm_record_list', 'sysparm_query') gets added in the URL when clicking on a record form a table list. Issue  Let's assume an incident record is accessed via a list, sometimes we do see in the URL containing additional parameters such as "sysparm_record_list", "sysparm_query". This article explains how these get added to this URL. Release All releases.

Resolution So, this can be achieved via before query business rule on the desired table that gets triggered before the list loads.

The following simple example will explain the scenario:

Create a business rule with the following parameters: [Table] = [incident] [Advanced] = [true] Under the "When To Run" form section, have: [When] = [before] [Query] = [true] Under the "Advanced" form section, have: Script: (function executeRule(current, previous /*null when async*/) {

// Add your code here current.addQuery('caller_id', gs.getUserID());

})(current, previous); Now suppose, you're logged in as "Abel Tuter" and when you access incident list, only those incidents are loaded that has "Abel Tuter" as Caller. (As the above Business Rule is triggered - and of course ACLs are also in place accordingly) Now when you open the incident from the list by clicking it and if you inspect the URL, you will notice the following: .service-now.com/incident.do?sys_id=aaf68490db43db00f3e87ffdbf96193b&sysparm_record_target=incident&sysparm_record_row=1&sysparm_record_rows=6&sysparm_record_list=caller_id%3D %5EORDERBYDESCnumber" rel="nofollow">https:// .service-now.com/incident.do?sys_id=aaf68490db43db00f3e87ffdbf96193b&sysparm_record_target=incident&sysparm_record_row=1&sysparm_record_rows=6&sysparm_record_list=caller_id%3D %5EORDERBYDESCnumber If you notice, the above URL has an additional parameter: ...&sysparm_record_list=caller_id%3D ... This explains the reason behind the extra field parameters that get added to the URL.

Related Links Please do note that this article explains the reason behind this behavior and if implemented, will be considered customization and can impact performance or generate unexpected issues (based on custom logic defined).

This indeed will come out of the scope of ServiceNow Support and for further assistance, please either refer ServiceNow community and contact Professional Services.