Why Scheduled Job not captured in Update set

[Mark Wood]

Hello Experts,

I want to know the reason why scheduled jobs and transnational data such as incidents, changes, problems, knowledge, and CI's

are not captured in the update set.is there any specific reason for that can one please guide them on this?

Thank You

[Michael Fry1]

Scheduled Jobs are considered data and data is not captured in update sets.

[jMarshal]

There are many reasons for this.

Primarily it is that you (as a developer user on the platform) should (sorry, bad word) NOT want this transactional data in your development artefacts...as the development being done is usually designed to fit any data, not just the data you have been developing with and/or testing with. Not to mention the reconciliation of transactional data coming from one instance to a production instance which is still running (live).

Imagine this - you're developing in subprod, with data that will be promoted (via an update set) to prod and in subprod, you have INC00011234, which your development modifies...but at the same time, in prod, someone manually modifies the same INC...which one stays, when you move the update set to production?

...I suppose there could be "skipped records" that you would mark for manual reconciliation (like when doing an upgrade)...but that's an odd concept, in terms of development. Development should be agnostic of the data and only consider the data model.



Though, I do understand the desire to include scheduled jobs and some "data" elements in update sets as they are often parts of automation/workflows (developed solutions, as opposed to "transactional record data")...my recommendation for that, is to make sure your organization follows good change management practices as the implementation plan would need to account for some "live data changes" if/when scheduled jobs are involved. Theoretically, you *should* (there's that word again) be able to set up the new jobs in prod, set as inactive and then just associate the job with the other programmic elements in the update set (keeping "live data chagnes" to a minimum, when releasing a solution in production - simply "activating" the new jobs and "deactivating" the old ones - as opposed to modifying the existing records)...but now we're going down a theoretical rabbit hole...

[Edward Rosario]

Scheduled jobs are not captured in update sets in ServiceNow because update sets primarily focus on capturing changes made to records within the system, such as tables, fields, and their configurations.

[Steven Parker]

While these items are not captured natively, we use a utility called "Add to Update Set".  This utility allows you to add items to update sets that normally wouldn't get added.  We use it for scheduled jobs and various other things and it allows you to add the scheduled job (or whatever else) to the update set and move it from one instance to another.

You can find the utility here:

https://developer.servicenow.com/connect.do#!/share/contents/9824957_add_to_update_set_utility?t=PRO... 

There is also more details on the utility and subject here:

https://www.servicenow.com/community/developer-blog/add-to-update-set-utility-documentation-and-cust...