Domain separation and Process Mining

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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

    Process Mining in ServiceNow enables you to analyze business process flows by monitoring audit trails and assessing process effectiveness. This helps identify inefficiencies and improves business outcomes. Domain separation within Process Mining allows you to logically segment data, processes, and administrative tasks into distinct domains. This segmentation controls user access and visibility of data, ensuring secure and organized multi-tenant environments.

    Show full answer Show less

    How Domain Separation Works in Process Mining

    Each Process Mining project and its related entities (such as activity definitions, data logs, filter sets, and CIM initiatives) are assigned to the same domain as the project definition. When creating a new project, the domain is set based on the current user's domain. Entities created under a domain-separated project automatically inherit that domain assignment.

    Projects can be shared within their own domain or with users in the global domain. Scheduled Process Mining jobs are restricted to include only project definitions within their own domain. Additionally, projects launched from Performance Analytics KPIs and CIM initiatives created from Process Mining workspaces align with the respective domain of the initiating user or project.

    Practical Use Cases for ServiceNow Customers

    • Users in a specific domain (e.g., ACME domain), their parent domain, or the global domain can view project definitions and scheduled jobs tied to that domain.
    • Scheduled jobs created in a domain can only include project definitions from the same domain, ensuring data separation and security between tenants.
    • Support for domain separation facilitates service providers’ scenarios, such as ensuring tenant customers see responses from their service providers while maintaining data isolation.

    Important Considerations

    • The instance owner is responsible for configuring the application to function across multiple tenants using domain separation.
    • Domain separation applies to multiple system components, including user interfaces, cache keys, reporting, rollups, and aggregations.
    • Cascade domain changes are not supported, so domains must be managed carefully when assigning or modifying entities.

    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.