> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemmodeler/flowcharts/execute-process/change-settings.md).

# Change settings

{% hint style="info" %}
If you need to keep changed settings, it may be necessary to use the Confirm Session Changes process node...
{% endhint %}

## Change language

<figure><img src="/files/bbEC40djOVIJT4LVyBm0" alt=""><figcaption><p>Change node</p></figcaption></figure>

#### Function&#x20;

With the change language process you can change the language of the user's session in the runtime. You can choose languages from the available languages configured in the project settings. You can find a list of all supported languages and their names in the [available languages section](/platform/wemreference/functions/localization/availablelanguages.md).&#x20;

#### Properties

For the change language node, we have the following properties:

| Property name | Type             | Description                     |
| ------------- | ---------------- | ------------------------------- |
| Language      | Expression, text | Language you want to change to. |

#### How to use this node?

There are different ways in which we can implement and use this node, here we will show a basic example that you can later modify according to the need, and the ideas, that you want to implement in your project.

One of the easiest ways to use it:

1. Create a field with the Default Language. In this case we use en-US

<figure><img src="/files/1AuESYhdFTDofqWHcNXd" alt=""><figcaption></figcaption></figure>

2\.    Inside the properties of the change language process node you insert the datafield you just mad&#x65;***.***

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

3. Create an interaction that triggers the change language process, in this case we will use a button that activates the process

<div data-full-width="false"><figure><img src="/files/RuBDfaVPfjbqK7e51HCy" alt=""><figcaption></figcaption></figure></div>

#### **Flowchart**

For the [flowchart](/platform/wemmodeler/flowcharts.md), connect from the start node to the interaction node where you want to change the language from. Next is to add the button exit "change" to the process node and connect the default exit back to the interaction screen.&#x20;

<figure><img src="/files/Z0JXI9sEiUyvceGocLod" alt=""><figcaption><p>Using the change language node.</p></figcaption></figure>

Inside the node properties; put which language the project is going to change into, as the example below shows.

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

