Do you want to create the new branch?

Your view may be set up to create a new branch for this element. If so, do you want to create the new branch?

Checking out a version of an element creates a placeholder for a new version on a specific branch, as illustrated below.

You (or your project manager) can set up the config spec for your view to create versions of elements on a new branch automatically. This is common if your project collects all of its changes on a specific branch and this is the first time you check out an element for a project.

However, from the Version Tree Browser (and by using the -version option of the cleartool checkout command), you can override this behavior and force a new version of the element to be created on the current branch. The table below describes the actions taken when you select Yes or No at the Version Tree Browser prompt.

Config Spec Rule	Selecting Yes	Selecting No
If your view is set up to create a new branch...	A new branch is created and a placeholder for the version is created on the new branch. (See the illustration above.) When you check in the version, it becomes version 1 on the new branch.	A placeholder for the new version is created at the end of the current branch. No new branch is created. If the version you check out is not the latest on the current branch, when you check in the version, you must merge your changes with the latest version.
If your view is not set up to create a new branch...	If the version in your view is not the latest on the current branch, the latest version on the current branch is checked out. If you work in a snapshot view, the checked-out version is loaded into your view.	A placeholder for the new version is created at the end of the current branch. If the version you check out is not the latest on the current branch, when you check in the version, you must merge your changes with the latest version.