> 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/time-analysis.md).

# Retire classic TIME Analysis

Retire the classic TIME Analysis after upgrading to YouDesign Command v26.1; no migration is needed.

Retires the classic TIME Analysis. Command's TIME Analysis content type replaces it and calculates its scores live, so there is nothing to migrate. Follow [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md) first.

## Steps

### 1. Back up the TIME configuration records

Step 4 deletes the TIME configuration records by hand. Export them to XML first, so they can be put back if anything goes wrong.

1. Open each URL from step 4 in turn.
2. Right-click any column heading and choose **Export > XML**.
3. Save the file somewhere outside the instance.

To put the records back, open the same list, right-click a column heading, choose **Import XML** and select its file. Import the attribute configurations first, then the breakdowns, then the score calculation details.

### 2. 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" %}

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

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

The set also removes the colored **Tolerate**, **Invest**, **Migrate** and **Eliminate** labels from the TIME quadrant field in Business Application lists.

### 3. Delete seven global settings

Delete these from the YouDesign Command global settings (`x_inpgh_upmx_global_settings`):

* `time.configuration.chartSize`
* `time.configuration.field_names`
* `time.configuration.bubbleColors`
* `time.configuration.quadrantSeparator`
* `time.configuration.quadrantColors`
* `time.configuration.active`
* `time.configuration.additionalEditorRole`

### 4. Delete the TIME configuration records

Delete the records listed at each URL, in this order, because each depends on the next:

1. Score calculation details: `https://<instance>.service-now.com/x_inpgh_upmx_score_calculation_detail_list.do?sysparm_query=attribute_config.nameSTARTSWITHtime`
2. Attribute configuration breakdowns: `https://<instance>.service-now.com/x_inpgh_upmx_attribute_config_breakdown_list.do?sysparm_query=attribute_config.nameSTARTSWITHtime`
3. Attribute configurations: `https://<instance>.service-now.com/x_inpgh_upmx_attribute_config_list.do?sysparm_query=nameSTARTSWITHtime`

### 5. Remove the TIME Analysis form sections

1. Open `https://<instance>.service-now.com/sys_ui_form_section_list.do?sysparm_query=sys_ui_section.caption%3DTIME%20Analysis`.\
   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 the classic TIME Analysis.
2. Clear the cache: open `https://<instance>.service-now.com/cache.do`.

## Check it worked

* The **TIME Analysis** section is gone from the Business Application form.
* A TIME Analysis in Command still shows its quadrants.

## Related

* [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md)
* [Content Types](https://docs.ins-pi.com/command/the-portal/content-types.md#time-analysis)


---

# 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/time-analysis.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.
