Branch topics, images, or resources
This procedure describes how to branch one or more topics, images, or resources.
The object to branch must already exist in that version before you can branch it. Also, an object cannot be branched in its primary version. For example, consider a topic that exists in 3 versions: 4.1, 4.2, and 4.3. Version 4.1 is the topic's primary version. When you branch the topic, you have the option of branching it to versions 4.2 and 4.3 only.
When you branch an object, IXIA CCMS does not branch the object's children. For example, if you branch a topic that includes images, the CCMS creates a new topic with the exact same content as the source topic, so both topics reference the same images.
If the parents of the object are in a closed version when you branch the object, all the parent objects will also be branched to the new version. This is because the parent of an object cannot be in a higher status than the child object. For example, a topic cannot be at the Authoring:done status if the image referenced in the topic is in Authoring:review. When you create a new instance of the object, it is created in the new version with a "work" status (or its equivalent in your workflow). When this occurs, the change in status for the object would cause a change in status for the parent objects and in the case of a closed version this is not possible. So, for example, if you branch an image from a closed version to a new version, all the topics that reference that image, and all the maps that reference those topics are also branched to the new version with a "work" status.
Important
When a topic is first created or imported into the CCMS with DRM, the filename and the id match. If a new instance of that topic is created, the id remains the same as the original, but the filename is different. Just as you cannot have two files with the same name (and extension) in a Windows directory, for example, you cannot have two objects with the same file name in the CMS repository. However, two or more objects can have the same id. In a DRM version container, the key name is the object’s id and the key href is the object’s filename. If the id remains the same for all instances of the object, it is much more straightforward to keep the same keys defined from version to version, but simply pointing to new filenames (instances) as appropriate. |
To branch one or more topics, images, or resources: