Child Design Domain Inheritance

You can set a project preference so that the domain configured for a composite/modular parent design is automatically inherited by its child designs. This ensures that any domain controlled read/write design access is the same for parents and their children.

When you turn on the project preference “Inherit domain of child design from composite design”, the Domains assigned to all parent designs in the project are automatically assigned to all of their child (derivative, functional module, or production module) designs as follows:

• If the child design is linked to only one parent design, its domain is inherited from that parent.

• If the child design is linked to multiple parent designs: Child designs with the Release Level Type of “Released”, inherit the domain of the latest created parent design with a Release Level Type of “Released”.

Child designs with the Release Level Type of “Draft”, “Pending”, or “Obsolete” inherit the domain of the latest created parent design with a Release Level Type of “Draft”, “Pending”, or “Obsolete”.

Note If a child design has a Release Level Type of “Released”, where the configuration of “Released” has Harness Processing or Modular Processing behaviors selected (see Release Level Behaviors), the rules treat the child design as if it has a Release Level Type set to “Draft”, “Pending”, or “Obsolete”.

Such inherited domains display as read-only on the New Derivative Harness Design dialog box and Edit Design dialog box.

Inaccessible designs due to domain restrictions are filtered from the design browser tree. Access to such child designs is controlled by your user account domain access settings, configured in Capital Access Manager.

Note

Editing access to child designs is unavailable under these conditions:

• The child design has inherited a domain to which you have access, but was previously assigned a domain to which you do not have access.

• The child design has inherited a domain to which you do not have access, but was previously assigned a domain to which you did have access.

In this example, the child designs are only linked to one parent (COMPOSITE 1 rev 1) and inherit its domain.

Figure 16: Domain Example 1

In this example the child designs are linked to multiple parents and inherit the domain of the draft parent (COMPOSITE 1 rev3).

Figure 17: Domain Example 2

In this example, the child designs are linked to multiple draft parents and inherit the domain of last created draft parent (COMPOSITE 1 rev3).

Note

This use case describes an invalid scenario. Child designs should not be controlled by two draft parents.

Figure 18: Domain Example 3

In this example, released child designs are linked to multiple released parents and inherit the domain from the last created released parent (COMPOSITE 1 rev3).

Figure 19: Domain Example 4

Parent Topic:

Harness Designs

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens