Domain separation and Universal Task
Summarize
Summary of Domain Separation and Universal Task
Domain separation in ServiceNow's Universal Task allows for the organization of data, processes, and administrative tasks into distinct domains. This functionality enables agents to request additional information or assign tasks to employees for effective ticket resolution while controlling user access to data across different domains.
Show less
Key Features
- Process Domain Separation: Configuration tables are separated by process domains, allowing for the inheritance and overriding of settings across child domains.
- Data Domain Separation: Data tables ensure that information from child domains can be accessed by the parent domain while restricting access to other service domains unless configured otherwise.
- Runtime Support: The application supports domain separation at runtime, affecting the user interface, cache keys, reporting, and data aggregations.
- Sample Use Case: In a service provider scenario, responses through chat can be viewed by tenant-customers, ensuring transparency in communications.
Key Outcomes
Implementing domain separation in Universal Task helps organizations manage their services more effectively by allowing tailored configurations per service while maintaining oversight at the organizational level. Customers can expect enhanced data security and streamlined processes that cater to specific service needs without compromising on accessibility or functionality.
Domain separation is supported for ServiceNow Universal Task. Universal Task enables agents to request extra information from the employee or to task the employee to accomplish an activity, in order to resolve a ticket. 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: Basic
- Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
- The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
- The owner of the instance must set up the application to function across multiple tenants.
Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.
For more information on support levels, see Application support for domain separation.
Universal Task domain separation overview
In the Universal Task framework, all the configurations are process domain-separated, and the data tables, namely, Universal Task table, Employee form table, and Task template table are data domain separation offerings.
How domain separation works in Universal Task
The configuration tables in Universal Task are process domain-separated. So, the configurations created by the parent domains are also implemented in the child domains. However, a child domain can override the configuration, if needed. For example, In an organization, the services are the child domains, while the organization is the parent domain. The task types available for Universal Task in a particular organization, will also be available for the various services of the organization. However, a particular service can override the task types as needed.
The data tables in Universal Task are data domain-separated. So the data stored in any of the child domains is accessible to the parent domain. For instance, if a service is using task templates, the data captured in the Task templates table for the service domain is accessible to the organization domain, but not to the domains of other services, unless configured.
Tables
- sn_uni_task_config
- sn_uni_task_base_task_config
- sn_uni_task_catalog_task_config
- sn_uni_task_emp_input_task_config
- sn_uni_task_universal_task
- sn_uni_task_template
- sn_uni_task_employee_form