> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/design/user-interface/uis/menus.md).

# Menus

Lists, editors and widgets can utilize different menu actions, such as delete, import, export, which are configured through UI screens.

A menu action can trigger data updates, queries or API calls and can be attached to a listing screen, editor screen or an individual value widget.

While it is possible to implement new menu action types, Rierino already includes a number of alternatives for different use cases.

## API Actions

Certain menu actions perform calls to Rierino backend APIs. All these menu actions share the following properties:

* **URL:** URL path of the API endpoint to call (allows using "=pattern" for generating dynamic paths using current data).
* **Method:** REST method to use for calling API endpoint.
* **Extra Body:** Extra payload to add to the API call.
* **Extra Headers:** Extra headers to add to the API call.
* **Content Type:** Type of content to send ("none" for empty body).
* **As Text:** Whether response should be returned as text (or json).


---

# 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.rierino.com/design/user-interface/uis/menus.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.