Behavior When Parent (the Source Item) Is Versioned First

Let’s first consider what happens when there is no behavior set on the life cycle state:

Notice that with the Float RelationshipType behavior, when Child2 is created, Parent1 still points to Child1. The reason for this is that when a new version of the Parent is created, the previous versions are then Hard Fixed in their current configuration. So, when Parent2 is created Parent1 is pointing to Child1. It remains in that state going forward, no matter how many times Child is versioned after that.

When the Life Cycle Behavior is set to Float, it forces even the RelationshipType defined as Fixed to act as Float. See the figure below.

When the Life Cycle Behavior is set to Fixed, it forced even the RelationshipType defined as Float to act as Fixed. See the figure below:

When the RelationshipType is defined as Hard Fixed or Hard Float it overrides whatever the behavior is set by the Life Cycle state. Notice the two figures below showing that the behavior defined by the RelationshipType rules the behavior, regardless of the behavior defined by the Life Cycle state.

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.

So far, we have been looking at all these cases with the assumption that the Parent or the source item is versioned first. Now, we need to examine all the same cases, but with the Child or the Related item versioned first.