Then, record types would be defined using these elements.
然后使用这些元素定义记录类型。
Figure 3: a common workflow architecture — the primary record types.
图3：通用工作流架构——主要的记录类型。
Figure 2 further illustrates the flow for working with these new record types.
图2进一步描述了与这些新记录类型一起工作的流程。
A developer may, of course, be working on multiple record types at the same time.
当然开发人员可能会在同一时间处理多个记录类型。
The purpose of integration is to establish the bridge for two different record types.
集成的目的在于为两种不同的记录类型建立一个沟通的桥梁。
You may see many other record types depending on how your ClearQuest Schema was designed.
根据ClearQuestSchema 的设计方式您可以看到许多其它的记录类型。
One such example is the Notes package, which adds fields and hooks to existing record types.
举一个例子就是notes包，它可以向已存在的记录类型添加区域和hooks。
Step 1: Configurations in ClearQuest - apply RequisitePro packages for applicable record types.
第1步，ClearQuest中的配置-对可应用的记录类型应用requisitepro包。
You can apply these packages to an existing schema without impacting your current teams or record types.
你可以在不影响你目前小组或者记录类型的情况下将这些包运用到你现存的计划中。
The ALM schema provides the primary record types for managing work, which are called: Request, Task, and Activity.
ALM模式为管理工作提供了主要的记录类型，称作：请求、任务，以及活动。
Select and run a query for one of the record types that has been enabled for the integration (such as All Defects).
为在这个集成中激活的记录类型选择并运行一个查询(比如allDefects)。
As you can see from the previous topics on projects, there are several record types involved in setting up a project.
就像您在之前的项目的主题中看到的那样，有几种记录类型与设置项目有关。
The collection of data was referred to as a "data base" because it consisted of not one but many different record types.
数据收集被称为“数据库”，因为它包含很多不同的记录类型。
For example, two record types cannot both be named Defect, and two fields on one record type cannot both be named Headline.
例如，两个记录类型不能同时命名为Defect，而同一记录类型的两个字段不能同时命名为Headline。
Agree on the names of record types, fields, global scripts, and so on, so that every project member knows which names to use.
就记录类型、字段、通用脚本等等之类的名字达成一致意见，这样每一个项目成员都能知道使用哪一个名字了。
They also present fewer constraints to the maintainers of the change management system than broader and more generic record types.
比起更广泛且更一般的记录类型，它们还表现出对变更管理系统的维护者更少的约束。
Synchronization rules must be created with mappings of record types to work item types and record properties to work item properties.
同步化规则必须与记录类型对工作项类型的映射以及记录类型对工作项属性的映射一起创建。
The first field for record type is populated with a pull-down selection showing all of the record types available for the ClearQuest schema (see Figure 8).
RecordType的第一个有内容的字段，由一个下拉选择框组成，显示了ClearQuest模式可利用的所有记录类型(参见图8)。
What this means is, if you want to associate multiple record types from ClearQuest to a single project; then the profile must contain a task mapping for each record type.
意思是说，如果您想从ClearQuest 中联合多个记录类型映射到一个单一的项目，那么这个档案必须包含每个记录类型的任务映射。
Information contained in this output includes process, thread, and node number, as well as trace point Numbers, function names, trace record types and, in some cases, probe Numbers.
该输出中的信息包括进程、线程、节点号，以及跟踪点号、函数名、跟踪记录类型，在某些情况下还包括探测号。
Information contained in this output includes process, thread, and node number, as well as trace point Numbers, function names, trace record types and, in some cases, probe Numbers.
该输出中的信息包括进程、线程、节点号，以及跟踪点号、函数名、跟踪记录类型，在某些情况下还包括探测号。
应用推荐