Install Domain separation plugin in already live Production instance?

Suggy · ‎12-22-2022

We have 2 customers running their own insances (instance A and B).

Now they have decided to use only 1 instance. 'A' instance will be as it is, 'B' will be released and start using 'A'.

On 'A' domain separation plugin needs to be activated.

1. Is it fine to activate 'Domain separation' plugin in already running instance?

2. If so, are there any challenges? Any issues? Anything to be aware of? (Apart of managing 'B' data into their respective domain)

Tom Sienkiewicz · ‎12-23-2022

You definitely need to look at B both from data and process perspective, to understand how the process/configuration might have to differ from A. There might be conflicting requirments or at least a need to have certain logic run only for either of the domains (BRs, client scripts. Flows etc.).

Now technically yes you can activate DS in a live instance. What is going to happen is all your data in instance A is going to be placed into the global domain and be visible for everyone. So you will need to decide which data needs to be moved to the dedicated domain for A.

Then before you bring in any data for B, you need to create logic/rules for putting this data into dedicated domain for B (for example as part of transform maps).

You also need to review and plan which data needs to be visible to both domains (any foundational data etc.). If you expect global reporting requirments from both A and B domains, create another domain above A and B with access to both, or at least create dedicated visibility config for a "global reporting" kind of domain and users.

You should also review the domain separation support level of different ServiceNow products. Some of them already have rules to put data into the correct domain, for others you need to configure those yourself.

It will help if you start by cloning your prod into a sandbox instance, then activate DS there and play around/do initial analysis there.

View solution in original post

Tom Sienkiewicz · ‎12-23-2022

You definitely need to look at B both from data and process perspective, to understand how the process/configuration might have to differ from A. There might be conflicting requirments or at least a need to have certain logic run only for either of the domains (BRs, client scripts. Flows etc.).

Now technically yes you can activate DS in a live instance. What is going to happen is all your data in instance A is going to be placed into the global domain and be visible for everyone. So you will need to decide which data needs to be moved to the dedicated domain for A.

Then before you bring in any data for B, you need to create logic/rules for putting this data into dedicated domain for B (for example as part of transform maps).

You also need to review and plan which data needs to be visible to both domains (any foundational data etc.). If you expect global reporting requirments from both A and B domains, create another domain above A and B with access to both, or at least create dedicated visibility config for a "global reporting" kind of domain and users.

You should also review the domain separation support level of different ServiceNow products. Some of them already have rules to put data into the correct domain, for others you need to configure those yourself.

It will help if you start by cloning your prod into a sandbox instance, then activate DS there and play around/do initial analysis there.

Suggy · ‎12-28-2022

Hey @Tom Sienkiewicz Thanks for replying. Had you come across such a situation before? Or you answered technically 🙂

Tom Sienkiewicz · ‎01-01-2023

Hi, me personally - I've worked with DS starting with a fresh instance, but as a vendor we've had clients adding DS post go-live, so let's say I'm more or less in the loop.

Let me know if you have any specific questions, maybe I can help.

Suggy · ‎01-06-2023

We successfully compelted this exercise in lower environment. Thank you very much @Tom Sienkiewicz