Viewing the Commit History
Every time you commit changes to the master database, the changes you made are recorded permanently. They are not overwritten when the next batch of changes are made. So the entire history of a version controlled item is available for review.
It is also possible to view the history of an individual network object.
Viewing the History of a Version Controlled Item
To view the commit history a version controlled item, use one of the following methods:
- Right click on the database item in the Explorer Window and choose Show commit history from the popup menu.
- If the currently active window is a Network or GeoExplorer, select Version control | Show commit history from the Network menu.
- If the currently active window is a Digitisation Template
- The Commit
History Dialog is displayed. There may be some delay before the dialog is displayed
as InfoWorks ICM downloads the history from the master database. On the
dialog you can:
View details of any previous commit, such as user id, number of changed objects and any comments made at the time. To do this, select one of the rows in the list and click the Details button. This displays the Commit Details Dialog where more detailed commit information is shown. Comments can be edited/updated after a commit operation has been performed. Please refer to the Commit Details Dialog topic for further information.
By default, the Commit History Dialog displays the most recent 100 commits applied to the network. To see the next 100 commits, click the Show more button. Click the Show all button to display all commits applied to the network.
- View the differences between two versions. Select two rows to view the differences between those two versions. Select one row to view the differences between that version and the current version, including any uncommitted changes. Then click the Diff button. See Comparing Version Controlled Items for more details
- Open a previous version of the database item. Select a row and click Open. InfoWorks ICM will retrieve the data from the master database and display a read only copy
- Create a branch. Select a row and click Branch. A new version of the network is created, based on the version of the selected network. See Creating a Branch for more details.
- Copy history to the clipboard. Select one or more rows, right click and choose Copy selected items to the clipboard from the context menu.
- Click Close when you have finished with the dialog.
Viewing the History of a Single Network Object
You can view the commit history of individual objects from the object
- Open the property sheet for the object. See Property Sheets for information on the various ways of doing this.
- Click the
Commit
History button on the property sheet toolbar. This displays
the Commit History Dialog. On
the dialog you can:
- view details of any previous commit, such as number of changed objects and any comments made at the time. To do this, select one of the rows in the list and click the Details button. This displays the Object commit details dialog where you can find details about what changes were made to the selected item in the master database during a single commit operation. Additionally, the Full history option of the Object commit details allows users to access the full commit history for the network object.
- view the differences between two versions. Select two rows to view the differences between those two versions. Select one row to view the differences between that version and your current version, including any uncommitted changes. Then click the Diff button. See Comparing Individual Objects for more details.
- view all the commits (scenario and base commits) for the selected network object if is in a scenario and has been modified from the base. To do this, enable the Show Base option. This option is disabled by default (only scenario commits are displayed by default).
- copy history to the clipboard. Select one or more rows, right click and choose Copy selected items to the clipboard from the context menu.
NoteAll base commits are displayed after scenario commits. The order in which commits are listed in the dialog is based on the order of precedence for scenario objects rather than in chronological order. Scenario commits always override base object commits.
- Click Close when you have finished with the dialog.
Please refer to the Commit History Dialog and the Object commit details Dialog topics for more detailed information.
