然后使用这些元素定义记录类型。
因此，只是当记录类型位于方案之中时，它才有用。
Therefore, it is usable only if the record types are in the schema.
范例2：方案是一般复杂的，它拥有少量记录类型。
Example 2: The schema is moderately complex, with few record types and hooks.
正如图28所示，您没有局限于档案的一个记录类型。
As you saw in Figure 28, you are not limited to one record type for a profile.
该出错信息会告诉您记录类型Defect并不存在。
This error message tells you that the record type Defect does not exist.
记录类型要激活的选择取决于你如何计划来管理你的请求。
This choice of what record types to enable depends on how you plan to manage your requirements.
利用这个下拉框选择想要的记录类型能够，如图13所示。
Use the drop-down menu and select the desired record type, as shown in Figure 13.
您的方案可能丢失了关于应用于特定记录类型依赖包的信息。
Your schema might be missing the information that a dependent package has been applied to a specific record type.
未来需要什么记录类型，字段，状态模型，以及hook ？
What record types, fields, state models, and hooks will be required in the future?
修改缺省的缺陷记录类型，在缺陷记录类型中增加一个新字段。
Modify the default defect record type to add a new field to the defect record type.
数据收集被称为“数据库”，因为它包含很多不同的记录类型。
The collection of data was referred to as a "data base" because it consisted of not one but many different record types.
可能需要创建集成，或者可能需要在已知的记录类型中添加新的字段。
Integrations may need to be created, or new fields added in a given record type.
在您得到URI之后，您可以使用它来为每一个记录类型得到资源模板。
After you get the URI, you can use it to get the resource template for each record type.
实际上，集成方案是您可能安装或者更新包，或者激活记录类型的地方。
In fact, the Integration schema is the only place where you may install or upgrade packages or enable record types for packages.
对于一个通用的集成，用户可以将任意的记录类型与需求类型联系起来。
And for a custom integration, user can associate any record type with any requirement type.
请注意在打印记录类型时，它看起来就像前面带有额外类型标签的映射。
Notice that when a record type is printed, it looks like a map with an extra type tag in front.
再次减少了个人记录类型的复杂程度，状态转换也减少了设计计划的时间。
Again, reducing the complexity of individual record types and state transitions reduces the time required to design the schema.
就像您在之前的项目的主题中看到的那样，有几种记录类型与设置项目有关。
As you can see from the previous topics on projects, there are several record types involved in setting up a project.
在下一小节中，您将看到如何使用现已存在的记录类型来覆盖这些公共区域。
In the sections that follow, you will see how to use existing types of record to cover these common areas.
为了使处理更简单，我添加了一个类型字段，可以用来明确定义的记录类型。
To make processing even simpler, I have added a type field, which can be used to explicitly define the type of the record.
修改你想要进行权限控制的记录类型，并增加一个reference字段。
Modify the record type for which you want to enable access control, and add a reference field.
ALM模式为管理工作提供了主要的记录类型，称作：请求、任务，以及活动。
The ALM schema provides the primary record types for managing work, which are called: Request, Task, and Activity.
对于集成的记录类型，方案必须有一个回应用值，例如TMTestCase。
For the record type to be integrated, the schema must have a back reference value, such as TMTestCase.
你可以在不影响你目前小组或者记录类型的情况下将这些包运用到你现存的计划中。
You can apply these packages to an existing schema without impacting your current teams or record types.
启用TaskMappings部分，通过以下这些步骤添加一个新的记录类型。
Starting with the Task Mappings section, add a new record type by following these steps.
比起更广泛且更一般的记录类型，它们还表现出对变更管理系统的维护者更少的约束。
They also present fewer constraints to the maintainers of the change management system than broader and more generic record types.
工作请求记录类型是一个可以运用统一变更管理(ucm)包的基于状态的记录类型。
The Work Request record could be a state-based record type with the Unified Change Management (UCM) package applied.
又像前面，这个选择菜单包含ClearQuest记录类型可利用所有字段的列表。
Again, the selection menu contains a list of all of the fields available for the ClearQuest record type.
这显示了只有在“SuperAdmin ”组中的成员可以对ACL记录类型操作。
This shows that only members in the "SuperAdmin" group can operate on the ACL record type.
ClearQuest变更请求记录类型到Jazz工作项的映射必须得到建模和实施。
A mapping of the ClearQuest change request record type to Jazz work items must be modeled and implemented.
应用推荐