Version Control Usage

The version control facility can be used in many different ways, although these roughly fall into one of four types of use as discussed here.

Usage

Type

Usage

See also

Single Shared model

Users share a model stored in a central project file or DBMS repository. In this configuration you can view changes to other users' Packages without explicitly having to check them out, by simply refreshing your view of the model.

Version control is used to:

Archive successive versions of your work to date
Maintain Package revision history
Recover from unwanted changes or accidental deletions, through an 'undo' facility
Regulate access to Packages

 

 

Multiple Private models

One model is created by a single user who configures it for version control. The model file is then distributed to other users, with each user storing their own private copy of the model.

Version control is used to:

Propagate changes to the model, throughout the team
Archive successive versions of your work to date
Maintain Package revision history
Recover from unwanted changes or accidental deletions, through an 'undo' facility
Regulate access to Packages

 

 

Shared Packages

Individual users create separate models but share one or more Packages:

Users share Packages through version control

 

 

Standard Packages

A company might have a standard set of read-only Packages that are broadly shared:

Individual users retrieve Packages with the Get Package menu option

 

 

Learn more