Group revision rule entries by item type

You can modify the order of precedence of revision rule entries by grouping revision rules by item type. Teamcenter evaluates any revision rule under the item type group for configuration of item revision only if the item type of the revision rule group and underlying item revision matches. By using this grouping mechanism in a product structure that has item revisions of different item types, you can create revision rules that selectively apply the revision rule entries according to the given item type. For example, you may use an item to manage parts and equipment, but need to distinguish between a production part and the equipment used to manufacture the part. Each of these item types may have the same status but can be configured in a different way, for example, by unit or date released. To achieve this, you can define a revision rule with a clause that restricts some of the entries to certain item types. To do so, create a Has Item Type entry in a revision rule in the following format: Copy Has Item Type (<item type 1, item type 2, etc) {

<Entry 1>

<Entry 2> etc.} Example Copy Has Item Type (Part) } Has status (Approved, Configured with Released Date) } Has status (Production, Configured with Unit Number) Here the Has status ( Approved, Configured with Released Date) revision rule entry configures the product structure only if the item type is Part. For all other item types in the product structure, Teamcenter applies the Has status (Production, Configured with Unit Number) revision rule entry. If neither of these entries applies, the part is not configured by this revision rule. Grouping entries for multiple item types Each Has Item Type entry may have one or more item type arguments, but cannot be left blank, that is, you cannot create a revision rule entry for Has Item Type (Any). To include more than one item type argument, use the syntax in the following example: Copy Has Item Type ( Prototype, Virtual Build ) { ...} Grouping combinations of item type entries You can only use one level of grouping and may not create nesting inside an existing group entry, as shown in the following examples: Single revision rule entry grouped for item type: Copy Has Item Type ( Prototype ) { entry 1 } entry2 Multiple revision rule entries grouped for item type without equal precedence: Copy Has Item Type ( Prototype ) { entry 1 entry 2 } entry3 Multiple revision rule entries grouped for item type with and without equal precedence: Copy Has Item Type ( Part ) { [Status (Released, Configured Using Release Date) } Has Item Type ( Module, Incremental Change ) { [Status (Released, Configured Using Unit No) } Working This example shows how you can use the same status type in both situations, but configured differently—in this case, by date for parts, but by unit number and incremental change for modules. You can only group Working and Status entries with equal precedence.