When creating a custom VCM merge type, what enumerated values are associated with each action in the custom.vcm.xml file?
When you create a custom VCM merge type with the Customize VCM tool in the Server Administration, a custom.vcm.xml file is created and each merge action is represented by an enumerated value which is shown in the following table.
|0||Ignore||Take no action
||Changes the revision to which the target is pinned to match the
||Moves the target item to the equivalent folder as the source item.|
||Merges the source and target items. The target item is modified
reflect the merged result.
||Deletes the target item.|
||Shares the source item to the target view.
||Moves the source item to the target view and share it back to
the source view.
||Overwrites the target with the contents of the source.
|66||MoveAndOverwrite||Equivalent to a Move followed by an Overwrite.
||Creates a merge point without modifying the target item so that
the two items previously in a merge condition are considered
resolved. The next View Compare/Merge session does not need to flag
it as a difference.
|6||Move and Merge
||Equivalent to a Move followed by a Merge.
|3||Move and Re-pin
||Equivalent to a Move followed by a Re-pin.
|40||Delete and Reverse Share
||Equivalent to a Delete followed by a Reverse Share.|
||Fail. View Compare/Merge cannot determine what action to take and will not commit changes while items are set to Fail. You must set failed items to another action, one that can be performed. Items with this action are found only in the Compare Perspective|
Not every action is valid for every item difference. For example, Delete is not valid when the target item is already deleted.