About Base VersionVault

Unstructured access to VersionVault tools is provided by base VersionVault.

When using base VersionVault, developers work directly with branches and versions of file and directory elements. Project managers can use branching rules, labels, and triggers to guide development efforts and create project policies, but base VersionVault does not require the use of any particular development methodology.

Unlike UCM, which requires the project leader to create a project before developers can begin work, base VersionVault requires only that at least one VOB be accessible to the VersionVault Server. Any VersionVault user who has access to the VOB can work with resources the VOB contains or add new resources to it.

When developers use base VersionVault, they do not need to join a UCM project. They need only create a base VersionVault view. After they have created a view, they can use the default configuration (which selects the latest version on the main branch of each element), use an existing configuration, or create their own. When the view has been created and the configuration is set, users establish load rules that specify which files and directories are loaded from the VersionVault Server and then update the view to load the selected versions. When the view has been updated, users can begin work.