Domain Scope

glide sys.domain.use_record_domain_for_processes (true/false) — controls the domain used when selecting processes. When this property is enabled, system will use the record’s domain for choosing which processes to run on any form. For lists, system will use the user’s session domain for picking the processes.

glide.sys.domain.use_record_domain_for_data (true/false) — controls the domain used when selecting data. When this property is enabled, system uses the record’s domain for restricting the data visibility within a form. Users with appropriate role will see Toggle Domain Scope UI Action to toggle domain scope between record’s domain and user’s session domain.

NOTE: When either the glide.sys.domain.use_record_domain_for_processes or glide.sys.domain.use_record_domain_for_data property is set to TRUE, the following properties are not used, regardless of their setting:

• glide.sys.domain.use_record_domain
• glide.sys.domain.use_record_domain_for_client_scripts
• glide.sys.domain.domain_change_notify
• glide.sys.domain.no_change_roles

Domain Picker

glide.ui.domain_reference_picker.enabled (true/false) property enables the type ahead reference domain picker.

glide.ui.domain_picker.role By default, users with the itil role, and roles that include the itil role can access the domain picker in UI16. You can restrict roles that have access to the domain picker by setting the roles as a coma separated list of roles in this system property.

Domain Process Override

glide.domain.strict_override (true/false) property prevents a child domain from inheriting the processes from the parent, even if they have not created overrides. When this property is ON, the domain framework will enforce stricter rules for policy overrides. For example, when a module is overridden in a child domain and marked as inactive, it will NOT use the parent domain’s module when the property is ON.

Or for example, if we are in Domain B and we don’t want any processes from the parent Domain A. If have not overridden the rules from Domain A and have not created any business rules in Domain B, the system will run the business rules from parent Domain A as long as this property is False. But if this property is enabled, Domain B will not get any business rules from parent Domain A.

Global Domain

glide.sys.restrict_global_domain_processes (true/false) property set to true, by default, when a user in the Global domain and views a table containing a sys_overrides column, the user sees records from only the global domain. This property enables an admin user to expand visibility from just the global domain to all domains. The Expand/Collapse Domain Scope links are used to expand or collapse visibility when this property is enabled.

Business Rules

glide.sys.domain.skip_domain_insert_businessrules (true/false) Specifies the domain scope for business rules executed on the domain table. In new activations of domain separation, the property default is true and business rules are determined by the session domain. In existing implementations, the property default is false and the business rules are determined by the newly created domain’s hierarchy.