SLAs in Domain Separated Instance - SLAs treated as Data or Process?

[rrshah83]

In Domain Separated instance, are SLAs treated as Data OR Process?

I have set use_record's_domain sys_properties to false. This means that data and process should be rendered based on current user's domain. It should never use record's domain. For SLAs, I found that whenever an task_SLA is created or updated, its domain changes to current record's domain. Do you know why?

I would want the SLAs to remain in the domain they were defined (in SLA definition). For example, if an SLA is created in Domain for Vendor A, no matter what the current user's or record's domain is, the task_SLA must be created in Vendor A domain and should always remain in Vendor A domain. So that only Vendor A can see their task_sla records.

Do we need to write AFTER business rules for these? (That seems like a workaround).

Additional Information:

domain hierarchy:

TOP --> Sector 1 --> Vendor A

TOP --> Sector 1 --> Vendor B

[rrshah83]

Please note, I have read all existing discussions in community. I have also read the ServiceNow KB: SLA definitions ignore domain separation (KB0523790).

But I still cannot figure out how SLAs work in domain separated environments.

[rrshah83]

deepak.ingale Hi Deepak, you seem to be most active for all domain separation discussions, could you please help?

[rrshah83]

david.legrand you seem to be most active for all domain separation discussions, could you please help?

[rrshah83]

Michael.Fry you seem to be most active for all domain separation discussions, could you please help?