> 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/oe-user-guides/management-dashboard/events/event-registry.md).
# Event Registry
View all the events happening in the system in relation to digital processes.
Event Registry is a list of all the events that were configured in your tenant for your OE value stream. The events are the triggers that initiate the processes and make them run.
Events are utilized by the `ce-type` attribute, which indicates that the event has occurred. By aligning the **Event Name** (eg. `order.created`) configured in OE with the `ce-type` name, you ensure that a value stream accurately receives and processes the event information.
{% hint style="success" %}
Event Registry lists all the events related to Commerce Engine. The events reflect the actions and processes happening in the Commerce Engine system, which you can use as triggers for the value stream without the need to configure them manually. The pre-configured commerce events facilitate digitalizing the commerce-related workflow processes.
{% endhint %}
To create a new event:
1. In **OE**, go to **Events** -> **Event Registry**.
2. Choose **Create New Event**.
3. Specify the **Display** and **Event** names.
**Display name** - it's the name that is visible in the UI when you create a value stream, for example: **Order Created**.
**Event name** - it's the name of the registered event, for example: `emporix/ce/order.created`.
---
# 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/oe-user-guides/management-dashboard/events/event-registry.md?ask=&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.
{% endhint %}
To create a new event:
1. In **OE**, go to **Events** -> **Event Registry**.
2. Choose **Create New Event**.
3. Specify the **Display** and **Event** names.
**Display name** - it's the name that is visible in the UI when you create a value stream, for example: **Order Created**.
**Event name** - it's the name of the registered event, for example: `emporix/ce/order.created`.
---
# 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/oe-user-guides/management-dashboard/events/event-registry.md?ask=