Which role restricts access and allows for managing items in a domain-separated catalog?
The role domain_catalog_admin is specifically designed to manage items within a domain-separated catalog in ServiceNow. This role restricts access and allows for the management of catalog items, ensuring that only users with the appropriate permissions can make changes within their designated domain. This is crucial for maintaining data privacy and integrity across different domains, especially in environments where multiple customers or departments are served by a single ServiceNow instance.
* ServiceNow Domain Separation and Service Catalog1
* ServiceNow Product Documentation on Domain Separation2
What does the system property glide.sys.domain.delegated_administration do?
The system property glide.sys.domain.delegated_administration is designed to empower customer administrators by allowing them to configure their own domains. This is crucial in a multi-tenant environment where multiple customers or departments are operating within the same ServiceNow instance but need to maintain separate configurations and data. By enabling this property, customer admins can make changes specific to their domain without the risk of affecting the configurations of other domains. This property essentially enables domain separation, which is a method of separating data into logically defined domains.
The system automatically sets which field when an administrator attempts to modify a policy, application, or module that belongs to another domain higher in the hierarchy?
When an administrator attempts to modify a policy, application, or module that belongs to another domain higher in the hierarchy, the system automatically sets the sys_domain_owner field. This field ensures that the ownership of the record is correctly attributed to the domain that originally created or owns the record, maintaining the integrity and separation of data across different domains.
* ServiceNow Domain Separation - Advanced Concepts and Configurations
* Understanding Domain Separation - Basics
To grant domain visibility to a user you can
Choose 2 answers
In ServiceNow, domain visibility determines whether users from one domain can access records from another domain. To grant domain visibility to a user, you can:
AAssociate a visibility domain to one of the user's roles: This allows any user with that role to see records in the associated visibility domain1.
EAssociate a visibility domain to one of the user's groups: Groups grant their members the visibility domains of the group, which means when a user is part of a group, they inherit the visibility domains associated with that group1.
It's important to note that when a user leaves a group, they lose the group's visibility domains, and the use of visibility domains should be done thoughtfully as excessive use can slow performance2. Moreover, the domain hierarchy should be optimal to prevent performance issues2.
The options B, C, and D are not standard practices for granting domain visibility according to the ServiceNow documentation and best practices. Specifically, associating a visibility domain directly to a user record or setting the visibility domain's parent to the user's domain are not mentioned as recommended methods3421.
Why would you set Choice Action to Ignore on a transform field map?
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
