Then, record types would be defined using these elements.
然后使用这些元素定义记录类型。
Therefore, it is usable only if the record types are in the schema.
因此，只是当记录类型位于方案之中时，它才有用。
Example 2: The schema is moderately complex, with few record types and hooks.
范例2：方案是一般复杂的，它拥有少量记录类型。
What record types, fields, state models, and hooks will be required in the future?
未来需要什么记录类型，字段，状态模型，以及hook ？
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。
This choice of what record types to enable depends on how you plan to manage your requirements.
记录类型要激活的选择取决于你如何计划来管理你的请求。
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 instance, there are record types for household, family, person, wage and salary job, and general income amounts.
例如，这些记录型态包括：家户、家庭、个人、工作、和平均收入等等。
You can also use the ClearQuest Bridge to link any record type or any number of record types, which gives you flexibility.
您还可以使用ClearQuestBridge来联系任意的记录类型或者任意数量的记录类型，就这给您了很大的灵活性。
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.
就记录类型、字段、通用脚本等等之类的名字达成一致意见，这样每一个项目成员都能知道使用哪一个名字了。
Again, reducing the complexity of individual record types and state transitions reduces the time required to design the schema.
再次减少了个人记录类型的复杂程度，状态转换也减少了设计计划的时间。
For instance, you can expand the Record Types and Forms nodes of the tree to inspect the existing Defect_Base_Submit form.
比如，你可以展开记录类型和目录树的表单节点来查看存在的 Defect_Base_Submit 表单。
Each of these three record types can themselves be assigned "types" (discussed below) to further refine the nature of the work.
这三个记录类型中的任何一个，它们自己都可以被分配“类型”(将在下面进行讨论)来进一步改进工作的本质。
In fact, the Integration schema is the only place where you may install or upgrade packages or enable record types for packages.
实际上，集成方案是您可能安装或者更新包，或者激活记录类型的地方。
They also present fewer constraints to the maintainers of the change management system than broader and more generic record types.
比起更广泛且更一般的记录类型，它们还表现出对变更管理系统的维护者更少的约束。
Taking a step deeper into the process we come upon two additional state-based record types, the Incident and Work Request records.
更深入一步进入过程，我们可以产生两个额外的基于状态的记录类型，事件（Incident）和工作请求（Work Request）记录。
Synchronization rules must be created with mappings of record types to work item types and record properties to work item properties.
同步化规则必须与记录类型对工作项类型的映射以及记录类型对工作项属性的映射一起创建。
This will give you the versatility to attach different ClearQuest record types to any one project based on what your process requires.
这样您就拥有了多种性能，可以根据您的过程需求为任何一个项目附上不同的ClearQuest记录类型。
In files that include different units of analysis, for instance, different record types are needed to hold the different variables.
举例来说，在包含不同分析单位的档案中，为了掌握不同的变项，使用不同的记录型态是必要的。
The requirements gathering process is streamlined because you no longer need to get all project teams to agree on record types and state transitions.
这些需求将过程集合起来成为流线型，因为你不再需要将所有的项目小组集合起来表明对记录类型和状态转换的建议。
Depending on your processes you may use some, all, or even none of these; you will need to map the various scope elements to ClearQuest record types.
根据您的过程的需要，您可能会用到其中的一些、全部，或者一个也不会用到；您就需要将各种各样的范围元素映射到ClearQuest记录类型。
Next, click the integration status, and check which requirement types, record types, or attributes are missing or incorrectly configured by the report.
接下来，点击集成状态，并检查有哪些需求类型、记录类型或者属性丢失了或者没有得到报告合适的配置。
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)。
应用推荐