# Page Not Found

The URL `apply_loops_to_screen_elements` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Loops - display multiple line results in app](https://mobsted-2.gitbook.io/knowledge-base/basics/introduction/apply_loops_to_screen_elements.md)
- [How to hide / show screen elements](https://mobsted-2.gitbook.io/knowledge-base/basics/introduction/hide_show_screen_elements.md)
- [Constructor elements to build your app](https://mobsted-2.gitbook.io/knowledge-base/references/intro-placeholder/constructor_elements.md)
- [Show any platform Data in app ellements](https://mobsted-2.gitbook.io/knowledge-base/basics/introduction/display_any_user_and_platform_data.md)
- [Events](https://mobsted-2.gitbook.io/knowledge-base/references/intro-placeholder/events.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://mobsted-2.gitbook.io/knowledge-base/basics/introduction/apply_loops_to_screen_elements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://mobsted-2.gitbook.io/knowledge-base/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://mobsted-2.gitbook.io/knowledge-base/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/knowledge-base/basics/introduction/apply_loops_to_screen_elements.md`).

You may also use `Accept: text/markdown` header for content negotiation.
