Domain separation and Process Mining
Summarize
Summary of Domain separation and Process Mining
Domain separation in Process Mining allows you to organize data, processes, and administrative tasks into distinct domains. This separation enables control over user access and visibility of data, ensuring that each service provider (SP) can manage its tenant-customer interactions effectively.
Show less
Key Features
- Support for Domain Separation: This feature is integrated at runtime, affecting user interface, cache keys, reporting, and data aggregations.
- Configuration: Project entities related to a process model are created within the same domain as the model definition, ensuring consistency.
- Project Sharing: Projects can be shared within their domain or with users in a global domain.
- Scheduled Jobs: Process Mining scheduled jobs can only include project definitions from the corresponding job's domain.
Key Outcomes
With domain separation, you can efficiently manage projects and scheduled jobs based on user domains, leading to improved data integrity and process efficiency. Users within the same domain as a project can view and interact with its details, while maintaining necessary data separation across different tenants.
Domain separation is supported in Process Mining. 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: 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 of Process Mining
Process Mining provides a way to generate business process flows from monitoring audit trails and analyzing effectiveness, so you can quickly discover inefficiencies in your processes. This allows in-depth analysis of business processes for improving outcomes.
How domain separation works in Process Mining
A project is configured to generate the process flow. All entities related to a process model definition, such as activity definitions, breakdown definitions, child table definitions, extract data logs, filter sets, notes, and CIM initiatives are created in the same domain as the process model definition.
When you create a new project definition, you set up its domain in the current user’s domain. Since you place all related entities for a model definition so they reside in the same domain, when you then create a related entity for a domain separated project definition, the entity is assigned to the project definition’s domain.
You can share a project with its own domain or with global domain users.
A Process Mining scheduled Job can include project definitions within the corresponding job’s domain only.
A project definition launched from Performance Analytics KPI is created in the current user’s domain.
A new CIM initiative added from a Process Mining workspace is created in the project definition’s domain.
Use cases
- Project definition created in the ACME domain: A user belonging to the ACME domain, its parent, or the global domain, can view the project definition.
- A Process Mining scheduled job created in the ACME domain: A user belonging to the ACME domain, its parent, or the global domain, can view the Process Mining scheduled job.
- A Process Mining scheduled job created in the ACME domain: A user can include only a project definition belonging to the ACME domain.Note:Cascade domain changes are not supported.