Domain separation and Digital Product Release

  • Release version: Xanadu
  • Updated June 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 Digital Product Release

    Domain separation in Digital Product Release allows for the organization of data, processes, and administrative tasks into distinct domains. This feature enables customers to manage visibility and accessibility of data based on user roles and domain configurations.

    Show full answer Show less

    Key Features

    • Support Level: Standard support includes all Basic level support features. Application properties are designed to be domain-aware as required.
    • Business Logic: Service providers can create or modify processes tailored to different customers, ensuring appropriate application use across multiple tenants within a single instance.
    • Domain Separation Field: Every table in Digital Product Release comes with a domain separation field named "Domain," which is essential for configuring domain separation effectively.

    Key Outcomes

    Customers can expect to implement domain separation that allows for tailored business logic and data management for different tenants. For example, an admin can enforce specific requirements, such as mandatory comments upon record closure, for one tenant while allowing flexibility for others. This customization enhances the overall functionality and user experience within Digital Product Release.

    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.