> For the complete documentation index, see [llms.txt](https://docs.emobiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emobiq.com/emobiq-client/006-actions-and-visual-logic/logic-block-and-parameter-types/visual-interface.md).

# Visual Interface

This section will provide you with a visual overview of logic blocks and parameters in eMOBIQ. There are three key areas that are involved when user use logic blocks. These interfaces are as illustrated in the example below:

![Overview](/files/nCMlgasUjtexyufWScUf)

1. **All Logic Blocks**

   In the section which indicates "All Logic Blocks", it contains the list of all actions/logic blocks that are available for use. Here, you can drag various logic blocks into visual logic space on the left to design the functionalities of your app.
2. **Logic Block Example**

   The "Logic Block Example" showcases a specific logic block in action. This visual representation allows you to see how a logic block is displayed in the visual logic space and how it functions within your application. You can drag more actions from the action list into the workspace and connect different logic blocks together to build more sophisticated logic.
3. **Logic Block Inspector**

   The "Logic Block Inspector" opens the configuration view of a selected logic block. This interface allows you to delve into the details of a logic block's input parameters. This inspector allows users to configure the selected logic block accordingly to change the logic block behaviour to meet specific requirements. Use the action reference to explore the different behaviours of logic blocks.


---

# 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://docs.emobiq.com/emobiq-client/006-actions-and-visual-logic/logic-block-and-parameter-types/visual-interface.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.