Version Control

Manage the changing versions of AADvance
elements including projects, libraries, controllers, programs, functions, and function blocks by saving these to a version control repository. Saving these elements to a control repository enables multiple users to work on the same solutions and project elements at the same time and retrieve older versions of elements at a later time.

The version control automatically checks in elements to the version control repository upon performing the following operations:

Creating a project

Downloading code to targets

Updating targets

Such automatic check-ins ensure that the code located on a target always has a corresponding version stored in the version control repository. When a user performs one of these operations for a project or an element while others also have elements checked out, the user performing the operation steals the locks from the other users. Modifications performed on such elements by the original lock holder are no longer available for committing.

When modifying elements, automatically check out elements then check in these modifications.

From the repository, check out elements for exclusive access when making modifications. Also, upon modifying checked-in elements, these elements become checked out for exclusive access. Afterwards, check in modifications performed on these elements into the repository. When checking in elements, choose to recursively check in all sub-elements to the repository.

When deleting, renaming, and adding elements, check out the parent of that element.

Element	Parent
Program, Function, Function Block	Controller, Library
Controller	Project
Library	Project

When retrieving, for example updating, an AADvance element from the repository, choose to update this element to the latest version or any specific version previously checked in to the repository. When getting the latest version, recursively replace all sub-elements from the repository. When retrieving a specific version from the version control history, the local element and its sub-elements revert to those from the version control. For controllers having been renamed, retrieve the required version from the controller history; the required controller version from the project history cannot be retrieved.

TIP: When a controller has been renamed, execute the View History
command on the most recent version of the controller.

From the Application View
, view the version control status for all elements. From the Communication View
and Equipment View
, view the version control status for projects and controllers.

	Available element where local version is the same as the version in the repository
	Available element where local version differs from the modified version in the repository
	Available element where locally modified version differs from the version in the repository
	Locked element currently checked out by another user where local version is the same as the version in the repository
	Locked element currently checked out by another user where local version differs from the modified version in the repository
	Locked element currently checked out by another user where locally modified version differs from the version in the repository
	Checked out element where local version is the same as the version in the repository
	Checked out element where locally modified version differs from the version in the repository
	New element not yet checked in to the repository