The topic includes an overview of domain separation and Problem Management. With
domain separation you can separate data, processes, and administrative tasks into logical
groupings called domains. You can then control several aspects of this separation, including
which users can see and access data.
Support level: Standard
- Includes Basic level support.
- Business logic: Processes can be created or modified per customer by the service
provider (SP). The use cases reflect proper use of the application by multiple SP
customers in a single instance.
- The owner of the instance needs to be able to configure the minimum viable product
(MVP) business logic and data parameters per tenant as expected for the specific
application.
Use case: An admin needs to be able to make comments mandatory when a record closes for
one tenant, but not for another.
Overview
- Problem Management is about eliminating
the root cause of a service interruption.
- The problem and problem task tables support domain separation. Therefore a Problem user sees
only problems or problem tasks that have been created within the (tenant) domain that they
belong to.
- Only Problem users can create and access Problems and problem tasks.
- Problem and problem task tables both support domain separation. Therefore, a Problem user
sees only problems and problem tasks that have been created within the (tenant) domain that
they belong to.
How domain separation works in Problem Management
Problem users see only problems and problem tasks that have been created within the (tenant)
domain that they belong to.
Problem users can use Problems and problem tasks within the tenant domains. Problem users can
create and update problems and problem tasks of their domain, any child domains, and the global
domain.
Known Issues
Task-Outage Relationship [cmdb_ci_outage] is not domain separated.
If installed, the Task-Outage Relationship table is not domain separated. Therefore Fulfillers
or Problem users can view any Task-Outage Relationship records regardless of the domain that the
records belong to.
The Task-Outage Relationship table is installed when administrator activates the optional
Task-Outage Relationship plugin.
