Using check in/check out

00:04

While info

00:04

works.

00:04

WS pro encourages its users to use the newer merge method for updating models.

00:10

It does still offer the lock method better known as check in, check out

00:15

while check in,

00:16

check out can quickly get messy with multiple

00:18

users making changes to the same model.

00:21

There are ways to convert them into models that can use the merge method.

00:24

Also known as the commit approach.

00:28

In this exercise in the model group window,

00:30

there is a model group called session 03 lock,

00:34

expand it and observe how icons beneath are a different color yellow.

00:39

From those you would see if you were using the commit approach,

00:43

click and drag the lock network into the workspace which opens the GEO plan

00:49

at the top of the window.

00:50

Notice that the R O in parentheses indicates that this is read

00:53

only meaning it cannot be edited until it is checked out.

00:58

Right? Click the lock network and select. Check out

01:02

in the new name, network dialogue.

01:04

The name of lock network number one is chosen by default

01:08

click. OK.

01:10

This creates a branching version of the file you can edit.

01:14

In this example,

01:16

a pipe's diameter is resized by opening its

01:18

properties in the branched version of the network

01:23

to check in the model, right? Click it again and click, check in

01:29

a small dialogue appears asking if you want to validate it.

01:33

Click, yes,

01:35

the check in comment, dialogue gives you the option to enter a comment.

01:39

But in this example, nothing is entered.

01:42

Click. OK.

01:44

Remember that once you check back in the new branch network,

01:47

it turns read only again and must be checked back out to make any additional changes.

01:53

Keep in mind that this process can become

01:55

quite messy such as if another user starts working

01:58

on the project and does not know what changes you have made or intend to make.

02:04

Therefore,

02:04

it is recommended that you use the newer commit approach as it

02:08

is more flexible when you make mistakes and it supports scenarios,

02:12

a valuable function of info works W S pro

02:15

whereas check in check out does not,

02:18

it is also possible to turn a check-in checkout model

02:22

into one that can be used with the commit method.

02:25

First delete any new networks you just created.

02:28

So only the original lock network remains

02:32

right, click session, 03 lock and select copy.

02:38

Then

02:38

right click the master database hover the cursor over advanced in the sub menu,

02:43

then select paste session 03 lock and convert to merge model.

02:49

The new commit model now appears in the model group window.

02:52

Any new branches that are checked in will appear below

02:54

as new versions of the model using the commit approach.

Video transcript

00:04

While info

00:04

works.

00:04

WS pro encourages its users to use the newer merge method for updating models.

00:10

It does still offer the lock method better known as check in, check out

00:15

while check in,

00:16

check out can quickly get messy with multiple

00:18

users making changes to the same model.

00:21

There are ways to convert them into models that can use the merge method.

00:24

Also known as the commit approach.

00:28

In this exercise in the model group window,

00:30

there is a model group called session 03 lock,

00:34

expand it and observe how icons beneath are a different color yellow.

00:39

From those you would see if you were using the commit approach,

00:43

click and drag the lock network into the workspace which opens the GEO plan

00:49

at the top of the window.

00:50

Notice that the R O in parentheses indicates that this is read

00:53

only meaning it cannot be edited until it is checked out.

00:58

Right? Click the lock network and select. Check out

01:02

in the new name, network dialogue.

01:04

The name of lock network number one is chosen by default

01:08

click. OK.

01:10

This creates a branching version of the file you can edit.

01:14

In this example,

01:16

a pipe's diameter is resized by opening its

01:18

properties in the branched version of the network

01:23

to check in the model, right? Click it again and click, check in

01:29

a small dialogue appears asking if you want to validate it.

01:33

Click, yes,

01:35

the check in comment, dialogue gives you the option to enter a comment.

01:39

But in this example, nothing is entered.

01:42

Click. OK.

01:44

Remember that once you check back in the new branch network,

01:47

it turns read only again and must be checked back out to make any additional changes.

01:53

Keep in mind that this process can become

01:55

quite messy such as if another user starts working

01:58

on the project and does not know what changes you have made or intend to make.

02:04

Therefore,

02:04

it is recommended that you use the newer commit approach as it

02:08

is more flexible when you make mistakes and it supports scenarios,

02:12

a valuable function of info works W S pro

02:15

whereas check in check out does not,

02:18

it is also possible to turn a check-in checkout model

02:22

into one that can be used with the commit method.

02:25

First delete any new networks you just created.

02:28

So only the original lock network remains

02:32

right, click session, 03 lock and select copy.

02:38

Then

02:38

right click the master database hover the cursor over advanced in the sub menu,

02:43

then select paste session 03 lock and convert to merge model.

02:49

The new commit model now appears in the model group window.

02:52

Any new branches that are checked in will appear below

02:54

as new versions of the model using the commit approach.

Video quiz

When you see, at the top of the GeoPlan, “R/O” in parentheses, what does this indicate?

(Select one)
Select an answer

1/1 questions left unanswered

Step-by-step Guide

While InfoWorks WS Pro encourages use of the newer merge method for updating models, it still offers the lock method, better known as Check In/Check Out. However, Check In/Check Out can get messy with multiple users making changes to the same model, so there are ways to convert them into models that can use the merge method, also known as the commit approach.

To use the Check-In/Check-Out method:

  1. In the Model Group window, expand the Session 03 -- Lock model group.

Notice the subgroup icons are a different color (yellow) than those for the commit approach.

  1. Drag-and-drop the LockNetwork into the workspace to open the GeoPlan.

At the top of the window, notice the R/O in parentheses to indicate the network is currently read-only, meaning it cannot be edited until it is checked out.

The InfoWorks WS Pro interface, Model Group window, with Session 03 – Lock expanded to show subgroups with yellow icons; and in the workspace, the network GeoPlan open with R/O in the title bar to indicate read-only.

  1. In the Model Group window, right-click LockNetwork and select Check Out.

The LockNetwork shortcut menu with Check out called out and selected.

  1. In the New Name – Network dialog box, leave the default name of LockNetwork#1.
  2. Click OK, creating a branching version of the file that you can now edit.

In this example, the diameter of a pipe is resized by opening its properties in the branched version of the network.

  1. In the Model Group window, right-click LockNetwork#1 and select Check in.

The network shortcut menu with the Check In option called out and selected.

  1. In the confirmation dialog box, click Yes to validate the model.
  2. In the Check In Comment dialog box, in the text box, enter comments, if necessary.
  3. Click OK.

Note: It is recommended that you use the newer commit approach, as it is more flexible when you make mistakes, and it supports scenarios.

To turn a Check In/Check Out model into one that can be used with the commit method, first, delete any newly created networks, so that only the original LockNetwork remains:

  1. In the Model Group window, right-click the newly created network, such as LockNetwork#1, and from the shortcut menu, select Delete.
  2. Click Yes to confirm.

Now, convert the model:

  1. Right-click Session 03 – Lock and select Copy.
  2. Right-click the Database and select Advanced > Paste: Session 03 – Lock and convert to merge model.

The Database shortcut menu with the Advanced flyout displayed and Paste: Session 03 – Lock and convert to merge model called out and selected.

The new commit model now appears in the Model Group window. Any new branches that are checked in will appear below it as new versions of the model, using the commit approach.

Was this information helpful?