You are here: Best Practices > Source Control and Versioning

Source Control and Versioning

OVERVIEW

ClosedWhat

Source control refers to the process of tracking changes across types of “source code” that can be used to generate the application. Versioning is a more general term that refers to keeping snapshot revisions of each major version of a particular resource. For more information, including a reference to many of the terms you will see here, see http://en.wikipedia.org/wiki/Revision_control.


ClosedWhy

Keeping track of changes, and why they were made, is important for any project. It supports:


ClosedWhere

You should use source control anywhere you have code. In addition, it is usually a good idea to keep all major versions of any other types of documents (for example, datasheets, contracts), especially if they are published or distributed in some form. CPQ Cloud does not have versioning built in, but there are a variety of other tools that you can use.


ClosedHow

The first step is to get a good version control system. There are a number of these, many of them free. If you have a standard within your organization, that is usually the best one to use. If you do not have a standard that your CPQ Cloud admins are already using, here are a few that you can try:

Next, you need some policies and guidelines. This is really dependent on your development procedures, but here a few recommended practices:


ClosedOther Solution Components

Some elements (for example, Attributes, Simple Rules) are not easy to put under version control because they are not expressed as text. In practice this rarely creates an issue, since these components are fairly simple to modify/delete/recreate, but if you are concerned about this, there are a few steps you can take:


NOTES

RELATED TOPICS

Related Topics Link IconSee Also