Lifecycle feature considerations
As an administrator or a provider, you must note the following points before you enable the lifecycle feature.
- Visibility of assets
- The following table lists the visibility and accessibility of assets on the UI based on user
persona.
Use case State of asset API consumer API provider Administrator View API in API gallery Draft 
Live 
Retired View package in API packages (Package gallery) Draft Live Retired Request application (for an API) or subscription (for a package) Draft Live Retired Search an API or package by using global search Draft Live Retired Accessing an API or package by using deep link URL Draft Live Retired Note: API consumers can access the APIs or packages that are in Draft or Retired state, if they have a valid application or valid subscription that is associated with the asset.
- State of restored APIs
- When you restore APIs from an archive, the restored APIs retain the same state from the backup archive. If APIs are backed up from an instance in which the API lifecycle feature is not enabled, then the restored APIs are kept in the Draft state.
- State of migrated APIs
- When you migrate APIs to 10.15 from an earlier version of Developer Portal, the migrated APIs are kept in the Draft state. You can change their state according to your requirement.
- Creating applications for APIs in Draft state
- Only administrators or providers can create applications for the APIs that are in the Draft state to test them before you expose to consumers. Consumers cannot view or use those APIs.