Domain separation and Digital Product Release

  • Release version: Zurich
  • 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 you to organize data, processes, and administrative tasks into distinct logical units known as domains. This feature enables fine control over user visibility and access to data across different domains, ensuring data integrity and security in a multi-tenant environment.

    Show full answer Show less

    Key Features

    • Domain Separation Support: All tables in Digital Product Release are equipped with a domain separation field, facilitating the management of separate data environments.
    • Standard Support Level: This includes all aspects of Basic level support, ensuring application properties are domain-aware where applicable.
    • Customizable Business Logic: Service providers can tailor processes for each customer, allowing for specific configurations that reflect different tenant needs.

    Key Outcomes

    By implementing domain separation, customers can efficiently manage multiple tenants within a single instance of Digital Product Release. For example, an Admin can require comments for record closure in one tenant while not enforcing this in another. This flexibility supports diverse operational requirements and enhances user experience across domains.

    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.