Domain separation and Digital Product Release

  • Release version: Yokohama
  • Updated July 31, 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 Digital Product Release

    Domain separation in Digital Product Release allows customers to manage data, processes, and administrative tasks in distinct logical groupings known as domains. This feature enhances data visibility control by determining which users can access specific data within the application.

    Show full answer Show less

    Key Features

    • Domain Awareness: All application properties are tailored to be domain-aware, ensuring that they function correctly across different domains.
    • Business Logic Customization: Service providers can create or adjust business processes according to customer needs, allowing for tailored use cases in a multi-tenant environment.
    • Domain Field: Every table in Digital Product Release includes a domain separation field, enabling effective configuration of domain separation during implementation.

    Key Outcomes

    By utilizing domain separation, administrators can customize functionalities such as requiring comments for record closures based on tenant specifications. This flexibility ensures that each tenant's unique requirements are met while maintaining a single instance of the application for multiple service providers.

    Domain separation is supported for Digital Product Release. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

    Support level: Standard

    • Includes all aspects of Basic level support.
    • Application properties are domain-aware as needed.
    • Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
    • The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application.

    Sample use case: An admin must be able to make comments required when a record closes for one tenant, but not for another.

    For more information on support levels, see Application support for domain separation.

    Overview of domain separation in Digital Product Release

    All tables in Digital Product Release can be domain-separated and include the required domain separation field.

    How domain separation works in Digital Product Release

    • Each table in Digital Product Release includes the domain separation field called Domain.
    • Customers can use this field to configure domain separation in their implementation of Digital Product Release.