> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands/user-interface-command-group-0x18nn/display-flexible-ui-pages-display-only-command-0x1830/ui-page-option-0x01-and-0x02-layout.md).

# UI Page Option 0x01 and 0x02 Layout

The host uses UI Page Option **0x01** to display a page with a title, a maximum of 6 data buttons (2 rows and 3 columns in Landscape Screen Orientation, 3 rows and 2 columns in Portrait Screen Orientation) with text, and maximum 3 functional buttons with a color option of red, green, or yellow.

The host uses UI Page Option **0x01** to display a page with a title, maximum of 4 data buttons (2 rows and 2 columns in Landscape Screen Orientation, 2 rows and 2 columns in Portrait Screen Orientation) with text, and maximum 3 functional buttons with a color option of red, green, or yellow.

The host uses UI Page Option **0x02** to display a page with a title, maximum of 6 data buttons (2 rows and 3 columns in Landscape Screen Orientation, 3 rows and 2 columns in Portrait Screen Orientation) with $Amount, and maximum 3 functional buttons with a color option of red, green, or yellow.

The host uses UI Page Option **0x02** to display a page with a title, maximum of 4 data buttons (2 rows and 2 columns in Landscape Screen Orientation, 2 rows and 2 columns in Portrait Screen Orientation) with $Amount, and maximum 3 functional buttons with a color option of red, green, or yellow.

The button with \*\*$\*\*Amount value is host provided. The title, data buttons text, and functional buttons are labeled with String IDs associated with configured String messages. See **Table – Default User Interface String IDs and Strings**. When the user presses any button, the device sends a notification to the host to indicate the corresponding button is pressed. See **User Interface Host Action Request - Notification 0x1803.** After that, the host will decide what to do next.

## Recommended maximum number of characters for this page

* Landscape Screen Orientation:
  * Title text:
    * \~18 Upper case wide size characters (example: “WM”)
    * \~23 Upper case regular size characters (example: “ABC”)
    * \~21 lower case wide size characters (example: “wm”)
    * \~30 lower case regular size characters (example: “abc”)
  * 3-columns data button text:
    * \~5 Upper case wide size characters (example: “WM”)
    * \~8 Upper case regular size characters (example: “ABC”)
    * \~6 lower case wide size characters (example: “wm”)
    * \~9 lower case regular size characters (example: “abc”)
  * 2-columns data button text:
    * \~9 Upper case wide size characters (example: “WM”)
    * \~13 Upper case regular size characters (example: “ABC”)
    * \~9 lower case wide size characters (example: “wm”)
    * \~15 lower case regular size characters (example: “abc”)
  * Functional button text:
    * \~5 Upper case wide size characters (example: “WM”)
    * \~8 Upper case regular size characters (example: “ABC”)
    * \~6 lower case wide size characters (example: “wm”)
    * \~9 lower case regular size characters (example: “abc”)
* Portrait Screen Orientation:
  * Title text:
    * \~13 Upper case wide size characters (example: “WM”)
    * \~17 Upper case regular size characters (example: “ABC”)
    * \~14 lower case wide size characters (example: “wm”)
    * \~20 lower case regular size characters (example: “abc”)
  * 2-columns data button text:
    * \~6 Upper case wide size characters (example: “WM”)
    * \~10 Upper case regular size characters (example: “ABC”)
    * \~7 lower case wide size characters (example: “wm”)
    * \~11 lower case regular size characters (example: “abc”)
  * Functional button text:
    * \~4 Upper case wide size characters (example: “WM”)
    * \~6 Upper case regular size characters (example: “ABC”)
    * \~5 lower case wide size characters (example: “wm”)
    * \~7 lower case regular size characters (example: “abc”)

### The Layout for a page with a title, a maximum of 4 data buttons with text/$Amount, and a maximum of 3 functional buttons:

<figure><img src="/files/y3KmgiXVY3nXBHZwwHu5" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/0qxtoJifpS9YZpeEsKxu" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/czzjYJxlBInxHfzSyfnH" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/5Fj5KkQGF7PdNLO8c6pX" alt=""><figcaption></figcaption></figure>


---

# 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.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands/user-interface-command-group-0x18nn/display-flexible-ui-pages-display-only-command-0x1830/ui-page-option-0x01-and-0x02-layout.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.