Domain separation and Service Exchange (legacy)
Domain separation is supported for Service Exchange. 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
Domain separation is available only for the Provider Request [sn_nowebonding_remote_request] table and not to any of the configuration tables in the application.
How domain separation works in Service Exchange
- Only the Provider Request [sn_nowebonding_remote_request] table in the application can be domain-separated.
- Make sure that the customer company and account tables are associated to the right domain for the domain separation logic to work.
Use cases
When providers have their customer data separated by domains, the provider requests and corresponding fulfillment tasks are associated with the respective customer domains.