Domain system properties and user preferences
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Now Platform Security
Administrators have access to properties and user preferences that control domain scope.
Properties
New activations of domain separation automatically restrict domain scope to the record's domain for all related data or processes. When the user views a record in a form, the record's related data (such as reference picker and related list data) and applied processes (such as business rules and client scripts) are restricted to the record's domain scope. If there are records in multiple tabs, each tab has its own domain scope based on the record opened within that tab. The following properties restrict domain scope to either the record’s domain and the user’s current session domain.
Property | Details |
---|---|
glide.sys.domain.use_record_domain_for_processes | Restricts domain scope to the record's domain for all processes. This
property does not apply to business rules. Business rules are always processed
from the domain record.
|
glide.sys.domain.use_record_domain_for_data | Restricts domain scope to the record's domain for all data.
|
- 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
In new activations of domain separation starting with the Jakarta release, the session domain determines the business rules executed on the domain table. In previous versions, business rules executed on the domain table were set based on the newly created domain’s hierarchy. This behavior is modified by the glide.sys.domain.skip_domain_insert_businessrules property. Setting this property to true significantly improves domain insert performance.
Property | Details |
---|---|
glide.sys.domain.skip_domain_insert_businessrules | 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.
|
glide.sys.domain.skip_non_global_businessrule_if_nodomain | Ensures that only bus.rules from global domain are executed when using
queryNoDomain() or when table is not domain-separated, so you can skip any other
business rules
|
User preferences
In addition, user administrators can set the following user preference globally or on a per-user basis:
Preference | Category | Updated By | Details |
---|---|---|---|
glide.domain.session_scope | Domain | Admin Only | When true, sets the default scope to the user's session domain rather than
the record's domain. When false, the default scope is the record's domain. Users
with the domain_expand_scope user role can still change the domain scope as needed.
|
glide.domain.session_scope_notification | Domain | Admin Only | When true, displays a visual cue that record values include an expanded
domain scope. When false, the notification is hidden.
|
On this page
Related Content
- Domain separation application properties
The Domain Separation plugin has two new tables to give service providers more flexibility in customizing their applications that use domain separation. These tables are the System Application Property table [sys_application_property] and the System Application Property Value table [sys_application_property_value].