Cloning objects
Cloning an object creates an identical copy of the same object.
A clone is an exact copy of the existing object. The only difference between a clone and the original object is the clone has a new ID and filename. You can edit a clone to make any necessary changes or updates to the content.
Dependencies of the clone
A clone does not have identical dependencies to the original object. A clone is a new object with its own dependencies, however clones can start with dependencies that match those of the original object.
An example would be a clone of a topic that references the same images as the original topic, though other dependencies are not copied. The clone is not automatically referenced in all the same maps as the original topic, nor is the clone associated with Collaborative Reviews as the original topic.
Assignments and status for the clone
The clone is automatically assigned to the user who created the clone and set to active status for the user. For example, if a contributor cloned an object, the clone would start in Contribute status.
Clones in IXIA Dynamic Release Management (DRM)
Cloning is different from forking or pushing an object as clones are not different instances of the same object. Clones are considered to be new objects because they have new IDs and filenames, and are always in the same Branches as the original object. If you edit, fork, or push a clone, it has no impact on the original object.
Objects you can clone
You can clone many of the objects in IXIA CCMS Web, such as:
- Maps
- Topics
- Images
- Resources
- Ditavals