Workflow for working on activities in a multiple-stream UCM project

Checking out and modifying source files

To modify files and directories under HCL VersionVault control, you must check them out and ensure that you have assigned your revisions to an activity. Checking out a file makes it writable in your view. Then you can use any editing tool to modify it.

Viewing metadata

Metadata is information that is kept about your activities and source files. While working with checked-out files (checkouts), you might want to use HCL VersionVault tools to view metadata. For example, you can do the following tasks:

• See the history of an element.
• Compare versions of an element.
• See which versions are checked out to your view.

Checking in and testing source files

If you work in a multiple-stream project, if you want to keep a record of the current state of a checkout or to store versions for backup, check in the file. Make sure that you assign the version to the correct activity. Any work that you check in from your development view is not available to other team members until you deliver it.

Before you deliver your work, build and test the work in your development view. This testing is particularly important to do after you rebase the stream and before you deliver activities. This ordering of your work reduces the amount of merging needed when you deliver your work.

When you are ready to make your work available to the rest of the project, deliver it.

If you work in a single-stream project, you do not check in until you test your source files and want to complete your activity.

Indicating your progress

Working on multiple activities

You can set your view to only one activity at a time, but you can keep multiple undelivered activities in your stream. You can work on one activity, set and work on a different activity, and then set and return to working on the original activity.