States of assets when copying between tracks

IBM BPM, V8.0.1, All platforms > Manage assets in the Process Center repository > Copying changed assets
States of assets when copying from one track to another

Before they are copied from one track to another, assets are in the New, Updated, Conflict, or No Change state as compared to the assets that are available in the destination track.
The following table shows the conditions of each state.

Conditions when states occur
States Conditions
New

The asset is only in the source snapshot.

Updated

The asset is in both the source snapshot and the tip of the destination track and is of the same version, but the asset includes at least one updated dependency in the tip of the destination track.
The asset is in both the source snapshot and the tip of the destination track and is of the same version, but at least one of its dependencies is not in the tip of the destination track.
The asset is in both the source snapshot and the tip of the destination track but each asset is of a different version.

Conflict

An asset dependency in the source snapshot cannot be resolved because of one of the following situations:

An asset in a snapshot (asset A) depends on another asset in that same snapshot (asset B), and asset B gets deleted.
An asset in a snapshot (asset A) depends on another asset in a snapshot or a toolkit (asset B), and the project dependency on the toolkit gets removed.

An asset depends on an asset from a toolkit and both of the following conditions occur:

Both the source snapshot and the tip of the destination track include the same toolkit as a dependency.
This dependency points to a different snapshot of the toolkit.

If the asset is in both the source snapshot and the tip of destination track and is of the same version, but the asset includes a dependency that is in the "Conflict" state, then the asset is marked to be in the "No Change" state.

No Change

The asset is in both the source snapshot and the tip of the destination track and is of the same version. All the present dependencies are of the same version
.

Copying changed assets from one track to another

States	Conditions
New	The asset is only in the source snapshot.
Updated	The asset is in both the source snapshot and the tip of the destination track and is of the same version, but the asset includes at least one updated dependency in the tip of the destination track. The asset is in both the source snapshot and the tip of the destination track and is of the same version, but at least one of its dependencies is not in the tip of the destination track. The asset is in both the source snapshot and the tip of the destination track but each asset is of a different version.
Conflict	An asset dependency in the source snapshot cannot be resolved because of one of the following situations: An asset in a snapshot (asset A) depends on another asset in that same snapshot (asset B), and asset B gets deleted. An asset in a snapshot (asset A) depends on another asset in a snapshot or a toolkit (asset B), and the project dependency on the toolkit gets removed. An asset depends on an asset from a toolkit and both of the following conditions occur: Both the source snapshot and the tip of the destination track include the same toolkit as a dependency. This dependency points to a different snapshot of the toolkit. If the asset is in both the source snapshot and the tip of destination track and is of the same version, but the asset includes a dependency that is in the "Conflict" state, then the asset is marked to be in the "No Change" state.
No Change	The asset is in both the source snapshot and the tip of the destination track and is of the same version. All the present dependencies are of the same version .