"Last Run by" value for Servicenow ReportsIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> "Last Run by" value for ServiceNow reports We have an OOB module which is called "Report statistics" and this capture the statistics of the report and the last run time as well. But it do not capture "Last Run by". https://docs.servicenow.com/csh?topicname=report-statistics.html&version=latest#report-statistics There is a system table which collects this data and you can implement a custom solution to get this into a custom table of your choice for your reporting requirements. **** The steps outlined is a workaround to get this information and this should be tested on your SUB PROD instances and you should also weigh in the performance impact while implementing this on PROD as every instance is different and there is no way to benchmark this. Procedure The information you are looking for is captured on sysevent table which is a system table. This table is not available/recommended for reporting and there is an OOB auto rotation enabled on this every 7 days. https://docs.servicenow.com/csh?topicname=events.html&version=latest So this table will only have last 7 days of data. To get the information you are looking for, you have to create a customised script on a sysevent table to capture the required information to a custom table of your choice and use that table for reporting. if you use a realtime Business Rule, it can create a lot of load on the instance as this is the one of the most busiest/frequently accessed system table of the instance platform. You can plan for a scheduled custom script which pulls the required information once a day during your NON business hours. This can pull the required information( columns/data required) daily into the custom table of your choice and used for reporting. https://instancename.service-now.com/sysevent_list.do?sysparm_query=nameLIKEreport name ==> report.view.homepage/report.view Instance ==>sys_id of Report user id ==>sys_id of the user user name ==> user name of the user Processed ==> Report processed time.