Domain separation and Process Mining

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Domain separation and Process Mining

    Domain separation in Process Mining allows ServiceNow customers to logically segment data, processes, and administrative tasks into distinct domains. This enables controlled access where users see and interact only with data relevant to their domain, supporting multi-tenant environments commonly used by service providers. Process Mining itself helps analyze business process flows by monitoring audit trails to identify inefficiencies and improve outcomes.

    Show full answer Show less

    Key Features

    • Domain Separation Support: Process Mining supports domain separation at runtime, including separation in the user interface, cache keys, reporting, rollups, and aggregations.
    • Domain Assignment: All entities related to a process model (e.g., activity definitions, breakdowns, extract logs, CIM initiatives) are created within the same domain as the process model definition.
    • Project and User Domain Alignment: When creating a project or related entities, they are assigned to the current user's domain to maintain consistent domain boundaries.
    • Sharing and Access Controls: Projects can be shared within their own domain or with users in the global domain, enabling flexible access while maintaining separation.
    • Process Mining Scheduled Jobs: Scheduled jobs operate only within their domain and can include project definitions from that domain exclusively.
    • Support Level: Basic support for domain separation is provided, focusing on ensuring data is properly segregated for service provider use cases.

    Practical Use Cases

    • Multi-Tenant Service Providers: Allows a service provider’s response in chat to be visible only to the appropriate tenant customer, maintaining data privacy across tenants.
    • Domain-Specific Project Access: Users in a domain, their parent domain, or the global domain can view projects or scheduled jobs created in that domain, facilitating hierarchical access control.
    • Domain-Restricted Job Configuration: Scheduled jobs can only include projects that belong to their own domain, ensuring process execution respects domain boundaries.

    Important Considerations

    • Cascade domain changes are not supported; domains must be carefully assigned at creation.
    • Instance owners are responsible for configuring the application to function correctly across multiple 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

    1. 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.
    2. 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.
    3. 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.