Configuration Changes

Network Locator Client

The path in the URL to the Network Locator Client has been modified in this release for better clarity. It has changed from landing-page to locator-client. After the upgrade, you can now access the Locator Client at:

https://<KUBERNETES-BASE-URL>/api-network-locator-gateway-<namespace>/locator-client/

Storage Service

For enhanced security during file uploads, you can now configure file upload settings in the storage service. These settings are not automatically applied to your configuration. Please manually apply the necessary changes. The following parameters can be adjusted to meet your requirements:

▪allowed-file-extensions

▪max-file-name-length

▪max-file-size-bytes

Since templates for dynamic documents and emails are provided as HTML or Qute files, it is strongly recommended to keep at least the *.html and *.qute file types in the allowed-file-extensions parameter.

Example Configuration:

{
"vertigis": {
"storage": {
"expiration": {
"schedule-cron": "0 0 6 * * ?"
},
"locator-result": {
"expiration": {
"duration": 3,
"enabled": true
}
},
"security": {
"file-upload": {
"allowed-file-extensions": ".html,.pdf,.qute,.png",
"max-file-name-length": 100,
"max-file-size-bytes": 1000000,
"mime-type-mapping": {
".7z": "application/x-7z-compressed",
".csv": "text/csv",
".docx": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
".gif": "image/gif",
".gz": "application/gzip",
".html": "text/html",
".jpeg": "image/jpeg",
".jpg": "image/jpeg",
".json": "application/json",
".pdf": "application/pdf",
".png": "image/png",
".pptx": "application/vnd.openxmlformats-officedocument.presentationml.presentation",
".qute": "application/xslfo+xml",
".rar": "application/vnd.rar",
".svg": "image/svg+xml",
".tar": "application/x-tar",
".txt": "text/plain",
".webp": "image/webp",
".xlsx": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
".xml": "application/xml",
".zip": "application/zip"
}
}
}
}
}
}

Process Manager

For better clarity, we have renamed the two templates involved in the review mode. Please update the configuration in the Process Manager as described here:

Replace:

"manual-process-agent": {
"file-id": "locator-templates@mail@requestManualProcessAgent.html",
"subject": "[Network Locator] Plan Information - Manual Process Agent - {request_id}"
},
"manual-process-extern": {
"file-id": "locator-templates@mail@requestManualProcessExtern.html",
"subject": "[Network Locator] Plan Information - Manual Process - {request_id}"
}

with:

"review-agent": {
"file-id": "locator-templates@mail@requestReviewAgent.html",
"subject": "[Network Locator] Plan Information - Review Agent - {request_id}"
},
"review-extern": {
"file-id": "locator-templates@mail@requestReviewExtern.html",
"subject": "[Network Locator] Plan Information - Review - {request_id}"

}

Locked Areas

A new Qute variable {agent_comment} is now available for use in Mail Templates and Dynamic Document Templates. By including this snippet in your templates, you ensure that the message entered by the internal agent during the review process is forwarded to the end user.

{#if agent_comment??}
<fo:block font-size="11pt" font-weight="bold">Internal agent comment: {agent_comment}</fo:block>
{/if}

Templates can be edited in the Locator Admin Client under Process Manager > Templates.

HELM Deployment

In previous releases, sensitive data such as passwords had to be provided directly in the Helm values. To enhance security, you now have the option to reference a secretName instead. Check the values.yaml file in Deploy Network Locator Web Services for more details.

Step by Step Upgrade Instructions

1.Deploy the Solution Package for version 1.3 using Solution Manager.

2.Create Kubernetes secrets for sensitive data.

You can either create secrets manually, or you can use the provided code snippet to create the secrets using a command line:

kubectl create secret -n <NAMESPACE> generic keycloak-admin-password-secret \
--from-literal=password=<KEYCLOAK-ADMIN-PASSWORD>
kubectl create secret -n <NAMESPACE> generic keycloak-postgres-password-secret \
--from-literal=password=<KEYCLOAK-POSTGRES-PASSWORD> \
--from-literal=postgres-password=<KEYCLOAK-POSTGRES-ADMIN-PASSWORD>
kubectl create secret -n <NAMESPACE> generic portal-secret \
--from-literal=username=<PORTAL-USER-NAME> \
--from-literal=password=<PORTAL-PASSWORD>
kubectl create secret -n <NAMESPACE> generic mailer-secret \
--from-literal=host=<HOST> \
--from-literal=ssl=<USE-SSL> \
--from-literal=start-tls=<STARTTLS> \
--from-literal=start-tls-enabled=<START-TLS-ENABLED> \
--from-literal=port=<PORT> \
--from-literal=username=<USERNAME> \
--from-literal=password=<PASSWORD> \
--from-literal=from=<FROM-MAIL>
kubectl create secret -n <NAMESPACE> docker-registry registry-secret \
--docker-server=vertigisapps.azurecr.io \
--docker-username=<USERNAME> \
--docker-password=<PASSWORD>

3.Modify your existing values.yaml.

▪Replace the sensitive data with the secret references from the previous step.

▪Update the appUrl parameter for Cockpit and Landing Page with the values from the solution deployment.

4.Modify the existing Process Manager configuration in Admin Client (see Process Manager Configuration).

It's important that you do this before upgrading to version 1.3

5.Modify the existing Storage Service Configuration in Admin Client (see Storage Configuration).

It's recommended that you do this before upgrading to version 1.3

6.Perform HELM uninstall of the existing deployment.

helm uninstall <RELEASENAME> --namespace <NAMESPACE>

You won't lose any data during uninstallation, as Locator uses persistent volumes to store important data that remain intact and will be reused when you deploy the new version.

7.Perform HELM install with the new version.