Understanding version control systems

Step-by-step Guide

Before using InfoWorks WS Pro, it is important to understand how its version control systems work. There are two methods for managing version-controlled objects: the lock method and the merge method.

The lock method is the legacy version control system, better known as “Check In/Check Out.” In this version control system, objects are locked for editing until you  “check them out” to work on them.

Using the lock method, version-controlled objects include:

• GeoExplorers
• networks
• alternative demand objects
• controls
• live data configurations
• digitization templates
• IWLive baselines

In the lock method, before changing a version-controlled object, it must be checked out; however, newly created objects are checked out automatically. Then, for as long as an object is checked out, no one else can change it. When finished working on the object, it must first pass verification, and then be checked back in.

IMPORTANT:

• The lock method will only apply to version-controlled objects when the merge method is not selected.
• There is no revision history with the lock method.

The merge method is present in newer versions of InfoWorks WS Pro. This version control supports multi-user editing and scenarios, and it offers full revision history.

Using the merge method, most of the same objects can be version-controlled, except for IWLive baselines. Merge version control is automatically assigned to a database. If you wish to use the lock method, it must be switched on in the database settings.

IMPORTANT:

1. You can get other users’ changes at any point in the workflow, even while making your own changes.
2. Committing changes to the database allows other users to see them.
3. You can resolve conflicts between what you and others have committed.