This is an overview of domain separation and . 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: 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. This includes domain
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.
Use case: When a service provider (SP) uses chat to respond to a tenant-customer’s
message, the client must be able to see the SP's response.
Overview
- Using Service Desk Call, ITIL users can create a call record and quickly capture basic
information from a customer contact. Users can then decide if the call is an incident, a
problem, a change, or a service catalog request.
- Service Desk personnel can process customer calls more quickly by retaining and reusing the
information captured during the call. Users with the ITIL role can read, create, and edit an
existing call, but cannot delete existing calls or edit a call after it is transferred.
- At the end of the call, the ITIL user can decide one of two actions to take:
- Transfer the call record to an incident, problem, change, or service catalog
request.
- Record the call as another type of contact, such as a wrong number.
- Typically, ITIL users create the new_call (Service Desk) records when they receive a call
from ESS user. Once they understand the nature of the issue, the new_call record is converted
into a corresponding incident, request, problem, change, and so on.
- The [new_call] table supports domain separation. Therefore, an ITIL/Fulfiller sees only
those new_call records that have been created within the (tenant) domain that they belong
to.
How domain separation works in Service Desk
ITIL/Fulfillers see only those new_call records that have been created within the (tenant)
domain that they belong to.
Domain separated tables
Use cases
- An ITIL/Fulfiller creates new_call records only in those domains to which they have
access.
- When a new_call record is converted into a Request / Incident / Problem / Change, and so
on, the corresponding record is created in the same domain as that of the associated new_call
record.
- An ITIL/Fulfiller can create a new_call record only for those callers who belong to the
domains to which they have access.
