> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2023/2023-12-21-oe-renaming.md).

# 2023-12-21: OE - Renaming Commerce Execution Platform to Orchestration Engine

### Overview

We are proud to announce a significant change in our journey: the renaming of our product from Commerce Execution Platform to Orchestration Engine. This change reflects our commitment to growth, evolution, and better aligning our brand with our vision for the future.

Together with our product name change, we've also decided to change some names inside the application, see the table below for details.

| Former name                 | Current name             |
| --------------------------- | ------------------------ |
| CXP                         | OE                       |
| Execution Template          | Digital Process          |
| Execution Context           | Process Context          |
| Execution Step              | Process Step             |
| Execution Template Debugger | Digital Process Debugger |

### Known problems

No known problems at time of release.

### Documentation and links

[Working with Digital Processes](/oe-user-guides/value-streams/working-with-value-streams.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://developer.emporix.io/release-notes/archive/2023/2023-12-21-oe-renaming.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.