> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/lifecycle.md).

# Retire legacy Lifecycles

Retire the legacy Lifecycles feature after upgrading to YouDesign Command v26.1, after moving its definitions and dated phases into Command. Skip this if you are using Full Cleanup.

Retires the legacy Lifecycles implementation. The new [Lifecycle](https://docs.ins-pi.com/command/features/lifecycle.md) replaces it. Follow [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md) first.

{% hint style="danger" %}
**Migrate first.** The cleanup set drops the legacy lifecycle tables. The lifecycle definitions and its dated phases must reach Command before then, or they are lost.
{% endhint %}

## Steps

### 1. Back up the legacy tables

The cleanup set drops these tables with every record in them. Export them to XML before you migrate, so the records can be put back if anything goes wrong.

| Table                                       | Name                                  |
| ------------------------------------------- | ------------------------------------- |
| **Lifecycle**                               | `x_inpgh_upmx_pf_lifecycle`           |
| **Lifecycle Breakdown**                     | `x_inpgh_upmx_pf_lifecycle_breakdown` |
| **Business Application > Software Product** | `x_inpgh_upmx_report_cmdb_app2swp`    |

For each one:

1. Open `https://<instance>.service-now.com/<name>_list.do`, with the name from the table above.
2. Right-click any column heading and choose **Export > XML**.
3. Save the file somewhere outside the instance.

If a list holds more records than your instance exports at once, filter it into parts, for example by **Created**, and export each part.

To put the records back, back out the cleanup set so the tables return, then on each table's list right-click a column heading, choose **Import XML** and select its file.

### 2. Migrate the data

1. In Command, click **Open menu** (☰), expand **Migration** and choose **Lifecycles**.
2. Click **Migrate** on **Definitions and phases** and wait for 100%.
3. Click **Migrate** on **Lifecycle data** and wait for 100%. On a large instance you can click **Stop after this batch** and run it again later; it continues where it left off.
4. Optional: to see the Command lifecycle on forms before the cleanup, click **Switch to Command** on **Forms show Command**. **Revert to legacy** switches forms back.

Each finished step is marked **Done**, and its button then reads **Re-check**. Rows that can never be written are counted under **Cannot be written** and count as done. The top of the page reads **Ready for legacy cleanup** once every step is done, or how many steps are left. A record already migrated is never written twice, so running it again is safe.

**Forms show Command** sets the global setting `lifecycle.form_visualization.use_command` (`true` shows the Command lifecycle, `false` the legacy one). The setting only works until the cleanup: once the legacy lifecycle tables are gone, forms always show the Command lifecycle.

### 3. Commit the update set

**First, check Logic Preservation.** In **Retrieved Update Sets**, look for **YCM V26.1 Legacy Logic Preservation** with the state **Committed**.

If it is already committed, for example because you retired another feature first, do not commit it again. Committing it again turns the shared Lifecycles and Measures calculation jobs back on, even ones you deleted by hand. If it is not there, or not yet committed, commit it now:

{% file src="/files/r5th8lgCHZ3rAU8Ldbom" %}

The cleanup set deletes the legacy `x_inpgh_upmx.lfc_editor` role. Before you commit it, give everyone who holds that role **Command Editor** (`x_inpgh_upmx.editor`): Command Editors now change lifecycles. See [Roles the cleanup removes](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md#roles-the-cleanup-removes).

Then commit **YCM V26.1 Legacy Lifecycle Cleanup**. Skip this set if you are using **Full Cleanup**.

{% file src="/files/grN81KCG5HeK535c7CdQ" %}

The set keeps the **UPMX Lifecycle Visualization** form widget: the `UPMXLifecycleVisualization` UI macro and its UI formatter. From the cleanup on, that widget shows the Command lifecycle.

The set also removes the chart colors defined for the legacy lifecycle fields, such as *internal lifecycle*, on the Command tables.

### 4. Delete 8 scheduled jobs

The set switches these jobs off but cannot delete them. In **System Definition > Scheduled Jobs**, delete each one:

<details>

<summary><strong>The 8 Lifecycle jobs</strong></summary>

* `YCM Fill Report Table CMDB Business Application > Software Product`
* `YCM LC Set Lifecycle Stages`
* `YCM LC Delete Lifecycle Breakdowns with Empty Start Date`
* `WEEKLY: YCM LC Recalculate All Lifecycle Dispositions`
* `PERIODIC: YCM LC Set Lifecycle Stage on Definition Change`
* `ON DEMAND: YCM LC Set Lifecycle Stages`
* `ON DEMAND: YCM LC Load Portfolio Element IDs in CMDB CI Lifecycle Breakdown`
* `YCM CAL Set Days to EOL and Days in Production Calculations`

</details>

The last job is shared: it goes only because this cleanup removes the *days to EOL* and *days in production* fields it fills. If you keep Lifecycles, it keeps running.

### 5. Delete one global setting

Delete `lifecycle.MaxYearLimit` from the YouDesign Command global settings (`x_inpgh_upmx_global_settings`).

### 6. Remove the Lifecycles form sections

1. Open `https://<instance>.service-now.com/sys_ui_form_section_list.do?sysparm_query=sys_ui_section.caption%3DLifecycles`.\
   Review each section listed before you delete it: the search matches the section name on every form, so a section with the same name on another form that still needs it can appear too. Delete only the sections that belong to legacy Lifecycles.
2. Clear the cache: open `https://<instance>.service-now.com/cache.do`.

Anything left behind shows as an empty block on the form.

### 7. Delete the realtime indicators on removed fields

Open `https://<instance>.service-now.com/x_inpi_yd_realtime_indicator_list.do?sysparm_query=source_fieldINinternal_lifecycle%2Cx_inpgh_upmx_internal_lifecycle%2Cstandards_lifecycle%2Cmanufacturer_lifecycle%2Cx_inpgh_upmx_manufacturer_lifecycle` and delete the indicators listed.

### 8. Remove the Lifecycles tab from Admin Settings

The **Admin Settings** page of the **YouDesign Command (UPMX)** experience still has a **Lifecycles** tab for the legacy feature. The update set leaves the page alone, so it works whichever features you keep.

1. In the filter navigator, open **UI Builder**.
2. Open the **Experiences** tab.
3. Search for **YouDesign Command (UPMX)** and open it.
4. Expand **Admin Settings** and click **Default**.
5. In the content tree, select the **Lifecycles** tab.
6. In the right panel, click **Tabs**, then **Go to Tabs**.
7. Click the settings icon on the **Lifecycles** tab, then click **Delete**.
8. Click **Save**.

## Check it worked

* None of the 8 Lifecycle jobs is left in **Scheduled Jobs**.
* The **Admin Settings** page of the **YouDesign Command (UPMX)** experience has no **Lifecycles** tab.
* The **Lifecycles** tab is gone from the Business Application form, with no empty block left.
* Forms that showed the legacy lifecycle visualization now show the Command lifecycle.
* Lifecycles in Command still show as before.

## Related

* [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md)
* [Lifecycle](https://docs.ins-pi.com/command/features/lifecycle.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://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/lifecycle.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.
