Getting Started With AuthorIT - instructional media + magic
Getting Started With AuthorIT - instructional media + magic
Getting Started With AuthorIT - instructional media + magic
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
56 <strong>Getting</strong> <strong>Started</strong> <strong>With</strong> <strong>AuthorIT</strong><br />
Making an Object Active<br />
When you create a new version of an object, that new version will be created as<br />
Inactive, or proposed. Once you have finished making changes to the new version you<br />
will want to make it the Active version.<br />
When you make an object the Active version, several things happen:<br />
The current Active object changes status to Redundant, and becomes read‐only.<br />
Any child relationships that the current Active version of the object was involved<br />
in are replaced with the new version, only where the parent in that relationship is<br />
not already Redundant.<br />
The new version of the object changes its status to Active.<br />
Example<br />
Lets look at an example where you have already produced version 1 of a Book and it<br />
is related to several Topic objects which are also version 1. Now you want to create a<br />
new version of the Book. However, only a few of the Topics need to be changed, and<br />
you still want the ability to publish the old version of the Book as it is.<br />
First you would create a new version of the Book object, and make that new version<br />
Active. This has the effect of making the old version Redundant.<br />
Next, you would create a new version of the Topic you wanted to change. After<br />
making the changes to the new version of the Topic, you would make that new<br />
version Active. Just like for the Book, the old version of the Topic would become<br />
Redundant. Additionally the relationship that the new Book has with the old version<br />
of the Topic now changes to be with the new version of the Topic. However, the<br />
relationship that the old version of the Book has to the old version of the Topic is<br />
retained, because the parent in the relationship (i.e. the old Book) was already<br />
Redundant.<br />
This replacing of relationships occurs automatically through the entire Library for the<br />
object version being made Active. This ensures that your changes are propagated<br />
through all the documentation in the Library.<br />
Effect of Version Status on Relationships<br />
The Version status of a object will affect its ability to be involved in a relationship.<br />
Only the Active version of an object can be involved in a relationship where it is the<br />
child. This is because the act of making an object Active automatically replaces the<br />
child relationship of the current Active version, with itself.