This is an overview of domain separation in Planned Maintenance.Domain
separation enables you to 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*
The
support level is Standard but has some exceptions or special conditions.
- Includes Basic level
- 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 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.
How domain separation works in Planned Maintenance
There is no sys_domain column in the Maintenance Plan (sm_maint_plan) table. The application
cannot be exposed to customer fulfillers; however, the table is condition-based so there is some
limited support.
You can set maintenance plans to include or exclude domains or set them globally by design.
Support in the Part Requirements (sm_part_requirement} table is data only.
