Making an Object Active

When you create a new version of an object, that new version will be created as Inactive, or proposed. Once you have finished making changes to the new version you will want to make it the Active version.

When you make an object the Active version, several things happen:

• The current Active object changes status to Redundant, and becomes read-only.
• Any child relationships that the current Active version of the object was involved in are replaced with the new version, only where the parent in that relationship is not already Redundant.
• The new version of the object changes its status to Active.

Example

Lets look at an example where you have already produced version 1 of a Book and it is related to several Topic objects which are also version 1. Now you want to create a new version of the Book. However, only a few of the Topics need to be changed, and you still want the ability to publish the old version of the Book as it is.

First you would create a new version of the Book object, and make that new version Active. This has the effect of making the old version Redundant.

Next, you would create a new version of the Topic you wanted to change. After making the changes to the new version of the Topic, you would make that new version Active. Just like for the Book, the old version of the Topic would become Redundant. Additionally, the relationship that the new Book has with the old version of the Topic now changes to be with the new version of the Topic. However, the relationship that the old version of the Book has to the old version of the Topic is retained, because the parent in the relationship (i.e. the old Book) was already Redundant.

This replacing of relationships occurs automatically through the entire Library for the object version being made Active. This ensures that your changes are propagated through all the documentation in the Library.