Push content to target branches

You can push objects, such as a topic and its content, to other target branches.

1. For source object you want to push, click (More options).
2. Select Manage Instance.
   The Push To dialog appears and lists all the branches in the Product or Library that do not have the source instance of the object:

   • Branches with a (Topic) and creation date have a different instance of the object that you want to push.
   • Branches without the icon and date do not have any instance of the object.

   The branches are organized by branch type.

   Note: If a branch is greyed out, you cannot currently push the source object to it. The reason a branch is unavailable is explained in the Push To dialog.

   You can push updates to another instance only if the source instance is at the same status as the target instance or the source instance is further along in its workflow. This prevents incomplete content from being pushed into completed objects.

3. Select the branches that you want to update.
   As you select branches, the bottom of the Push To dialog updates to summarize the actions that CCMS Web will take.

   You can only update one instance in target branches or share the source instance with other branches.

   If you pick a branch that already has an instance, you can then select only other branches that share the same instance.

4. Where updates are required, select Automatic or Manual at the bottom.
   You can update the instance automatically only if there are no potential conflicts.
5. Click Push.
   One of the following occurs:

   • If an instance of the object already exists in the target branch, the instance is updated automatically unless a manual update is required or you chose it.

     If this instance is shared with other branches that you did not select, the instance forks in the target branches.

     Note: Follow the steps below only if you must manually update objects or there are dependencies.
   • If an instance of the object did not exist in the Branch, the source instance is now shared with the selected Branches.
     Note: For maps, a new instance of the map is created because maps are never shared between Branches. Follow the steps below only if there are dependencies.
6. If the object has dependencies, choose one of the following actions:

   Scenario	Description	Steps
   Push Dependencies dialog appears	The Push Dependencies dialog explains if dependencies must be shared with the target Branches. Any target Branches that do not have a dependency must share the dependency with the source Branch. Note: Any dependencies that already exist in the other Branches are not updated during a push. You might want to push these dependencies later.	Click Continue. If you have any dependencies checked out, enter a comment and click Check in.
   Dependencies Preventing the Push dialog appears	There are dependencies, but some are checked out by other users. They cannot be checked in and shared, so the object cannot be pushed.	Click Back.

7. If you must manually update an instance, do the following in the Manual Update window:
   Important: If you cancel now, you cannot undo any forking actions performed earlier.
   1. To accept or reject a change, click one of the following.
      • Accept:
      • Accept All:
      • Reject:
      • Reject All:
   2. To manually make a change, edit the object in the Main Editing area.
      Note: You can access all the usual functionality in the editor for the object type, but you cannot manually change images.
   3. Repeat the steps as required to accept or reject all changes.
8. Add a comment for the instances that you manually updated.
9. Click Check in.
   The object is checked in, and the comment appears in its revision history.