Domain separation and Table Builder
Summarize
Summary of Domain separation and Table Builder
Domain separation in ServiceNow allows you to segregate data, processes, and administration into logical domains, controlling user access and visibility. It supports multi-tenant environments, enabling service providers to configure business logic and data parameters per tenant, ensuring tailored functionality for each customer within a single instance.
Show less
Table Builder is a tool that lets developers configure form layouts and logic for tables in their applications. When launched from UI Builder, Table Builder supports domain separation, allowing developers to create and modify forms within different domains in the same browser session. However, domain separation is not supported when Table Builder is launched from App Engine Studio.
Key Features
- Domain-Specific Form Customization: Developers can create domain overrides for form layouts, section layouts, and form logic, enabling customized user experiences per domain.
- Session Domain Switching: Allows developers to switch session domains to manage overrides effectively within the multi-tenant architecture.
- Override Indicators: UI policies and form views with domain overrides are clearly marked, helping developers identify customized elements across domains.
- Governance and Standardization: Encourages minimal domain-specific configurations to maintain a stable, scalable instance and reduce code sprawl, facilitating smooth adoption of new ServiceNow features during upgrades.
- Form and Section Layout Management: Domain overrides require changes to both form and section records when applied at lower domains. Section labels cannot be edited before saving domain overrides.
Practical Considerations
- System dictionary changes like field metadata updates do not require domain overrides.
- Single-section forms only have section records until a second section is created; adding sections can break existing domain overrides for these forms.
- In the global domain, developers can view all form views across domains, facilitating comprehensive management of domain-specific customizations.
Benefits for ServiceNow Customers
This capability enables organizations managing multiple tenants or business units within one instance to maintain tailored configurations while preserving overall system stability and performance. By leveraging domain separation in Table Builder, customers can efficiently customize forms and processes per domain, support multi-tenant use cases, and minimize administrative overhead related to managing complex domain configurations.
Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Support level: Standard*
The support level is Standard but has some exceptions or special conditions.
- Includes all aspects of Basic level support.
- Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
- The instance owner must be able to configure minimum viable product (MVP) business logic and data parameters. This configuration is done per tenant, as expected for the specific application.
Sample use case: An Admin must be able to make comments required when a record closes for one tenant, but not for another.
For more information on support levels, see Application support for domain separation.
Overview of domain separation
Table Builder enables developers to configure the layout and logic for each form view for tables in their application. When launched from UI Builder, Table Builder supports domain separation, which is the ServiceNow instance-wide multi-tenant architecture.
Table Builder enables developers in domain-separated environments to create forms while they are in the same browser window. Domain separation in Table Builder works similarly to an application scope that helps administrators to create or edit in a multi-tenant environment.
Standardization is the key principle to maintaining a stable, healthy, and scalable ServiceNow instance, where domain separation is installed. By having standardization, you have a common configuration that most of the instance operates by. When an instance has hundreds or thousands of domains, managing them successfully requires rigorous governance. Domain-specific configurations should be done only if they are deemed necessary by the instance owners. Most instances should follow the common instance configuration to provide a more uniform experience across the instance. It also lets instance owners minimize the code sprawl that slows the adoption of new ServiceNow features that are included as part of the release upgrades.
How domain separation works in Table Builder
Table Builder enables developers to switch the session domain to create domain overrides to the form layout, section layout, and form logic. System dictionary record changes (such as field metadata for a field label) do not require domain overrides. Form layout changes require domain overrides to both the form record and the section when the change is performed at a lower domain. When creating a domain override, section labels can't be edited prior to saving the override.