# Frequently Asked Questions

# What are long-lived and point-wise (short-lived) configuration items? What are the differences between the two?

Long-lived items have a lifespan that spans multiple versions, from their introduction to their obsolescence, while point-wise items are relevant only for the specific version they are introduced in.

In Ketryx, configuration items are categorized into two types based on their lifespan and version applicability: long-lived and point-wise (short-lived) item types.

1. **Long-lived Item Types**:
   - These items have both "Introduced in version" **and** "Obsolete in version" fields.
   - "Introduced in version" specifies the first version where the item is effective (inclusive).
   - "Obsolete in version" indicates the first version where the item is no longer effective (exclusive).
   - Examples include Anomalies, Configuration Items, Requirements, Risks, Software Item Specs, Hardware Item Specs, and Test Cases.
   - If "Introduced in version" is not defined, it's assumed to be effective from the first version.
   - If "Obsolete in version" is not defined, it's assumed to be effective in all subsequent versions.

2. **Point-wise (Short-lived) Item Types**:
   - These items **only** have an "Introduced in version" field.
   - This field ties them specifically to the version they are effective in.
   - Examples include CAPAs, Change Requests, Complaints, Test Executions, and Tasks.
   - They are relevant only to the specific version they are introduced in and do not have a predefined end of effectiveness like long-lived items.

More information on configuration item management can be found [here](https://docs.ketryx.com/Nfv9ttHxYK0eaVZFq3wl/manuals/man-01-ketryx-lifecycle-management#id-5.3.-processes-tasks-items-and-members).