Import Validation Rules for Item Revisioning Data

When you import items and BOMs, incoming item revisioning data is validated against a set of rules. These rules maintain the integrity of both incoming data and existing data.

The affected item revisioning properties are:

• Lifecycle State
• Revision Number
• Release Date
• Effectivity Date

General

The following rules are applied when importing items with lifecycle state, revision number, or release date properties:

• If any one of these properties is mapped - Lifecycle State, Revision Number, or Release Date, all three must be mapped.
• If there is a value for any one of these fields, all three fields must have a value. If any of the values are missing, an error is displayed and the missing values must be fixed before the items can be imported.

Lifecycle State

The following rules are applied when importing items with a lifecycle state:

• If the lifecycle property is mapped and an incoming item does not have a lifecycle state, the existing working revision of the item is updated.
• Only existing lifecycle values can be imported. If an item has a lifecycle value that does not match the lifecycle values in the target workspace, an error is displayed and the value must be fixed before the items can be imported.
• The lifecycle state Unreleased is a reserved state and is not allowed when importing items.

Revision Number

The following rules are applied when importing items with a revision value:

• If an incoming item matches the current revision in the workspace, the existing item is updated. If it does not match, it is imported as a new item.

• If the incoming item matches the current revision in the workspace AND a least one child is identified for that revision, the existing item is updated.

• When importing the latest revision of an item, the existing working revision of the item is overwritten.

  Note: You must have the Override Revision Locks permission.

Release Date

The following rules are applied when importing items with a release date:

• If an item does not have an effectivity date, the release date is used.
• The value must be in date format.

Effectivity Date

The following rules are applied when importing items with an effectivity date:

• Effectivity Date is an optional property.
• If an effectivity date is not available, the release date is used as the effectivity date.
• The value must be in date format.
• If Effectivity Date is mapped but there are no values for Lifecycle State, Revision Number, and Release Date, then Effectivity Date is ignored.

Automatic and Manual Numbering Rules

If automatic numbering is on:

• The revision value format is validated against the workspace.
• The incoming revision is placed in logical order with the existing revisions.
• If the revision value matches an existing revision, the existing item is updated.

If manual numbering is on:

• The revision value format is not validated.
• The incoming revision is placed in order based on release date.