Standard Change Domain Separation

[Jon G]

Is it possible to add domain separation to Standard Change templates?

We use domain separation quite heavily, and would like to have Standard Change Templates that are approved in one domain, but not available in other domains. Can this be done?

[Michael Fry1]

You should be able to following these instructions: https://docs.servicenow.com/bundle/london-platform-administration/page/administer/company-and-domain...

[Jon G]

I'm familiar with that process, but I wasn't certain about doing that in this case. There are a few different tables in use for Standard Change:

My biggest concern is Standard Change Template extends Record Producer which ultimately extends sys_metadata.  I can't add the domain field to metadata, and even if I could, I'm not sure it would be a good idea.  I can try adding domain at a lower level and see what happens. EDIT: I'm going to try adding at the Catalog Item level (sc_cat_item) to see what happens.

Standard Change Proposal extends Task - we're all set there.

Standard Change Template Value extends sys_template.  It looks like I can add the sys_domain column to template.  I don't think this will cause much of a problem.

I'm going to play with this a little bit in my developer instance.

Thanks for the tip.  Hopefully somebody who has specifically dealt with this can comment as well.

[Jon G]

Was searching for something else related to my own post above and found this again.

For anyone searching:

I did some testing in my developer instance, but we never implemented in PROD, so there might be some yet-to-be-discovered bugs. 

It seems that adding domain separation to sc_cat_item and sc_category accomplished what we were trying to do.  Categories and catalog items only appear in the domains they need to, and I didn't see any ill effects.

The only downside that I still see is that Standard Change Properties seem to be one-size-fits-all. I don't think there's a way to have separate Standard Change Properties per-domain.