- Working with UCM activities
A UCM activity identifies the set of versions created during a specific development task. Every change to a resource in a UCM project must be associated with an activity.
- Checking out resources
Check out resources when you want to modify them.
- Checking in resources
Check in resources to commit your modifications to the repository (VOB).
- Canceling a checkout
Cancel a checkout if it was not needed or to discard your changes.
- Hijacking files
Hijack a file when you need to modify it when you cannot connect to a server.
- Canceling a hijack
Cancel a hijack if it was not needed or to discard your changes.
- Converting hijacked files to checkouts
You must convert hijacked files to checked-out files before you can check them in.
- Finding modified files
Use VersionVault Search to find files that have been checked out, hijacked, or that have not been added to source control.
- Deleting resources
You can use the VersionVault Navigator or VersionVault Details view to delete resources under VersionVault source control. On Windows systems, you can also perform this operation from Windows Explorer. The resources are not, in fact, deleted: they are only uncataloged from the current version of the directory and can be recovered from the predecessor version of the directory.
- Moving resources
You can use the VersionVault Navigator or VersionVault Details view to move resources under VersionVault source control. On Windows systems, you can also perform this operation from Windows Explorer. This operation affects resources (versions) in the local VersionVault view and elements in the VOB.
- Renaming resources
You can use the VersionVault Navigator or VersionVault Details view to rename resources under VersionVault source control. These operations affects resources (versions) in the local VersionVault view and elements in the VOB.
- Rebasing a UCM stream using Advanced Rebase
Rebase a UCM stream to update a UCM view with the set of versions selected by the parent stream's recommended baselines, or with a set of versions in baselines that you choose.
- Rebasing a UCM stream using Default Rebase
Rebase a UCM stream to update a UCM view with the set of versions selected by the parent stream's recommended baselines, or with a set of versions in baselines that you choose.
- Delivering UCM activities using Advanced Deliver
Delivering UCM activities makes your work available to other members of your team.
- Delivering UCM activities using Default Deliver
Delivering UCM activities makes your work available to other members of your team.
- Removing components
Use the Remove Component option in the VersionVault Details view to delete UCM components.
- Showing Pending Changes
Use the Pending Changes view to show and resolve all incoming and outgoing changes for the current view.
- Accepting incoming changes
In the Pending Changes view, you can accept incoming changes by performing a rebase operation.
- Integrate outgoing changes
In the Pending Changes view, you can integrate outgoing changes by performing a deliver operation.
- Synchronizing all changes
In the Pending Changes view, you can synchronize all changes by performing both a rebase and a deliver operation.
- Resolving all conflicts
In the Pending Changes view, you can resolve all conflicts by performing merges.
- Listing the history of a resource
List the VersionVault history of a resource to see comments and other metadata associated with changes to the resource.
- Using tools to compare and merge files and directories
With the HCL VersionVault Explorer you can compare or merge files and directories.
- Creating a new Compare/Merge provider
Use the Compare/Merge Providers preferences to create an external, 3rd-party, Compare/Merge Provider.
- Using a new Compare/Merge provider
Use the Compare/Merge preferences to specify a new Compare/Merge Provider.