> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-lens/deprecations.md).

# Deprecations

This feature allows users to define and manage application deprecations.

### Deprecations

List of all the deprecations defined in the system.

* Navigate to **`IZ Lens`** -> **`Deprecations`**.
* **`Type`** - Type of asset E.g.: mule-plugin, rest-api.
* **`Display Name`** - Readable name for the deprecation asset.
* **`Value`** - Version of the asset being deprecated.
* **`Deprecated Apps Count`** - Total applications marked for deprecation based on the defined rule.
* **`Status`** - Status of the deprecation. Possible values include -
  * **`Active`**
  * **`Obsolete`**
  * **`Deprecated`**
  * **`Sunset`**
* **`Actions`** Displays the total assets / applications that are deprecated based on the rules configured in Deprecations. Actions include -
  * **`Update Deprecation`** - Update deprecation definition
  * **`View Deprecated Applications`** - View the list of application marked for deprecation using the defined rule
  * **`Delete`** - Delete deprecation rule

### Configure Deprecations

Click on **`Add Deprecation`** button to create a new deprecation rule. Fields include -

* **`Deprecation Status`** - Status of the deprecation. Possible values include -
  * **`Active`**
  * **`Obsolete`**
  * **`Deprecated`**
  * **`Sunset`**
* **`Deprecation Name`** - Name of the deprecation asset. E.g.: mule-http-connector
* **`Deprecation Display Name`** - Readable name of the deprecation asset.
* **`Deprecation Type`** - Type of asset E.g.: mule-plugin, rest-api.
* **`Deprecation Metadata`** - Deprecated asset’s metadata.
* **`Deprecation Value`** - Version of the asset being deprecated.
* **`Deprecation Operator`** - Comparison operator to be used when applying the rule.
* **`Calculation Type`** - Comparison types include -
  * **`Version Compare`** - SemVer comparison. Ideally used for version comparison
  * **`String Compare`** - Used to compare string values
* **`Deprecation Notes`** - Additional notes to define the deprecation

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FhzGAcK0mg1Ju0QTysbc4%2Fconfigure-deprecations.png?alt=media&amp;token=7014e411-e6ee-447a-9966-3cd0c5b2592f" alt=""><figcaption></figcaption></figure>

### Deprecate an API Asset

This option can be used to deprecate an API asset version. Once the deprecation rule is defined, all the associated / dependent applications will be marked for deprecation as well.

1. Navigate to **`IZ Eye`** -> **`APIs`** and search for the API version which has to be deprecated
2. Click on **`Configure Deprecation`** to deprecate a specific API asset version

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Ftww61QhqAYkl8jBd7oSK%2Fconfigure-api-deprecation.png?alt=media&amp;token=dd5e9152-ba56-4d32-a1cf-f1dacbd246cc" alt=""><figcaption></figcaption></figure>

### See Also

* [Inventory](/product-guides/integral-zone/iz-suite/iz-lens/inventory.md)
* [Aggregated Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/application-dashboard.md)
* [Application Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/application-dashboard.md)
* [Mule Projects](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/mule-applications.md)
* [API Applications](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/exchange-apis.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-lens/deprecations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.