New schedule creation is not capturing in update set??

[gaurav56]

Hi,

I have created new holidays schedules, but it is not showing in my update set that i selected before creation.

Can anyone know about this?

Thanks

Gaurav Jindal

[Deepak Ingale1]

Hi Gaurav,

In ServiceNow, there are two kind of data types if has to be segregated based on whether those gets captured in update set or not

1) Configuration data :- These type of data gets captured in Update sets. e.g, business rules, client scripts, ui macros etc.

2) Record data :- These are records just like Incidents, problems, changes etc.

ServiceNow determines what should gets captured and what not depends on the dictionary attribute "update_sync" present on the dictionary record of the "table" against which you are working.

You can check this by going into "dictionary" module then by looking for the table which you are working on. If that table has "update_sync" attribute, then your changes will get captured in update sets, else will be ignored.

Servicenow treats schedule entries as "Record Data" and not "configuration data" and there exists a separate process to move these type of data since it is very critical from sys_id point of views because your "Configurational Data" sometime refer to sys_ids of "record datas"

In your case, "Schedule Entries" are "record data" which are dependant on " SLA Definitions" which are "configuration data". \

So be careful while moving those kind of things. I suggest involving more experience "admins" if you want to move these scheduled entries to UAT.

You can still export these entries separately in XML file, and then import in "UAT" .

Exporting and Importing XML Files - ServiceNow Wiki

[Pradeep Sharma]

Hi Gaurav,

Please go through the below blog for more info.

Manually Add a Record to an Update Set - ServiceNow Guru

Please let us know if you have any questions.

[Geetanjali Khy2]

Hello Gaurav,

By default, scheduled jobs does not captured in update set because the ‘sys_trigger’ table doesn’t have the ‘update_synch’ attribute set.

You can run a script from the ‘Scripts – Background’ module to force the record into an update set. Please refer below script.

var gr = new GlideRecord("sysauto");    // Ensure the table name 'sysauto' is default table where the scheduled jobs are stored.

gr.get("d745b2780fe03401fff8e9ce1450e0f");   // add the record sys_id here

var gum= new GlideUpdateManager2();

gum.saveRecord(gr);

[Saurav Paira]

GlideUpdateManager2 does not work from Scoped Application