When an admin wants to view only the global domain process while in the global domain, they need to click on the Global Domain Scope. This option allows the admin to filter and view processes that are specific to the global domain, ensuring that they are not seeing processes from other domains. This is particularly useful in a domain-separated environment where maintaining clarity and separation of processes is crucial.
Reference:
* ServiceNow Domain Separation - Basics
* ServiceNow Domain Separation - Advanced Concepts

In ServiceNow, even though the Inbound Actions table has a domain field, records in this table should all be placed in the Global domain. This is because inbound actions, such as inbound email actions, are designed to be accessible across the entire platform, regardless of the specific domain. By placing these records in the Global domain, ServiceNow ensures that the actions can be executed and managed universally, without domain-specific restrictions.
For example, if an inbound email action creates an incident, the system creates the incident in the same domain as the user in the Caller field. If that user is not in the User [sys_user] table, the incident is placed in the Global domain1.
This approach maintains the integrity and accessibility of inbound actions across the platform.
1: ServiceNow Inbound Email Actions Documentation

In ServiceNow, the concept of domain separation allows for data and administrative segregation between different domains within an instance. When a business rule is defined in a parent domain, it applies to that domain and all child domains unless specifically overridden in a child domain1.
If a business rule is overridden in a child domain, the original rule in the parent domain continues to apply only to the parent domain and any other child domains that have not overridden the rule. The overridden rule in the child domain applies only to that specific child domain1.
Therefore, for the parent domain, the business rule that was created in the parent domain will run. The child domain's override does not affect the operation of the parent domain's business rules. This ensures that each domain can have customized behavior while still inheriting the broader rules set at the parent level.
It's important to manage these rules carefully to maintain the intended data integrity and operational workflows across different domains within the ServiceNow environment4.

In ServiceNow's domain separation model, data accessibility is designed to maintain the integrity and segregation of data across different domains. Here's how data accessibility works between parent and child domains:
* The parent users can access all child data: Users in a parent domain have visibility into the data of their child domains. This is because the parent domain is considered to have a higher level of data access privilege, allowing it to oversee and manage the data within its child domains1.
* The parent users can access all child data, but cannot access domains contained in the child domain: While parent domain users can access data in their immediate child domains, they cannot access data in "grandchild" domains or any domains that are further nested within a child domain. This maintains a level of data isolation and ensures that users only have access to the data they are permitted to view and manage1.
The options stating that both parent and child users can access each other's data (A) and that child users can access all parent data are incorrect. The domain separation model is hierarchical, not reciprocal, meaning that child domains do not have inherent access to parent domain data, and access between domains is not automatically bidirectional1.
For detailed information on domain separation and data accessibility, ServiceNow provides extensive documentation and best practices, which can be referenced for a deeper understanding of these concepts12

Setting the Choice Action to "Ignore" on a transform field map in ServiceNow is used to avoid inserting dummy referenced records into the global domain. When importing data, if the system encounters a reference field value that does not match any existing records, setting the Choice Action to "Ignore" will prevent the creation of a new, potentially incorrect record. Instead, the system will skip the field and leave it blank, ensuring data integrity and avoiding the clutter of unnecessary records.
For more detailed information, you can refer to the following resources:
* ServiceNow Support Article on Transform Maps
* Choice Action Field in ServiceNow