Define Mapping Rules for Change Management

A mapping rule is a set of rules that is defined to map the following attributes, object, and state:

To access the Mapping Rules table, navigate to the following launch points:

The Mapping Rules table is available at the organization context when the wt.mappingRules.enableOrganizationRules property is set to true. By default, this property is set to false.

The rules defined at the organization context take precedence over the site context rules.

There are three types of mapping rule:

This mapping rule maps the change intent to the release target for an affected object type. It controls the availability of the release target values for the assigned change intents of the corresponding affected objects.

When creating this rule, set the following values:

• Type — Any affected object type, such as All Local Affected Object Types, All Remote Affected Object Types, Parts.

• Source Value — Any change intent, such as Effectivity, Save As, Revise. For more information on change intent, see About Change Intent.

• Mapped Value — Any release target, such as Change and Obsolescence. You can select one or more mapped values for a source value from the Mapped Value list.

When you define this rule for an affected object type, you can set the release target value for one or more type of object in the Resulting Objects table. For more information on Resulting Objects table and associated actions with it, see Resulting Objects Table.

If this rule is not defined, then all transition values are displayed under Release Target column.

The wt.change2.showAllChangeTransitions property controls the availability of transition values under the Release Target column. For more information on how the change intent of the affected objects is reconciled with the release target of the resulting objects, see Reconciling the Change Intent with Release Targets.

This mapping rule maps the affected object type to change intent. This rule controls the availability of change intent values for the affected object types in the Affected Objects table. When creating this rule, set the following values:

• Source Value — Any affected object type, such as All Local Affected Object Types, All Remote Affected Object Types, Parts.

• Mapped Value — Any change intent, such as Effectivity, Save As, Revise. For more information on change intent, see About Change Intent. You can select one or more mapped values for a source value from the Mapped Value list. You can also add a custom value for the existing change intent value, for more information see the Adding Custom Value to Existing Change Intent Value section in this topic.

After you have defined this rule for an affected object type, you can set the change intent value for one or more affected object types in the Affected Objects table. For more information, see Affected Objects Table for Change Tasks. If this rule is not defined for the specific affected object type, then the default rules for all local affected object types or all remote affected object types are applied.

The enumerated type customization utility allows you to add a custom value to the existing change intent. For more information on how to add, edit, or delete values of a Windchill enumerated type, see Enumerated Type Customization Utility.

You can add a custom value to the existing change intent using the utility and the wt.change2.ChangeIntentRB file. The added custom value is available in a change task and the Object Change Intents mapping rule. After restarting Windchill, the custom value and other change intent values are visible for the Object Change Intents mapping rule. You can also set the custom value as Default when creating the mapping rule.

This mapping rule maps the affected object type to the released state. It controls the creation of redline and synchronization of changes that match with the released state. When creating this rule, set the following values:

• Source Value — Any affected object type such as All Local Affected Object Types, All Remote Affected Object Types, Parts.

• Mapped Value — Any release states, such as Change and Obsolescence. You can select one or more mapped values for a source value from the Mapped Value list.

After you have defined this rule for an affected object type, you can set the state of the object from In Work to the latest Released state before creating the redline. For more information on redline process, see the Managing Redline section in Redline Process.

If this rule is not defined, then you cannot create redline for parts and the change notice workflow will not synchronize the affected objects on the other open change notices with the latest released revisions.

The enumerated type customization utility allows you to add a custom value to the existing released state. For more information on how to add, edit, or delete values, see Enumerated Type Customization Utility.

You can add a custom value to the existing release state using the utility and the wt.lifecycle.TransitionRB file. The created value is visible on a change task and mapping rule. After restarting Windchill, the custom value and other release state values are visible for the Object Release States mapping rule. You can also set the custom value as Default when creating the mapping rule.

You can create a new mapping rule or edit the existing mapping rule. You can create a duplicate mapping rule if the attribute values, such as Rule Name, Context, Source Value, and Mapped Value are unique.

Follow these steps to create a mapping rule:

2. Under the Mapping Rules field, select the appropriate values for the fields Type, Source Value, and Mapped Value. The options that are available for each field depend on the selections you make under the Rule Name fields. For more information about selecting appropriate values, see the Different Types of Mapping Rules section in this topic.

It is required to define one default value. The Default is applied only when a default value or mapping rule is defined for the objects that exist.

You can

Edit or

Delete rules from the mapping rules table. For more information on these actions, see Mapping Rules Table.