> 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/eksploatacja-aplikacji/webforms/konfiguracja/przekierowania-wewnetrzne.md).

# Eximee internal redirections

{% hint style="info" %}
Availability of functionality depends on the license and may not be available in all deployments.
{% endhint %}

Eximee internal redirect is a redirect from a form to another Eximee form, in which the platform itself passes selected parameters to the target form, for example the source of entry or channel. The form author does not have to append them manually to the redirect address. The list of passed parameters is set by the environment administrator in the file `webforms.xml`.

## Marking a redirect as internal

To mark a redirect as internal, select the field in Designer **Eximee internal redirect**. The field is available:

* in a navigation action – in the action row, under the method and field **Redirect link** (see [Navigation actions](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/przeplywy/akcje-nawigacyjne.md)),
* in the REDIRECT action – in the action details, in the row **Redirect type** (see [Actions](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/przeplywy/akcje.md)).

Parameters are appended to the marked redirect:

* after moving to the next page, going back to the previous page, and saving the application (navigation actions),
* when going to a selected page, for example with the buttons **Back** and **Next** browser,
* after calling the REDIRECT action.

A redirect without the field selected works as before – the platform does not change its address.

{% hint style="warning" %}
Select the field only when the address leads to an Eximee form. The platform does not check the target address, so marking a redirect to an external site will pass the parameters from the list to that site.
{% endhint %}

## Configuration

The list of parameters is specified in the file:

```
/etc/eximee/webforms.xml
```

in the element `eximee.internal-redirect.parameters`, as comma-separated names:

```xml
<webforms>
    <eximee>
        <internal-redirect>
            <parameters>SOURCE,channel,idKampanii</parameters>
        </internal-redirect>
    </eximee>
</webforms>
```

**Default value:** empty list. Then a redirect marked as internal does not receive any parameter.

{% hint style="info" %}
Changes to the list take effect after restarting the Webforms application. Forms do not need to be redeployed.
{% endhint %}

## Rules for appending parameters

* The redirect receives every parameter from the list whose name is not already in the address. A parameter specified in the address by the form author retains its value, including an empty one (for example `idKampanii=`).
* Parameter names are compared case-sensitively: `idKampanii` and `idkampanii` are two different parameters.
* The parameter value is the value of the form session variable with that name at the time of redirection, including when changed by the form logic. Exceptions:
  * `channel` gets the value `native`, when the form runs in a mobile app; outside it, the parameter is not appended,
  * `SOURCE` gets the source with which the form was launched.
* A parameter without a value is not appended.
* For GET method, parameters are added to the end of the address, in the order from the list, before the fragment `#`. For POST method, they are placed in the fields of the submitted form. Values are encoded so that the target form reads them unchanged.

{% hint style="warning" %}
For GET method, parameter values are visible in the address, browser history, and Referer header. If the list contains a parameter with sensitive data, for example the client session identifier, set the method to POST in the action.
{% endhint %}

## Example

The parameter list in `webforms.xml` is `SOURCE,channel,idKampanii`. Navigation action with the field selected **Eximee internal redirect** has GET method and redirect link:

```
https://wnioski.example.com/app/wniosek-docelowy/index.html?idKampanii=wiosna#start
```

The client opened the form in the browser with the parameter `SOURCE=www`, and the session variable `idKampanii` has value `autumn`. After moving to the next page, the target form will open at the address:

```
https://wnioski.example.com/app/wniosek-docelowy/index.html?idKampanii=wiosna&SOURCE=www#start
```

* `SOURCE` was appended before fragment `#start`.
* `idKampanii` retained the value `spring` from the redirect link.
* `channel` was not appended because the form runs in the browser.

If the action had the POST method, the target form would receive the fields `idKampanii=wiosna` and `SOURCE=www`, and the redirect address would not contain parameters.

## Troubleshooting

If a parameter from the list did not reach the target form, check whether:

* the field is selected in the action **Eximee internal redirect**,
* the name in `webforms.xml` has the same letter case as the session variable,
* the redirect link already does not contain a parameter with that name, including one with an empty value,
* the session variable has a value at the time of redirection,
* the Webforms application was restarted after changing the list.


---

# 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/eksploatacja-aplikacji/webforms/konfiguracja/przekierowania-wewnetrzne.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.
