rename-rename-checkout-edit => renegade

[Thomas Linder Puls]

This sequence of operations:

• Rename a folder
• Rename a file in the renamed folder
• Check-out the renamed file
• Edit the file

Makes the file renegade, rather than edited.

This sequence (giving the same end result) works:

• Rename a folder
• Check-out a file in the renamed folder
• Rename that file in the renamed folder
• Edit the file

I think other permutations also works, the only thing that gives problems is checking out a renamed file in a renamed folder.

[Tonya]

Do you have the "auto commit" option disabled? If so, the rename of the Folder has not been yet been committed to the Vault server. The Vault server thinks the renamed file is in the old working folder which puts the file in a renegade status. When renaming folders, we recommend to always commit after the rename.

Tonya

[Thomas Linder Puls]

Yes, auto-commit is off. If we commit after rename the files will be in an inconsistent state, because the files contains include directives that involves themselves. To get from one consistent state to another we will need both to perform the renames and update the include directives. Furthermore, the files and the folders have to (by convention) have matching names.

So we really prefer to perform the operation in one commit.

Furthermore, Vault acts as if it supports the operation.

[Tonya]

I apologize for the inconvenience. I should have specified that I have logged this issue. For future references, please refer to V: 19963. This appears to be an issue that was created in a previous Vault version and has not yet been reported until now.

The only work around I was able to come up with was to check in the folder immediately after the rename. Then the rest of your operations should go accordingly.

Tonya

[Thomas Linder Puls]

Thank you.

[Tonya]

You're welcome.

Tonya