BuildView
Use when you want to search for information related to building your
application, such as viewing a build tree, or when you want to do build actions.
PartFullUse when you want to search for parts across releases, components, or work
areas. For example, you want a list of all the optics.c parts. Unlike the Parts
Filter,you can specify one or more release or work area names.
Youcan also use this filter to display only parts that have been changed in a
work area. For example, you check out robot.c to work area 310:1, and that is
the only part that you have changed. If you use the PartFull Filter to query for
all the parts in work area 310:1, only one record is returned.
Youcannot use this filter to search for build information.
Refer to the online help, in particular How do I, for more information on how to use the
Filter windows. Select How do I from the Help pull-down menu to access the
information.
Using work areas
Awork area is a logical temporary work space that enables you to isolate your work on
the parts in a release from the official versions of the parts. Youcan check parts out to
a work area, update them, and build them without affecting the officialversion of the
parts in the release. Youmust create a work area before you can create, check out, or
check in parts. If your component’s process includes a design, size, review subprocess
for defects or features and the release follows a tracking subprocess, a work area is
automatically created when sizing records exist and the associated defect or feature is
accepted. TeamConnectionassociates these work areas with the appropriate defect or
feature.
The parts in a work area do not become available in the release until the work area is
integrated.Also, if your release follows a driver subprocess, parts that have been
changed do not become available in the release until the associated driver is
committed. However,users who have the authority to access the work area can view
and work with the parts in it.
Youcan save intermediate versions of the parts in your work area by

freezing

your
work area. Every time you freeze a work area, TeamConnectionsaves a revision level
of the work area. When you freeze work area 123:1, for example, a version called
123:2 is created. This version contains information about each part in the work area
and its current version at the time the work area was frozen. It may contain version 1 of
part optics.c, for example. If you freeze the work area again later,a new version called
123:3 is created with information about the versions of the parts in the work area when
it was frozen. This version may contain version 2 of part optics.c. Each of these work
area versions is saved in the database and you can retrieve the versions of the parts
they contain before you integrate the work area into the release. Therefore, you should
freeze a work area whenever there is a possibility that you will want to return to that
28 User’s Guide