Scheduled job for multiple tasks or tickets

[dave_greg]

Hi Everyone,

I’m just about to schedule hundreds of recurring monthly maintenance jobs, where I would like to have the dozens of tickets for each location set as tasks under each region.

ie. One region has many locations that need maintenance each month.

To date, it would appear I need to create a separate template for hundreds of locations… which is relatively simple via an Excel import, HOWEVER, I can’t see a way of scheduling a job for each region… it seems I need to create a scheduled job for EVERY template… which I can again import from Excel easily enough, but that means I can’t group those tasks under a specific ticket.

What is the best practice here?  How do you accomplish this requirement in your instance?

I’m potentially making a decision that will solidify a process for many years, so it’s vital this is workable from a reporting and maintainable perspective.  I don’t really care which application I use (ie. tickets or requests) so long as it works.

Above all else, I’m not after a scripted solution… I’m not a programmer and dont want to be!  I just figure that San Diego must have a simple way of achieving what is a pretty standard business  function.

Thanks for reading.

Regards,

Dave

[bammar]

I have a very interesting idea for you.

Get a spreadsheet with every single scheduled job - fields you need like category subcat, description, whatever was going to be in your template.

Add a field that only an admin can see of type true false titled Maintenance Repository in the table you want like Incident.. 

Add that column on your template spreadsheet and mark it true...

Upload that spreadsheet in- now ServiceNow holds all your maintenance tasks dozens for each location

Also assuming the jobs run monthly- then you can run a scheduled job monthly to identify the records with Migration repository  = true, make a new copy of each sans migration true and voila

If you need to get even more complex  you can try to use a date field or a frequency field like lets suppose maintenance is on 15th of everyth mth for some and 1 for the other- you can game the system a bit, and your levers of operation may dictate you run it every night and query a diff subset... Also consider lead time you may need the records ready a few days early if that is needed.  I bet you didnt expect the approach i suggested but  the cool thing is if you open a new location or task you can just add more to the repository 

[bammar]

one more thing- make the records with the true flag editable by only admin or maybe a new role granting them repository access.

[dave_greg]

Thanks for your help.  I didn’t quite grasp how a single scheduled job could call different templates.  But I’ve just realised I can’t import the hundreds of templates, as I can only use the basic fields in the list view (I’m using the ticket table), so it looks like it’s going to be a very manual exercise.  If have to manually enter each template, I may as well just schedule the job in the same time… then I’ll take your advice and label a field so that every group of locations has it’s own region… not very eloquent, but at least you can sort the list.

[dave_greg]

Apparently this is what I've been searching for... at least part of the answer:

https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/form-administration/task/create-templates-for-related-task-records.html