Domain separation and Digital Product Release

  • Release version: Australia
  • Updated March 12, 2026
  • 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 capability is essential for controlling user access and visibility to data, ensuring that each tenant can operate independently within a shared instance.

    Show full answer Show less

    Key Features

    • Domain Awareness: Application properties are designed to recognize and operate within specified domains as necessary.
    • Business Logic Configuration: Service providers can tailor processes based on customer needs, ensuring proper application use across multiple tenants.
    • Domain Field: Each table in Digital Product Release includes a domain separation field called 'Domain', which is crucial for implementing domain separation effectively.

    Key Outcomes

    With domain separation, the instance owner can configure tailored business logic and data parameters for each tenant. For example, an administrator may require comments upon record closure for one tenant but not for another. This flexibility enhances the user experience and operational efficiency within the Digital Product Release application.

    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.