An artifact becomes obsolete when it has been superseded by a newer version of the same artifact, installed by a different bundle.

This occurs regularly because common artifacts are packaged in many NE release bundles.

New bundles can be released and installed over time for bug fixes, extra adaptation, or new NE vendors.

Example scenario, using the fictitious NE 9999 ABC, releases 23.10 and 24.10:

• abc-mdc-1.2.1 is part of the adaptation bundle for release 23.10. This artifact provides MDC for the NE.

• abc-mdc-1.3.0 is part of the adaptation bundle for release 24.10.

• When the 24.10 bundle is installed, abc-mdc-1.2.1 becomes obsolete. Both the 23.10 and the 24.10 NEs automatically use the abc-mdc-1.3.0 artifact for MDC adaptation.

Important! As shown in the example, the obsolete status of abc-mdc-1.2.1 means it is not the version in use. The function of the 23.10 NE is not compromised.

Artifact bundle status changes

An artifact bundle becomes obsolete when all the artifacts in the bundle are superseded by artifacts in one or more newer bundles.

If a bundle is in obsolete status, it can be uninstalled and removed unless you prefer to keep it for rollback purposes.