{% hint style="info" %}
**Note:** before any languages can be used, they must be available in the project languages in the [configuration](/platform/wemmodeler/project-settings/project-configuration.md#languages) part of the project.&#x20;
{% endhint %}

<figure><img src="/files/ITcHrsempV6rpJTVxNOR" alt=""><figcaption><p>where to find out.</p></figcaption></figure>

## Change Timezone&#x20;

![](/files/WJU9Qov4LN3GeCj9Scke)

#### Function

This process is to change the timezone in the current project. It is important when we handle several timezones within our project. WEM supports the [IANA Standard Time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) and uses the tz identifier to name the timezones.&#x20;

#### Properties

For the change timezone node, we have the following properties:

| Property name | Type             | description                                                                                                                         |
| ------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Timezone      | Expression, text | Set the timezone in the expression. This can be a text datafield a expression or a string. Use the tzidentifier from the IANA list. |

#### Flowchart

For the [flowchart](/platform/wemmodeler/flowcharts.md), connect from the interaction node to the change language node. In the following example we will be using the start node  by default; an interaction node, and the change timezone node as shown below.

For the flowchart, connect from the start to the interaction node, from interaction to the change timezone node and back to the interaction again for the result.

<figure><img src="/files/Ov5DEbvI1s91cTS8Uh22" alt=""><figcaption><p>Sample case</p></figcaption></figure>

1. Use an interaction node, and put the change timezone node next to the interaction node in the flowchart.&#x20;
2. Create a field that hold a the timezone you want to change to or put the name in the process node properties.
3. Create an exit that will go to the node to execute the process and use the default exit to go back to your interaction node.&#x20;
4. Add a button that triggers the exit in your interaction node and a label that shows the current timezone.

<figure><img src="/files/3BxXFJ9gXzDr9l7EmiU4" alt=""><figcaption></figcaption></figure>

## Confirm session changes&#x20;

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

#### Function

Its function is to confirm if a session fields is changed and keep its information during this session without specifically making a post or other update (following an exit from a page). The node can be linked to an exit from another node and needs the default exit to have a next step. It will send the changes in session fields at the client/browser to store them on the server in the current session. Very useful in cases where a change in fields on a page can trigger an execute flowchart (containing the confirm session) but return back to the main page - in which case the session on server is not updated (that would only be when user follows an Exit) and the user wants to navigate away using a Navigation Item (without the Confirm Session, the changes will be lost to this session).&#x20;

## Sleep&#x20;

#### Function

This function is to set a wait time before the runtime goes to the next node.

#### Properties

The properties allow us to connect the elements of our project to the process options. For this sleep node, we have the following propertie:

<table><thead><tr><th width="249.33333333333331">Property name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>Seconds (max 5)</td><td>Expressions, number</td><td>Set the time in the node that will take to sleep the process.</td></tr></tbody></table>

#### How to use this node?

The following example will show the time in seconds it takes to execute the action of the sleep node.

The objective of this project is basically to visually show the time that the process takes to execute the "sleep" time that is part of the configuration; The process is explained in detail below. For this example project, two values, one initial and one final, are compared, using the assignment of a function type date to give a parameter between both fields. Initial date that starts from one point and ends at another; between this space the time of the sleep node process is calculated.

<figure><img src="/files/tX5hh76cwTnqEo5BGQyU" alt=""><figcaption><p>Sample case</p></figcaption></figure>

1. The [interaction node](/platform/template-editor/interaction.md).
2. Add an [assignment node](/platform/wemmodeler/flowcharts/assignment.md) with the advanced function "[now()](/platform/wemreference/functions/date/now.md)" that will compare the first number.
3. Add an [assignment node](/platform/wemmodeler/flowcharts/assignment.md) with the advanced function "[datePart](/platform/wemreference/functions/date/datepart.md)", that will have the start date day, which will compare the first number.
4. An overlay is added to show the executed process in progress.
5. The sleep node has been added with 3 seconds in its property max time.
6. Add an [assignment node](/platform/wemmodeler/flowcharts/assignment.md) with the advanced function "[now()](/platform/wemreference/functions/date/now.md)", that will compare the second number.
7. Add an [assignment node](/platform/wemmodeler/flowcharts/assignment.md) with the advanced function "[datePart](/platform/wemreference/functions/date/datepart.md)", that will have the end date day, which will compare the second number.
8. The next assignment node will receive the information of the time.

<figure><img src="/files/Srz4DBbhQWCSWtzRcpHb" alt=""><figcaption><p>The interaction node of sleep node process</p></figcaption></figure>

#### Node operation process.

Describing the process of the flowchart in the preview. Detailed after executing the project.

1. Before clicking the sleep button.&#x20;

   <figure><img src="/files/57d63JmySeLTf8yvgarp" alt=""><figcaption></figcaption></figure>
2. The processed overlay, while the node is been executed.

   <figure><img src="/files/Kws2QieVqLGHDLysAluZ" alt=""><figcaption></figcaption></figure>
3. The result of the compared fields within the time and sleep process node.

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

## Redirect&#x20;

#### Function

This processes is to redirect the user/browser to a specific url - without the need to let user click a link to go there. In this use case, we will be showing a simple way to use it, just as an illustration.

#### Properties

The properties allow us to connect the elements of our project to the different process parameters of their function. For this redirect node, we have the following:

<table data-header-hidden><thead><tr><th width="249.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Property name</strong></td><td><strong>Type</strong></td><td><strong>Description</strong></td></tr><tr><td>Url</td><td>Expressions, text</td><td>Set the url address where the user will be redirected to.</td></tr></tbody></table>

#### How to use this node?

For the [flowchart](/platform/wemmodeler/flowcharts.md), connect from the interaction node to the redirect node as shown below.

One of the easiest ways to use it:

<figure><img src="/files/PeLfEJMqD8AGVxIx5u1E" alt=""><figcaption><p>Sample case</p></figcaption></figure>

1. Use an interaction node, and put the redirect node on the canvas.
2. Create an exit that will go to the node to execute the process.

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

3. Set up the redirect node properties to a string with the url you want to point to. The property field is a expression and can be used with a text datafield, with expressions or directly with an url string. This example uses `"www.google.com"` as string.&#x20;

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

#### Node operation process.

1. Before clicking the "redirect" button, which also is shown as button most of the time.

&#x20;![](/files/KFtz3TcZg0lM2qsYkY41)

2. Then, you will go to the URL set, in this case, "google.com"

## Webrequest&#x20;

Webrequest, is the legacy version of the [**"HTTP"**](/platform/wemmodeler/flowcharts/http-request.md) node , which connects with any action of request, *get, put, post, delete,* etc... This node is updated to a more user-friendly way, for more information about its improvement, you can visit the documentation page with more details.

{% hint style="info" %}
Find out more information[ **about web-requests.**](/platform/wemmodeler/flowcharts/http-request.md)
{% endhint %}


---

# 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.wem.io/platform/wemmodeler/flowcharts/execute-process/change-settings.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.