# Updating Applications

The **application update process** allows you to roll out new versions of applications to all devices where earlier versions of those applications are currently configured or deployed. The update flow is organized into three steps, guiding you through selecting affected devices, configuring deployment, and finalizing and monitoring the rollout.

### 1. Devices

The first step of the update process lists all devices that are either configured to use an earlier version of the selected applications or have an earlier version currently deployed.

It also lets you choose which of these devices to include in the update.

<figure><img src="/files/re6Fn5LevAvMxZlREiSk" alt=""><figcaption><p>Application update, step 1 - selecting devices.</p></figcaption></figure>

Having selected the devices to update, proceed to the deployment configuration by clicking Next.

### 2. Deployment

This phase summarizes what will be updated and lets you determine weather the update should be deployed or not. You can now configure the deployment action for each affected device. The options are:

* **Do not deploy the update:** Only update the device configuration, but do not deploy the changes.
* **Deploy the update now:** Update and deploy immediately.
* **Deploy the update at a specified time:** Update and deploy the changes at a selected time.

<figure><img src="/files/92Vf4gSnb7YgCTAE7FFg" alt=""><figcaption><p>Application update, step 2 - configuring deployment.</p></figcaption></figure>

### 3. Finalize

After confirming the deployment settings, the update process is finalized. All pending updates are listed for all devices, where changes to the modules on each individual device can be viewed.

The possible module operation types are:

* **Added**: Module is added to the device.
* **Removed**: Module is removed from the device.
* **Modified**: Module version is changed.

{% hint style="info" %}
Updating an application version can cause side effects. If the device used an application several versions old, modules can have been added or removed in the newest version.
{% endhint %}

<figure><img src="/files/xiUbrNHwj68iXVqN5RjY" alt=""><figcaption><p>Application update, step 3 - finalizing.</p></figcaption></figure>

When all changes are reviewed, the update process can be started by clicking the Approve Update button.

<figure><img src="/files/ZQRVOlHj8m9BJ2wPP8Iv" alt=""><figcaption><p>Confirming the update and deployment</p></figcaption></figure>

Click ok will start the process. The device configurations are updated first.

<figure><img src="/files/MrII9nz4pjnT1UY4Gfab" alt=""><figcaption><p>Update process started - updating device configurations.</p></figcaption></figure>

When the device configurations are updated, deployments will start if configured.

<figure><img src="/files/nPYBxEHPxZ88e278vhGk" alt=""><figcaption><p>Update process - deploying to devices.</p></figcaption></figure>

The user does not have to wait for the completion of the deployments. It can be closed, and the deployments will keep running in the background.

To view the progress of the deployments, go to the [Deployment overview](/management-portal/management/deployments.md)


---

# Agent Instructions: 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:

```
GET https://docs.tricloudnexus.io/management-portal/management/update-center/updating-applications.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.

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.
