After promoting a file, it is not moved to the location where it was moved in the child view

0 Likes

Problem:

After promoting a file, it is not moved to the location where it was moved in the child view

Resolution:

Description:
User has a parent view (View A) and a child view (View B). User modifies File A in View B (causing the file to branch), and then moves the file from Folder A to Folder B also in View B. User performs a VCM promote from View B to View A. The merge action for the file states "Moved and modified in source, target on different branch". When the promote is committed File A in View A gets a new revision, but it does not get moved to the location to which it was moved in View B. Why is this the case?



Answer/Solution:
The policy with moves and default actions is: if the source and target are on the same branch, the default action includes "Move". If they are on different branches, the default action does not include "Move".

This decision was made when the decision table for the possible merge actions was designed. So, the contents are merged, but the file is not refactored. This would be desirable in many object oriented applications.

Old KB# 29819
Comment List
Related
Recommended