- My View
Does anyone know if it is possible to force the Incident auto-close to run sooner than 1 day for testing purposes? I am wanting to make sure the auto-close has no adverse impacts on some business rules I created to reopen Incidents.
You can modify property(in dev instances) for auto-close.
type in left nav: sys_properties.list(Press Enter)
Property name :glide.ui.autoclose.time
Mark Correct /Helpful /Like based on the effect of response.
Thanks Deepak! It appears that field only accepts integers so 1 is the lowest value I can use. I'll just be patient . I did see that using 0 turns off the auto-close.
The sys property actually accepts integer value representing the number of days before auto closing the ticket.
In the script responsible of the auto close functionnality you can change the call to daysAgo(integer) by minutesAgo() and put in the sys property 10 for example. This will help you test the auto close easily.
Wish this will help
Hi ait laaraj layla,
That sounds great! Do you have any information on how to access the script?
There is a scheduled job called "Autoclose Incidents" which runs every day. This scheduled job executes a business rule called "incident autoclose" which will in turn close any incident meeting the glide.ui.autoclose.time threshold.
Given it will only run once a day, it doesn't help you. So you could change the frequency of the scheduled job to run more often, or you can update this business rule in your test environment to run based on update - currently those actions are NULL and this is only executed via scheduled job.
Informationally if you look at the sys_created_on date of the incident autoclose business rule you will see it was created in 2006 so this is a very old piece of functionality. Best practice these days is for the function to be in a Script Include but this hasn't been updated to do that.
Please mark this post or any post helpful or the correct answer so others viewing can benefit.