Modifying Objects > Object Attributes and Properties > Propagating Harness Attributes by Connectivity

Connectivity Set

When you specify a harness attribute value on an object, the system identifies the connected conductor (or conductors if a multi-term exists) and the objects at both ends of the conductor to complete the connectivity set.

A connectivity set can be comprised of a conductor and any combination of the following connected objects:

Objects Plugs

Jacks

Splices

Inline half

Devices (directly connected to a conductor) Note Device connectors are not part of a connectivity set. If a harness value is added to a device connector, it will not trigger propagation or display on the Propagate Harness tab.

Ring Terminals

Grounds

Conductors Wires

Nets

Highways

Multicores

Overbraids

Modified Objects	Connectivity Set	Example
H1 added to connector P119.	Connector P119 Inline half J1 WIRE30
H2 added to connector P119.	Connector P119 Connector P120 WIRE30 WIRE31
H3 added to WIRE32.	Connector P119 Connector P120 Connector P121 WIRE30 WIRE31 WIRE32
H2 = Connector P119 and poke home WIRE30. H4 added to connector P120.	Connector P120 Poke home WIRE30

Note

If you change the harness attribute value on a connector that has a poke home wire terminating at it, a warning is displayed on the Propagate Harness tab, to identify that connected objects will be affected, if you change the harness attribute on the wire.

You can propagate harness attribute values to one or more objects in the connectivity set, and use the “Missing or conflicting harness attribute” Design Rule Check, to ensure that the values are consistent.

Shared Objects in Connectivity Sets

If you modify the harness attribute value on a shared object, the system identifies the impact to all the objects that are connected to the shared object in the other connectivity sets on the diagram and across the designs.

If you propagate harness attribute values to shared objects that exist in other designs, the current open diagram is not saved automatically. However, the values on the shared objects and all the objects in the connectivity sets in the other designs, are updated and saved.

The Propagate Harness Tab displays warnings and information, to enable you to decide whether to propagate the values to all the impacted objects across all the connectivity sets. See Using the Propagate Harness Tab.

Restrictions when Propagating Shared Objects

The following restrictions apply if propagating through shared objects to the connectivity in other designs:

If there is an active build list, values will only propagate to the designs in the build list.
If there is no active build list, values will propagate to all designs.
Harness attribute values will not propagate through shared objects, if a design is locked for the following reasons: The design or a shared object in the design is restricted by Domain Access.

Read-only for any other reason, such as locked by another user.

If the following restricted objects are identified in other designs, the propagation in this design is stopped, and the objects are not updated. Restricted by domain access or license policy.

Locked or frozen.

If objects with multiple harness attribute values, or existing poke home wires are identified in a design, the propagation in this design is stopped, and the objects are not updated. Note To find objects that have not been updated, you can use the “Missing or conflicting harness attribute” Design Rule Check (DRC).

Example Impact to Multiple Designs

Multiple designs can be impacted when you propagate harness attribute values on shared objects. The following example describes how designs can be impacted indirectly by connectivity, when you modify a shared object:

Design 1 — SO1 (Shared Object 1).
Design 2 — SO1 connected to SO2.
Design 3 — SO2 connected to SO3 and so on.

If you propagate the harness attribute values to SO1, all the objects that are connected to the shared object in the connectivity sets on the diagram and across the designs are updated.

If the other connectivity sets also contain shared objects that are in multiple designs (SO2), the connectivity sets can increase across the designs.

SO1 is updated in Design 1.
SO2 is updated in Design 2 because it is connected to SO1.
SO3 is updated in Design 3 because it is connected to SO2.

Design 3 is impacted indirectly, even if it does not contain objects connected directly to SO1.

Design-Wide

Objects in Connectivity Sets

Connectivity sets can include objects on multiple diagrams in the same design, if you create design-wide instances of objects on different diagrams.

If you modify the harness attribute value on a design-wide object or objects connected to it, the system identifies the impact to all the objects in the connectivity sets that include the instances of the design‑wide object.

In this example:

The design-wide instance of a connector is connected to five objects on Diagram 1, and four objects on Diagram 2 in the same design.

If you update a harness attribute value in any of the connectivity sets, the total number of impacted objects listed on the Propagate Harness tab will be nine. Five from Diagram 1 and four from Diagram 2.

Parent Topic:

Propagating Harness Attributes by Connectivity