Domain separation and Generative AI Controller
Summarize
Summary of Domain separation and Generative AI Controller
The Generative AI Controller supports domain separation, allowing ServiceNow customers to logically partition data, processes, and administrative tasks into distinct domains. This separation ensures that users in one domain cannot access or interfere with the capabilities or data of another domain, enhancing data security and operational isolation. Domain separation applies specifically to the OneExtend capabilities, which are foundational elements for Virtual Agent Designer topics and generative AI scripts and flows.
Show less
How Domain Separation Works in Generative AI Controller
Domain separation is implemented at the OneExtend capability level. Each capability record is associated with a specific domain, and related execution and configuration data, such as logs, are also domain-separated. When creating a new generative AI capability in a different domain, you must:
- Create a new record in the OneExtend Capabilities table with the appropriate domain set at creation time.
- Replicate associated attribute records and capability definitions from the global domain to the new domain.
- Configure the OneExtend Definition Config record to include the capability definition for the new domain.
These steps ensure that the capability functions correctly and independently within its domain. Using an existing capability as a blueprint is recommended to verify proper behavior.
Support and Use Cases
The Generative AI Controller provides standard-level support for domain separation, including domain-aware application properties and business logic tailored per tenant. This enables service providers to manage multiple customers within a single instance effectively. For example, an administrator can require specific record closure comments in one tenant's domain but not in another.
With domain-separated capabilities, customers can develop isolated Virtual Agent topics, Workflow Studio flows, and background or business rule scripts that operate independently within each domain, ensuring customized and secure service delivery.
Domain separation is supported for Generative AI Controller. 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
- Includes all aspects of Basic level support.
- Application properties are domain-aware as needed.
- 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 configure the minimum viable product (MVP) business logic and data parameters 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.
Domain separation enables you to create partitions in the application data and administrative processes. Because the generative AI tables are domain separated, Generative AI Controller supports domain separation for OneExtend capabilities. The capabilities are the basic building blocks for Virtual Agent Designer topics, components, flows, and scripts that use generative AI. With domain separation, you can isolate the data and control access so that users in one domain don’t have access to the capabilities of another domain.
For more details on domain separation and Virtual Agent, check out the documentation.
How domain separation works in Generative AI Controller
Domain separation is possible at the generative AI OneExtend capability level. Records that are related to the execution and configuration of OneExtend capabilities, such as log tables that are accessible to ServiceNow personnel, are also separated according to the capability's domain.
If you want to create a copy of an existing generative AI capability in a different domain, you must create a record in the OneExtend Capabilities (sys_one_extend_capability) table. See the reference for Generative AI Controller for more information about the OneExtend Capabilities table.
You set the domain when the record is created. The domain is based on the domain that you're in at the time that you create the record. When you're creating a capability record, you can use an existing OneExtend Capability record as a blueprint to help confirm that the capability works as intended.
After you create the OneExtend Capability record, you must create records for the following attribute and config records in the new domain:
- OneExtend Capability Attribute records with the same values as the capability in the global domain.
- A OneExtend Capability Definition that corresponds to the new capability.
- A OneExtend Definition Config definition record that includes the OneExtend Capability Definition for the new domain.
You can also create these records by using the related lists in the OneExtend Capability record default view.
Use cases
With domain-separated capabilities, you can build different Virtual Agent topics, flows with Workflow Studio, or different background and business rule scripts that are also domain separated.