Domain separation and Universal Task
Summarize
Summary of Domain Separation and Universal Task
Domain separation in ServiceNow's Universal Task allows agents to request additional information from employees or assign tasks to resolve tickets while maintaining data integrity across different logical groupings, known as domains. This feature ensures that data, processes, and administrative tasks are organized and that user access can be effectively controlled.
Show less
Key Features
- Process Domain Separation: Configurations created by parent domains are implemented in child domains, with the ability for child domains to override these configurations.
- Data Domain Separation: Data stored in child domains is accessible to parent domains, enhancing data visibility while restricting access to other service domains unless explicitly configured.
- Configuration and Data Tables: Specific tables for configurations and data are designed to support domain separation, ensuring organized and efficient task management.
Key Outcomes
By implementing domain separation within Universal Task, organizations can streamline service provider interactions, maintain data integrity, and enhance the visibility of task responses across different service domains. This setup is crucial for managing multiple tenants effectively and ensuring the right users have access to the relevant data and configurations.
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.
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