This chapter details the configuration changes from v1.3 to v1.4 and provides a step-by-step guide for the upgrade process.
Step by Step Upgrade Instructions
1.Deploy the Solution Package for version 1.4 using Solution Manager. Don't forget to set the sharing level of the portal items (see Deploy Network Locator Web App)
2.Modify your existing values.yaml.
▪Update the appUrl parameter for Cockpit and Landing Page with the values from the solution deployment.
Since we have upgraded the RabbitMQ version, you need to manually delete the persistent volume claim (PVC) associated with RabbitMQ. The PVC is typically named: data-network-locator-rabbitmq-0. This volume does not contain any mission-critical data, so it is safe to delete.
3.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.
4.Perform HELM install with the new version.
helm install <RELEASENAME> oci://vertigisapps.azurecr.io/network-locator/helm-chart \
--namespace <NAMESPACE> \
-f values.yaml \
--wait \
--version 1.4.0 \
--timeout 15m0s \
The following new possibilities are optional. You can perform a successful update even if you choose not to configure them immediately.
In our default shipment we have added a download link to the NoResult template, enabling users to download a ZIP file containing the official letter document even when a locate request returns no results.S
Note: If you are upgrading from a previous version, the template will not be updated automatically. To enable this feature, you need to manually add the following code snippet to the NoResult template:
<table border="0" cellpadding="10" cellspacing="0" class="button_block block-4" role="presentation" style="mso-table-lspace: 0pt; mso-table-rspace: 0pt;" width="100%">
<tr>
<td class="pad">
<div align="center" class="alignment">
<!--[if mso]>
<v:roundrect
xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:w="urn:schemas-microsoft-com:office:word"
href="{download_url}"
style="height:42px;width:111px;v-text-anchor:middle;"
arcsize="10%"
stroke="false"
fillcolor="#348844"
>
<w:anchorlock/>
<v:textbox inset="0px,0px,0px,0px">
<center style="color:#ffffff; font-family:Tahoma, Verdana, sans-serif; font-size:16px">
<![endif]-->
<a href="{download_url}" target="_blank" style="text-decoration:none; display:inline-block; color:#ffffff; background-color:#348844; border-radius:4px; width:auto; border-top:0px solid transparent; font-weight:undefined; border-right:0px solid transparent; border-bottom:0px solid transparent; border-left:0px solid transparent; padding-top:5px; padding-bottom:5px; font-family:'Roboto', Tahoma, Verdana, Segoe, sans-serif; font-size:16px; text-align:center; mso-border-alt:none; word-break:keep-all;">
<span style="padding-left:20px; padding-right:20px; font-size:16px; display:inline-block; letter-spacing:normal;">
<span style="margin:0; word-break:break-word; line-height:32px;">
Download
</span>
</span>
</a>
<!--[if mso]>
</center>
</v:textbox>
</v:roundrect>
<![endif]-->
</div>
</td>
</tr>
</table>
We have also added a new Qute variable, affected_groups, which allows you to include dedicated text elements in your letter document depending on whether any intersection groups have been affected. Here is a sample how this can be used in the letter template:
<fo:block-container top="130mm" left="0mm" width="170mm" height="50mm" absolute-position="absolute" z-index="1" border="0.1mm solid white">
<fo:block font-size="11pt" space-before="10pt">Sehr geehrte Damen und Herren,</fo:block>
<fo:block font-size="11pt" space-before="11pt" text-align="justify">
Entsprechend Ihrer Anfrage und auf Grundlage der beigefügten Begleitdokumente erhalten Sie eine Leitungsauskunft der VertiGIS GmbH.
</fo:block>
{#if affected_groups??}
<fo:block font-size="11pt" space-before="11pt" text-align="justify">
Folgende Sparten sind innerhalb Ihres Anfragbereiches betroffen:
{#for affected_group in affected_groups}
{affected_group}{#if affected_group_hasNext}, {/if}
{/for}
</fo:block>
{#else}
<fo:block font-size="11pt" space-before="11pt" text-align="justify">
In Ihrem Anfragbereich ist keine Sparte betroffen.
</fo:block>
{/if}
<fo:block font-size="11pt" space-before="11pt" text-align="justify">
Die Auskunft beinhaltet:
</fo:block>
<fo:block font-size="11pt" space-before="11pt" margin-left="10mm">- dieses Anschreiben</fo:block>
{#if affected_groups??}
<fo:block font-size="11pt" margin-left="10mm">- Planauskünfte für Sparten als PDF</fo:block>
{/if}
{#if group_results??}
{#for group_result in group_results}
{#if group_result.has_intersection is false}
<fo:block font-size="11pt" margin-left="10mm">- Negativauskunft für die Sparte '{group_result.group_id}'</fo:block>
{/if}
{/for}
{/if}
{#if added_static_documents??}
<fo:block font-size="11pt" margin-left="10mm">- {added_static_documents.size()} zusätzliche Dokumente</fo:block>
{/if}
<fo:block font-size="11pt" space-before="11pt" text-align="justify">Alle Dokumente sind Bestandteil dieser Auskunft.</fo:block>
<fo:block font-size="11pt" space-before="11pt" text-align="justify">Dieses Schreiben wurde maschinell erstellt und trägt daher keine Unterschrift.</fo:block>
<fo:block font-size="11pt" space-before="22pt">Mit freundlichen Grüßen,</fo:block>
<fo:block font-size="11pt">VertiGIS GmbH</fo:block>
<fo:block font-size="11pt">Abteilung Dokumentation</fo:block>
</fo:block-container>
You can now configure a maximum allowable request area. Setting a value is optional — if no value is specified, a default limit of 50,000 m² will be applied automatically.