Mapping Rules Table

Data Management Capabilities > Managing Change > Change Management Administration > Define Mapping Rules for Change Management > Mapping Rules Table

Mapping Rules Table

The mapping rules allow you to define rules to map the following attribute, object, and state:

• Change intent to release targets for all affected object types

• Change intent for all affected object types

• Release states for objects released by changes

Site and organization administrators can create, edit, and view mapping rules using the Mapping Rules table.

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

•

Site > Utilities > Business Rules

•

Organizations > Utilities > Business Rules

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.

Actions

The following actions are available from the table toolbar and from the right-click actions menu in the table rows:

Action

Description

Delete

Delete the selected one or more mapping rules.

New Mapping Rule

Create a new mapping rule. For more information on each mapping rule, see Define Mapping Rules for Change Management.

Export

Export the selected rules.

Import

Import a mapping rule from an existing ZIP or JAR file.

Edit

Edit the selected rule.

When the Edit Mapping Rule window opens, make your changes and select one of actions:

• OK—Applies the changes.

• Cancel—Discards the changes.

You cannot edit Rule Name, Type, and Source Value.

Table Columns

Column

Description

Rule Name

The name of a mapping rule. For more information on each mapping rule, see Define Mapping Rules for Change Management.

Context

Site or organization

If you define rules at the organization context, those rules take precedence over the context rules.

Source Value

These values change for each mapping rule that you select:

• Change Intent Release Targets—The source values are the change intent values. For example, Affected End Item, Effectivity, Revise, Save As, None.

• Object Change Intents—The source values are the affected object types. For example, All Local Affected Object Types, All External Affected Object Types, Part, Documents.

• Object Release States—The source values are the affected object types. For example, All Local Affected Object Types, All External Affected Object Types, Part, Documents.

Mapped Value

These values change for each mapping rule that you select:

• Change Intent Release Targets—The mapped values are the release target, such as Change, Obsolescence. You can select one or more mapped values for a source value from the Mapped Value list.

• Object Change Intents—The mapped values are the change intent values, such as Effectivity, Save As, Revise. You can select one or more mapped values for a source value from the Mapped Value list.

• Object Release States—The mapped values are the release states, such as Change, Obsolescence. You can select one or more mapped values for a source value from the Mapped Value list.

When mapped values are the release states, PTC recommends that you use Change and Obsolescence or any other custom value that you define. However, if you want to use values apart from the recommended and custom values, you must design the workflow appropriately.

Default

Any mapped value selected from the Mapped Value list.

Type

There are different affected object types, such as All Local Affected Object Types, All External Affected Object Types.

For more information, including examples of how these properties are used, see Define Mapping Rules for Change Management.