Editing objects in DRM
In IXIASOFT Dynamic Release Management (DRM), when you edit some objects, you must decide if the changes are for some or all of the Branches that object appears in.
IXIASOFT CCMS Web keeps track of all the Branches objects are in. This includes topics, images, and ditavals. When you edit an object, you can choose whether to edit the object across all Branches or only some Branches.
If you choose to edit the object in only some Branches, then the object is forked. This means the object in Branches you did not edit remains the same, but a new instance of the object is created for all the Branches you want to make changes for. Two instances of the object now exist, and you can update them independently.
Unavailable Branches
In some cases, you cannot edit an object in all the Branches it appears in because one or more Branches are unavailable.
In this case, you can only fork the object. However, you can still choose which available Branches to fork in if the object is in more than one available Branch.
Branches can be unavailable for the following reasons:
- The Branch is closed
- You might not be able to edit the object due to Content Level Security
Assignments and forked objects
Assignments do not change when you fork objects that do not have context maps, such as images and ditavals. In these cases, the assignments on the original object are copied to the new instance. So if you were assigned to the original object, you are automatically assigned to the new instance. You would be assigned to both objects.