> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/standard-app-core-concepts/concepts/gedi-message-setup.md).

# GEDI Message Setup

"A 'GEDI Message Setup', is a definition of the process that is connected to each 'GEDI Profile'"

![GEDI Message Setup](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2Fu4g4TMQqBi3e0LuSuW0H%2FCC%20Message%20Setup.png?alt=media\&token=1a5d4e10-4736-4bd5-a1d6-345db0bb5c20)

## Introduction

In the 'GEDI Message Setup' page view in Business Central you will find 'GEDI Message Setups'. A 'GEDI Message Setup', is a definition of how three main parameters; 'GEDI Profile', 'GEDI Message Code' and 'GEDI Mapping Document' are all tied together and build the process that is connected to each 'GEDI Profile'.

For each 'GEDI Message Setup' there is a check box for "Not Create Automatically". If this is checked, the normal events defined by 'GEDI Message Selection' will be disabled for the combination of 'GEDI Message Code' and 'GEDI Profile'. This can be useful when it's better to have a 'GEDI Mapping Document' create the 'GEDI Message Code' instead of the normal event. For example, when a control is to decide wheather a 'GEDI Message' should be created or not.  

![Example of what the 'GEDI Message Setup' table can look like.](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2Fidb1RoojuIhQBOZW2zuI%2Fbild.png?alt=media\&token=fccb2f99-fd15-4c05-8e4a-48562a564c24)


---

# 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.goldenedi.com/standard-app-core-concepts/concepts/gedi-message-setup.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.