> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/podglad-definicji-formularza-xml.md).

# Form definition preview (XML)

Tab **Source** allows viewing and editing the technical definition of the form (also [a composite component](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/komponenty-rozszerzone/komponenty-zlozone.md) and business) in the format **XML**.\
It provides direct access to the template structure, making it possible to inspect or modify elements that are not available in the standard editor view.

## **Features**

1. **XML definition preview**
   * Displays the full form structure, including:
     * application steps and pages (`<system:Page>`),
     * base and composite components,
     * definitions of visibility and listening conditions (`<data:ListeningOn>`, `<data:ClearOn>`),
     * grid layout (`<system:Page.layout>`),
     * translations (`titleKey`, `labelKey`).
2. **Manual editing**
   * In the **Source** you can edit the application's XML code—for example, adjust layout parameters, change the number of columns, or add attributes not present in the graphical interface.
   * This is especially useful when working with more advanced properties, such as:
     * `numColumns` – number of columns on the page,
     * `horizontalSpan` – the component width in columns.
3. **Validation**
   * The system automatically validates XML syntax, and errors (e.g. missing closing tags, incorrect attributes) are flagged in the editor.
   * If a save error occurs, the form will not be saved in the repository.

**Example code snippet in the Source tab**

```xml
<system:Page id="Page3" mid="Page3" page="3" titleKey="Page3.title" fixedColumns="true">
    <p1:GesText id="GesText3" mid="GesText3" labelKey="GesText3.label" textKey="GesText3.text">
        <data:ListeningOn/>
        <data:ClearOn/>
        <p1:GesText.layoutData>
            <ns6:GridData horizontalAlignment="FILL" horizontalSpan="10" verticalAlignment="CENTER"/>
        </p1:GesText.layoutData>
    </p1:GesText>
    <system:Page.layout>
        <ns6:GridLayout makeColumnsEqualWidth="true" numColumns="12"/>
    </system:Page.layout>
    <data:Curtains/>
</system:Page>
```

The above code shows the definition of the form page with identifier 'Page3' with one label component 'GesText&#x33;*'* and a page layout in 12 columns.

## **Best practices**

* Editing in the tab **Source** should be done carefully - preferably after saving the current version of the form.
* Before making changes, it is worth checking their impact on the form in the tab **Request**.

## **Use cases**

* **Changing the number of columns** (`numColumns`), when it is not available in the graphical interface.
* **Moving page or component definitions** between forms.
* **Finding dependencies of a given component** before deleting it.

## **FAQ**

**Are changes made in Source visible immediately?**\
Yes, changes are visible after saving or switching to another editor tab.

**Can only a fragment of XML be edited?**\
Yes, any element can be edited - both a component and an entire page block - as long as the syntax is valid.

**Does the Source tab also show translations and styles?**\
Yes, translation keys are visible (`*.labelKey`, `*.titleKey`) as well as CSS classes associated with components or pages.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FcmfgfJKeIf9Lx5GQPYhX%2Fobraz.png?alt=media&amp;token=0da82c9c-0cc0-4016-8a01-296de4656cb1" alt=""><figcaption><p><em><strong>Figure 1.</strong> View of the “Source” tab in the application editor</em></p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/podglad-definicji-formularza-xml.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.