Standard Change Templates - why do they go into an updateset???

[Zod]

Hi Experts,

I wonder why standard change templates are automatically added to an updateset. From my point of view this is not correct as they should be processed within the production environment .. . Any idea why this is set like this OOTB?

[Dubz]

Only data is excluded from update sets, all configuration is included.

Templates are configuration. Any specific instances of a standard change (data) won't be moved but the configuration of the template will be.

[Zod]

When using a standard change proposal and processing it (approval) a record producer is created (template) that can be used to create standard changes later on. This is part for the process and no configuration!!! If you check the updateset, not only the type "Standard Change Template" will be added, but also "Catalog Item Category" and "Catalog Items Catalog" ... all NO configuration.

This is not ok from a process perspective as this entries are not approved within the productive environment ... for me this looks like a wrong servicenow setup ..

[Zod]

I think the issue is that "normal" catalog items are created in DEV .. tested etc. and transported ... and the standard change templates just follow that logic even this does not make any sense for them .....

[Dubz · Accepted solution]

It creates a configuration that requires approval. It is still configuration. i can see why people might want to be able to create a bunch of templates on dev and then move them to prod. The best way around this is to be aware of what update set you are in when you're working on dev!