# Welcome

{% hint style="info" %}
**UPMX is becoming YouDesign Command.** We are currently in the process of renaming UPMX to **YouDesign Command** as part of the broader YouDesign Enterprise Transformation Suite. This rename is ongoing — the Command app has not been released yet, and this documentation continues to describe UPMX as it exists today. You will see both names referenced across our materials during the transition.
{% endhint %}

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2FnjsbWXY9Eph1Ks8uTwAr%2FRenaming.png?alt=media&#x26;token=1443dfa1-70f5-49ce-aea1-f1976b38e52e" alt="" width="316"><figcaption></figcaption></figure>

## What's happening with the rename

UPMX is not being replaced or rebuilt. It is the **same product, under a new name**. Over the coming releases, you will see the UPMX name gradually give way to YouDesign Command across the ServiceNow Store, our product UI, and these documentation pages.

While the transition is in progress:

* **This documentation remains the source of truth for the current product.** Every feature, table, role, and configuration described here applies to the UPMX app as it exists in your ServiceNow instance today.
* **No action is required from existing customers.** Installations, data, and configurations carry forward. When YouDesign Command is released, we will publish a dedicated upgrade guide.
* **Legacy references to "UPM-X" (with the hyphen) are preserved** in release notes, table names, and scope prefixes (for example, `x_inpgh_upmx_*`). These technical identifiers will not change with the rename.

If you are reading this for the first time and wondering which name to use — use **UPMX** for anything you are doing today. Use **YouDesign Command** when referring to the roadmap.

## About UPMX

UPMX is a natively built ServiceNow application for Enterprise Portfolio Management, Enterprise Architecture, and Strategic Planning. It runs 100% inside ServiceNow, requires no external integration, and needs no ongoing customization to start using.

The application extends the ServiceNow CMDB CI table with a **Portfolio Element** superclass, so every portfolio feature — fields, lifecycles, relationships, indicators — is inherited from a single governed table. This modeling approach keeps the metamodel consistent across the enterprise and lets your ServiceNow admin configure the architecture the same way they would any other ServiceNow application.

![UPMX Architecture](https://content.gitbook.com/content/x4mE784snR9Eb8oVrk4e/blobs/sbPea6tsMiUf3hetGD0c/d048f84%20UPMX_Architecture.png)

## Compatibility

UPMX is compatible with the latest versions of all common browsers. Actual compatibility depends on your ServiceNow UI framework — UPMX currently runs in **UI14**, which supports:

* Chrome 103+
* Firefox 102+
* Safari 15+
* Edge 100+

{% hint style="danger" %}
**Unsupported browsers**

* **Edge Legacy** — end of support 9 March 2021
* **Internet Explorer 11+** — end of support 17 August 2021
  {% endhint %}

## Where to go next

* [**Install**](https://docs.ins-pi.com/command/get-the-app/installation) — Installation instructions for your ServiceNow admin (typically 10–15 minutes, hands-free).
* [**Update**](https://docs.ins-pi.com/command/get-the-app/updating) — Upgrading an existing UPMX installation.
* [**Architecture**](https://docs.ins-pi.com/command/overview/architecture) — How UPMX extends ServiceNow's CSDM and CMDB model.
* [**Release Notes**](https://docs.ins-pi.com/command/overview/release-notes) — Full version history, including the V4.7 UPM-X → UPMX rename.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ins-pi.com/command/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
