This chapter outlines the changes introduced in version 1.11 and provides a step-by-step guide  for upgrading from version 1.10.

Before You Upgrade

•Back up your configuration — Save the Process Manager, Storage, and Sync Service settings from the Admin Client to local files, just in case.

•Locator-UI workflow — The locator-UI workflow is automatically provisioned on every deployment, including upgrades. Any custom modifications you have made to the locator-UI workflow will be overwritten. Before upgrading, export and back up your current workflow. After the upgrade, manually re-apply your customizations on top of the updated workflow, which now includes the human-readable Request ID display and missing French/Italian address field translations.

•Context path configuration (optional) — The API Gateway context path can now be left empty to deploy without a URL path prefix. Additionally, Keycloak context path is now explicitly configurable via the new global.keycloak.contextPath helm value (default: keycloak-instance-{{ .Release.Name }}), which can also be left empty. If you do not need to change these values, no action is required. Note: both paths must not be empty at the same time, as this would cause a routing conflict.

Step by Step Upgrade Instructions

1.Make sure you have a valid connection to your kubernetes cluster

2.Login to the VertiGIS Container Registry

a.helm registry login vertigisapps.azurecr.io

3.Deploy version 1.11 using HELM.

helm upgrade <RELEASENAME> oci://vertigisapps.azurecr.io/network-locator/helm-chart \
   --namespace <NAMESPACE> \
   -f values.yaml \
   --wait \
    --version 1.11.0 \
    --timeout 30m0s \

After the Upgrade

•Workflow changes (optional) — Re-apply your workflow customizations as described above

•Custom mail and document templates (optional) — Existing customized templates are preserved and will not be overwritten during upgrade. If you want to include the new human-readable Request ID in your templates, add the {display_id} Qute variable where desired (e.g., in email subjects or document headers).