> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoycore/object-model/solution/menu.md).

# Menu

## Overview

The `Menu` object is a reusable design-time entity that represents a list of menu items. It can be utilized across various components and services, promoting consistency in menu design.

## Functionality

The `Menu` object includes several key properties. The `comment` property allows adding programmer notes or other descriptive information about the menu's purpose. The `encapsulation` property defines the menu's visibility, with options such as "Public" (accessible across modules) or "Module Scope" (restricted to the same module). The `name` property serves as the unique identifier for the menu. Additionally, the `styleClass` property allows associating CSS classes for styling purposes.

## Properties Summarized

| Type                                                     | Name                            | Summary                                                                                         |
| -------------------------------------------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------- |
| [String](/reference/servoycore/dev-api/js-lib/string.md) | [comment](#comment)             | Additional design time information, such as programmer notes about this model object's purpose. |
| [Number](/reference/servoycore/dev-api/js-lib/number.md) | [encapsulation](#encapsulation) | The encapsulation mode of this Menu.                                                            |
| [String](/reference/servoycore/dev-api/js-lib/string.md) | [name](#name)                   | The name/identifier of the menu.                                                                |
| [String](/reference/servoycore/dev-api/js-lib/string.md) | [styleClass](#styleclass)       |                                                                                                 |

## Properties Detailed

### comment

Additional design time information, such as programmer notes about this model object's purpose.

**Type**\
[String](/reference/servoycore/dev-api/js-lib/string.md)

### encapsulation

The encapsulation mode of this Menu. The following can be used:

\- Public (available in both scripting and designer from any module)\
\- Module Scope - available in both scripting and designer but only in the same module.

**Type**\
[Number](/reference/servoycore/dev-api/js-lib/number.md) the encapsulation mode/level of the persist.

### name

The name/identifier of the menu.

**Type**\
[String](/reference/servoycore/dev-api/js-lib/string.md)

### styleClass

**Type**\
[String](/reference/servoycore/dev-api/js-lib/string.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://docs.servoy.com/reference/servoycore/object-model/solution/menu.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.