Domain separation and Process Mining

  • Release version: Washingtondc
  • Updated February 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 Optimization

    Domain separation in Process Optimization allows for the logical grouping of data, processes, and administrative tasks into distinct domains. This setup helps control user access and visibility of data, ensuring that the application services are appropriately aligned with service provider use cases. The application supports domain separation in various aspects, including the user interface, cache management, reporting, and data aggregations.

    Show full answer Show less

    Key Features

    • Data Organization: Enables systematic separation of data and processes across multiple tenants.
    • Access Control: Allows for defining user access rights based on domain affiliation.
    • Process Flow Generation: Facilitates the creation of business process flows by analyzing audit trails to identify inefficiencies.
    • Project Configuration: All related entities for a process model are created within the same domain, simplifying management and visibility.
    • Scheduled Jobs: Jobs can only include project definitions that reside in the corresponding domain, ensuring domain-specific execution.

    Key Outcomes

    By implementing domain separation, ServiceNow customers can expect improved organization of data and processes, enhanced control over user access, and increased efficiency in business process analysis. This structure not only streamlines operations but also supports compliance with service provider requirements, ultimately leading to better service delivery and operational outcomes.

    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.