2 Replies · Latest reply on Aug 12, 2017 9:48 PM by Pradeep Sharma

    Has anyone been able to have glide.ui.autoclose.time affect a scoped application?



      We are trying to have a new application for one of our teams auto close tickets after 3 days, the same way as it does for Incident. We found that this was via the following system property: glide.ui.autoclose.time.


      We are not sure this will work on a scoped application. Anyone have any experience doing this?

        • Re: Has anyone been able to have glide.ui.autoclose.time affect a scoped application?
          Sachin Namjoshi

          Autoclose functionality does not depend only on glide.ui.autoclose.time property.


          There are 3 pieces of configuration points that make up the auto-close behavior.


          The property glide.ui.autoclose.time is used to determine the number of days after a "silent" resolved incident is closed. A "silent" record is a record that has not been updated on any fields. Any update resets the record so that its auto-closure is measured from last updated timestamp.

          This record is located at /sys_properties.do?sys_id=d5c26446c0a8011800cdf450892cec2d.

          Business Rule

          Incident autoclose contains all the code necessary to do the closure. This includes the query for all the incidents in resolved state and a query of all incidents that have not been updated for longer than the "autoclose days." The business rule also sets a few values:

          • The value in closed_by field to be the same as resolved_by
          • Value in the state field to be closed
          • Active to be set to false

          This record is located at /sys_script.do?sys_id=d67b8d9ec0a80118008cd8f0f7f92fae.

          Scheduled job

          Autoclose Incidents calls the business rule every hour to actively search for "silent" resolved incidents. The job is auto-queued to run every hour by default. This job is normally quite quick and does not create excessive strain on the incstance. If you have an extremely high volume of incidents being moved into resolved state, then you may change this to run at a lower frequency or even once a day only.

          This record is located at /sys_trigger.do?sys_id=d67e98dac0a8011801393f5054790aa5.


          Since business rule and scheduled job will be in Global scope, you will have to customize auto close logic for your custom solution.




          Please mark answer as Correct, helpful as appropriate.

          • Re: Has anyone been able to have glide.ui.autoclose.time affect a scoped application?
            Pradeep Sharma

            Hello Carl,


            Below is the solution.

            1.Create a system property i.e sys_properties.do (Mimic the property in the same way as OOTB property "glide.ui.autoclose.time"

            2.Create a scheduled job with the script as. Update the table name/additional add query and property name(Per step1) as per your req

            function autoCloseTickets() {
            var ps = gs.getProperty('glide.ui.autoclose.time'); //Here create your own system property and pass the updated name
            var pn = parseInt(ps);
            var queryTime = new GlideDateTime();
            if (pn > 0) {
            var gr = new GlideRecord('PASS TABLE NAME HERE');
            gr.addQuery('sys_updated_on', '<', queryTime);
            while(gr.next()) {
            gr.state = 7;
            gr.comments = 'Ticket automatically closed after ' + pn + ' days in the Resolved state.';
            gr.active = false;




            Creating a Scheduled Job - ServiceNow Wiki


            P.S: Please ensure you are in the right scope before doing all the changes mentioned above. Let me know if  you have any questions.

            - Pradeep Sharma (@sharma_pradeep)

            PS: Hit like, Helpful or Correct depending on the impact of the response