Working with Serena Version Manager (CM tool integration)
* 
CM tool integration support for Serena Version Manager is being deprecated.
The topics that document the CM tool integration in this help are generic using Microsoft Visual SourceSafe terminology. The following notes apply when working with Serena Version Manager.
After performing a get latest operation, the message in the Modeler Output pane mistakenly states that a check out operation has been performed.
If you check out a Package, rename that Package in Modeler, and then check in that Package, the file name of the Package in the CM tool environment will reflect the original name of the Package, not the new name.
When installing Version Manager clients, we recommend that each client uses the same drive and path mapping for Version Manager. Failure to do so will not prevent Version Manager from working correctly, but it can result in the following problem; if a user checks in a Package and another user with a different drive mapping views that Package, the Package icon will not have an arrow, and the Check In command will not be available. To overcome this problem, the user will have to reconnect the Package using locally stored paths.
Was this helpful?