> 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/value-stream-modeller/settings-and-configuration/events/event-registry.md).

# Event Registry

Event Registry is a list of all the events that were configured in your tenant for your value streams. 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 VSM with the `ce-type` name, you ensure that a value stream accurately receives and processes the event information.

<figure><img src="/files/80NDQhrcdsnelalkF81T" alt=""><figcaption></figcaption></figure>

{% 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:

{% stepper %}
{% step %}

#### Open Event Registry

In **VSM**, go to **Events** -> **Event Registry** and choose **Create New Event**.
{% endstep %}

{% step %}

#### Specify the Display and Event names

* **Display name** - the name visible in the UI when you create a value stream, for example: **Order Created**.
* **Event name** - the name of the registered event, for example: `emporix/ce/order.created`.
  {% endstep %}

{% step %}

#### Save your changes

{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

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

```
GET https://developer.emporix.io/value-stream-modeller/settings-and-configuration/events/event-registry.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.