Sorry Aditya i probably should have attached it from the beginning. This is the report with out any timings attached to it. Currently, this is the report that the Change Admin runs the Change Meeting with and it shows all the changes requests that are approved and are in CAB Meeting State.
This is what the ServiceNOW Engineer sent me.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Your desired outcome, as I understand it, is to generate a list of records which, aside from other filter options, will include only those records that were created no later than the most recent Tuesday an 12:00 Noon, and no earlier than 12:00 Noon on Tuesday of the previous week. And, as I related during our call, there isn't a way to specify what you would like to do, using the Filter builder UI. You can however craft what's known as a "scripted filter", typically within the framework of a Script Include, which will encapsulate the necessary query / logic using GlideRecord objects. The idea is that the scripted logic will return a list or array of change_request.sys_id values, which you can call with a "Sys ID" filter. For general documentation on doing something like that, for Helsinki, please see Create scripted filters and Use script includes. A couple notes regarding the first link: * The given example of a filter:
[Caller] [is] [javascript:myFunction()]
should instead, for a script include -implemented filter be:
[Caller] [is] [javascript:new NewInclude().myFunction()]
* Your eventually filter used would look more like this:
[Sys ID] [is] [javascript:new CAB_ReportingFunctions().getLastWeekCHGs()]
...for script include "CAB_ReportingFunctions" and filter method getLastWeekCHGs(). * The javascript given looks odd because there are extra spaces added; otherwise, it's syntactically correct. The hardest part of this task will be work up logic to programmatically script a GlideRecord query specific to your date-time requirements, i.e. of setting abstract start- and end-points for that. If you need help there, I would suggest searching the ServiceNow Community, and perhaps posting a new question. (I reminded you that Tech Support can't really assist you with design or implementation tasks; you can however open incidents for API-level questions.) An idea that occurs to me---untested!---is to use the GlideSystem (gs) methods beginningOfThisWeek() and beginningOfLastWeek() as rolling reference points---to which you could add a set number of hours. The Glide APIs are documented at the ServiceNow Developers portal; click the Legacy tab to see classic "global" methods.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
