Domain Sep problems with SLAs, indicators, and more

[robpresland]

I think I understand Domain Separation. I am often proved wrong when I try to configure something.

I am not a newbie to Domain Sep, I've been working with it for more than a year now and have learned lots. Yet I still need to learn more.

I've run into some issues and I'm hoping some experts here can help me. Warning: long post ahead.

I have the following domains:

TOP -> Clients -> Shared -> Client F

TOP -> Clients -> Shared -> Client C

TOP -> Clients -> Client S

I need to:

1. Users in Client C need to see everything in Client F, ideally, without changing their session domain. Some of this is addressed with Client C contains Client F. One issue I have is that SLAs defined in Client F are not entirely visible to users in Client C (SLA def name and target are not visible in task_sla table). I was told SLA are process not data so I created Shared domain and moved the SLAs to the Shared domain. I think this has resolved the SLA issue. Please let me know if there are adverse issues I need to look out for in this configuration.

2. Users in Client F need to see their data in the indicators (Platform Analytics). By default, as the data collection jobs are run as System Admin, only global data is collected. So I changed the Run As to a user in Client F. Two issues with this: (a) a user in Client C needs to switch session domain to see the Client F data in the indicators, and (b) Client S will never see their data in indicators as there is no data collection for that domain. For (a) I can't see a way around this. Is there a solution for this? For (b) there is a plugin but it's only available in Platform Analytics Premium which we don't have. Is there an alternate solution, other than duplicating all the data collection jobs, and configuring Run As to be a user in Client S (all indicators are still defined in global)?

Thanks in advance to any insights and solutions that help.

Platform: Zurich Patch 7

[Mark Manders]

From what I have read, you need that subscription to allow what you are describing. ServiceNow doesn't allow other indicators/jobs to run besides the OOB ones, unless you have the licenses for it. So you can run an existing job on a domain user, collecting everything for that domain, but then no other domain records will be collected.

https://www.servicenow.com/docs/r/now-intelligence/performance-analytics/c_PAWithDomainSeparation.ht...

https://www.servicenow.com/docs/r/now-intelligence/performance-analytics/pa-domain-configurations.ht...