Domain Separation

Last updated on 15 February, 2024

LMDX can work natively in ServiceNow instances that have enabled domain separation. This allows for the logical separation of a ServiceNow instance into separate domains, where a single instance can support multiple organizations. As a managed service provider (MSP) you can for example segregate events, alerts and insights by tenant. For more information, see Grouping by Tenant and Domain Separation.

LMDX itself is not domain-separated and all scoped application records will be in the Global domain. This is because the SN admin role is required (for security reasons) for users to be able to access and configure LMDX.

All LMDX artifacts (config record, Outbound Transform Map and Outbound Field Maps) must be created within the Global domain to ensure the application works correctly. The only exception is Business Rule – this must reside in the primary domain of your instance. For more information, see the ServiceNow documentation.

Enabled Domains

You can enable domain support for LMDX. This lets you set up specific domains marked as “enabled” in LMDX, where each enabled domain can have its own LM Dexda credentials, allowing for the separation of data within LM Dexda portals. For more information, see Enabling Domain Support.

Domain Hierarchy Support

LMDX utilizes the domain hierarchy. If a record in a child domain matches the parameters set for a Config record in a parent domain, that record triggers the parent domain’s config. This allows for configuration standardization across multiple child domains, for example, different customers. You can make changes in one place and LMDX will apply that change across all child domains.

However, if there are multiple Config records associated with different Enabled Domains that could apply to a record, LMDX will use the closest match (for example lowest) within the domain hierarchy.

LMDX also similarly utilizes the CMDB hierarchy. In the case of a CMDB config in a domain-separated instance, the order of matching is first done on the CMDB hierarchy within the same domain, before moving up the domain hierarchy.