Domain Separation and its impacts on other plugins

[Dom Davidson]

Hello Community,

I am presently working with a client who is thinking about implementing ServiceNow, using Domain Separation.   Having the corporate entity of the company reside on global domain level and the other sub-branches of the company in child domains.

One of the questions that came up, where

- What are the impacts of Domain Separation while turning on plugins in the child instances?   Would the parent domain also have the plugin automatically turned on?   Also, would other child instances have this plugin automatically turned too? Are downloads of plugins domain separable?

- Also, if a plugin was turned on and enabled in one of the child instances(say ex.JIRA POC plugin) with all customization captured on the child instance.   Will the parent domain have access to these customization? I am aware Script Include is not domain separable, but what about Business Rules and Client scripts?

- Also, say if the above has been implemented(On child domain, a particular plugin was downloaded and enabled, along with added customizations-UI policies, Business Rules and Client Scripts) and later downstream the parent domain decides to download and implement the same plugin with added customizations(customizations different from child domain) how would this impact the big picture?

I couldn't find any materials regarding the above criteria, hence your expert response is most appreciated.

Much thanks!

-Dominic Davidson

[Chuck Tomasi]

Thanks Robert.

I think the precedence is that "Our Active Directory is set up with domains, so we should be able to do that with ServiceNow, right?" Two totally different scenarios and outcomes despite having the same term "domain".

[lss123]

What is the "SHARE update set" you're speaking of?   I'm interested in learning more about data separation without using ServiceNow's domain separation.

[Daniel Draes]

It is this one:

Simple Record Separation