Behavior When Child (the Related Item) Is Versioned First

As previously, let’s consider first what happens when there is no life cycle state behavior set. Notice that even for Fixed behavior, Parent 2 is associated with Child2. This is true because of the following rule: When a source item is versioned, it is automatically associated with the latest available version of all its children. In this case, since Child 2 was previously created, instead of pointing to Child1, Parent 2 points to Child2.

The Life Cycle State behavior overrides the RelationshipType behavior. In the diagrams below, Fixed relationship acts like Float when in Float life cycle state, and the Float relationship acts as Fixed in the Fixed life cycle state.

When the RelationshipType Behavior is set to Hard Fixed or Hard Float, it overrides the Life Cycle State behavior. In the diagrams, the Hard Fixed behavior acts as Fixed, regardless of the life cycle state setting, and the Hard Float acts as Float regardless of the life cycle state setting.

If the RelationshipType Behavior is not set to Hard, it can be overwritten by the Life Cycle State Behavior. The figure below shows what happens when one generation of the parent is in one state, with one type of behavior, and the next state is in another life cycle state, with a different behavior.

Remember that if the Life Cycle state behavior to Hard Fixed or Hard Float, it will override all subsequent state behavior through the end of the cycle. This is particularly useful if a life cycle map with states that follow Released, such as Obsolete, or Superseded. Most likely once an item reaches a Released state users would want to Hard Fix its behavior, so that its configuration remains the same, even if the item is promoted to Obsolete or Superseded.