A UCM project manager can create element types that have a mergetype of user. For a delivery (or a rebase) operation in the graphic user interface (GUI), the processing of versions whose elements have a mergetype of user allows the user options to handle the merge. By definition, versions whose element has a mergetype of user cannot be automatically merged. If a version whose element has a mergetype of user is detected, a new window opens and lets you determine how to handle the version or all such versions.
If a version that has been created as a result of a deliver (or a rebase) operation cannot be automatically merged with an existing version in the target stream (for a delivery or a rebase) and the element has a mergetype of user, a window titled Deliver User Mergetype Element (or Rebase User Mergetype Element) opens. A field in the window shows the path for the version that cannot be merged automatically. Under Please choose one of the following options, the following options are shown:
Set this option to have the version in the source view copied to the target view and have the merge arrow created. The version is considered merged (status is set to Yes).
Set this option to maintain the version that is currently checked out and have the merge arrow created. The version is considered merged. Use this option after you use Skip this element, merge later or manually.
Set this option to omit processing this version. The version is not considered merged. You have to create the proper version in the target stream, run the deliver (or rebase) operation again, and set Keep the version currently checked out on the target stream to have the version considered merged.
Set this option to cancel the deliver (or rebase) operation and undo all changes made.
After you set one of the options, you have the following choices: