Pushing object content among branches

You can push content from an object in a source branch to other target branches.

Determine whether you should automatically or manually push content from the source branch to a target branch.

  • If the target branch has a different instance of the object, that instance updates. You can choose to update it automatically or manually.

  • If the target branch does not have an instance of the object, the source branch shares the object with the target branch so that both have the same instance of the object.

Automatic and manual updating

When you push an object to update another instance,CCMS Web checks the instance in the target branch for recent changes.

If the target instance was modified more recently than the source object, there might be potential conflicts. You must manually update the instance in the source branch, then compare the two instances and decide which changes to keep or overwrite.

If there are no conflicting updates between the two instances, CCMS Web can automatically update the instance in the target branch. The two instances will have identical content.

If you perform a manual update, all future updates must be manual as well.

Note: You can choose to manually update an instance, even if an automatic update is allowed.

Dependencies of the object

If you push an object that has any dependencies, one of the following happens:

  • If an instance of the dependency already exists in the target branch, the dependency does not update.

    The object in target branch updates, but it will still refer to the instance of the dependency that already exists in that branch. If you want to update the dependencies in that branch, you must push each of them individually.

  • If an instance of the dependency does not exist in the target Branch, an instance of the dependency is shared with that branch.
    Note: A dependency cannot be added to the target Branch if it is checked out by another user. If you have it checked out, you can check it in during the push.
    Note: If the dependency is a submap, a new instance of the map is created in the target branch. Maps are never shared between branches.