- Introduction
- Getting started
- Managing solution projects and packages
- Managing solution deployments
Solutions user guide
Upgrading or downgrading a solution
The Upgrade / Downgrade option allows you to perform the following changes:
- Upgrade your solution to a newer version.
- Downgrade your solution to an older version (similar to a rollback to an older version).
Downgrading a solution does not delete entities, choice sets, and webhooks.
To upgrade a solution, take the following steps:
When a newer package version is available for a deployment, the Deployments table shows an Upgrade icon 
inside the Version column. You can start the upgrade flow directly from the table; this opens the same upgrade workflow described below.
-
Update your solution package with the changes you want to include in the new version. For details, refer to Editing a solution package version.
If a component with the same name already exists in the tenant, you can choose one of the following options:
- Keep the existing component and do not create an additional one.
- Keep the existing component and add additional new fields from the solution. This option does not alter existing fields.
- Rename the conflicting resource in the respective service (for example, Orchestrator or Action Center) in the target tenant.
- Rename the resource in the solution deployment, if possible.
-
Select the Solutions tab at the tenant level.
-
In the Deployments tab, select the three-dot menu corresponding to the targeted package, then choose Upgrade / Downgrade.
-
In the Upgrade / Downgrade window, indicate the package version you want to upgrade or downgrade your solution to, then select Continue.
A new screen opens, providing a summary of the changes introduced by the upgrade operation. The following details are shown:
-
Newly added components, marked with a plus (+) icon. These components will be created in the target environment after the upgrade, so make sure to review their properties.
-
Removed components, marked with a minus (-) icon. These components will be removed from the target environment after the solution upgrade unless they are referenced by other solutions. In this case, the components remain in the environment but are removed from the solution.
-
Edited components, marked with an asterisk (*) icon. The Compare property differences panel highlights all changes to the component properties.
Components that only have changes to configurable properties are not marked as edited. Edited components retain their existing configuration values for configurable properties by default, but you can switch to using the package configuration. If needed, you can update configurable properties directly. To review all property-level changes, use the Compare property differences panel.
-
-
Optionally edit any configurable component properties.
-
Save your changes as a draft, validate them, and/or deploy them.
After performing an upgrade, you can check the operation status in the Deployments tab. For details, see Checking the deployment status.
After an upgrade or downgrade, the deployment status is Inactive. Inactive deployments are further classified as Inactive (Ready to activate) or Inactive (Needs setup to activate), depending on whether additional configuration is required before activation. You must manually activate the deployment for the solution to become functional.
