# 13.28.1

{% hint style="info" %}
**Release date 18-05-2026**
{% endhint %}

## New Features

* **Dutch address support in map widgets**

  The map widget can now render a layer that points at a Dutch address object instead of a GeoJSON geometry. Valtimo geocodes the address to a WGS84 coordinate via the [PDOK Locatieserver](https://api.pdok.nl/bzk/locatieserver/search/v3_1/ui/) and renders the result as a `Point`. See the [Map widget documentation](/features/case/tabs/widgets.md) for the full list of recognised fields and a configuration example.
* **Zaak sync (per case definition)**

  A new "Zaak-synchronisatie" admin panel under `Admin > Cases > {Case name} > [ZGW]` configures how Valtimo propagates case changes to the linked zaak in the Zaken API, scoped per case definition. Two one-way synchronisations (Valtimo → Zaken API) are now available:

  * **Behandelaar sync** — when the dossier assignee changes, the linked zaak gets a behandelaar rol matching the assignee.
  * **Note sync** — Valtimo notes on the case are mirrored as `ZaakNotitie` on the linked zaak.

  See the [Zaak sync section](/features/case/zgw/zaken-api-sync.md) for details.
* **Admin settings**

  A new admin settings page is available under the Admin menu for managing the application logo (light and dark mode, PNG or SVG), customizing the accent color palette, and toggling front-end feature flags at runtime. The accent colors section lets administrators override the ten CDS color levels (color 100 through color 10) with a color picker. Changes take effect immediately in the current session; other sessions pick up the new values on their next page load. Logos, accent colors, and feature toggle overrides can be auto-deployed from classpath resource files using the importer framework. See the [admin settings documentation](/features/admin-settings.md) for details and the [front-end migration guide](/release-notes/13.x.x/13.28.1/front-end-migration.md) for setup instructions.

## Enhancements

* **Persistent page sizes per case definition for task list and case list**

  When a user configures the page size for a case definition, either for the task or case list, this is remembered. Next time they visit the task or case list for that case definition, the same page size is shown.
* **Person card widget**

  A new `person-card` widget type displays personal data for a single person (full name, birthdate, BSN, phone, email and city) in a compact card format on the case detail page. Field values are configured as JSON paths into the case document, and only the full name is required — empty fields are hidden in the rendered card. See the [Person card widget documentation](/features/case/case-detail/tabs/widgets.md) for the full list of fields and a configuration example.
* **Metroline widget**

  A new `metroline` widget type visualises the progression of a status as an ordered set of steps, similar to a metro-line diagram. The currently active step is highlighted and completed steps display the date and time they were reached. When a label is available for a step, an info toggletip is shown next to it so the label can be read on demand. Steps can be laid out horizontally or vertically, and are driven either by the internal case status history or, when the `zaken-api` module is on the classpath, by the statustypen of the linked zaaktype. See the [Metroline widget documentation](/features/case/case-detail/tabs/widgets.md) for the full configuration.
* **Highlight widget**

  A new `highlight` widget type emphasises a single value or the count of items in a collection on the case detail page. The configured JSON path resolves to a primitive value (string, number, boolean). Highlight widgets are always one column wide, use the selected accent colour for the left border and optional icon, and can include an optional action button (process or link). See the [Highlight widget documentation](/features/case/case-detail/tabs/widgets.md) for the full list of configuration options.
* **Generic case list**

  A generic case list can be used instead of the default case list with case definitions listed in the sidebar. The generic case list shows cases across all case definitions similar to the task list. This feature needs to be enabled in the angular configuration file(s) in order to make use of it, via the `enableGenericCaseList` property.
* **Improved actuator endpoint security**

  Endpoints added to `management.endpoints.web.exposure.include` are now automatically protected — no filter chain override needed.
* **Hardened anonymous health responses**

  Anonymous calls to `/actuator/health` only return the overall status; component details require the actuator role. Kubernetes probes and load balancers are unaffected.

  <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>Health groups (e.g. <code>liveness</code>, <code>readiness</code>) configured with <code>show-details: ALWAYS</code> previously exposed component details to anonymous callers. They are now also reduced to status-only for unauthenticated requests. Authenticate with the actuator role to keep seeing details.</p></div>
* **Faster Case Progress tab**

  The Progress tab on the case details page now loads noticeably faster, especially for cases with many associated processes.
* **Open widget link in a new browser tab**

  Link-type action buttons on case widgets now support an "Open in new tab" option in widget management. When enabled, clicking the button opens the configured URL in a new browser tab instead of replacing the case detail page.
* **`noteEventListenerEnabled` and `noteSubject` removed from the Zaken API plugin**

  These two properties moved off the Zaken API plugin and onto the new per-case-definition Zaak sync configuration (renamed to `noteSyncEnabled` and `noteSubject` respectively). The plugin now only owns connection settings; per-case-definition policy lives in the new "Zaak-synchronisatie" panel.

  See the [Zaak sync section](/features/case/zgw/zaken-api-sync.md) for details.

## Bugfixes

* SmartDocuments compatibility with newer SmartDocuments versions.
* When a header widget was configured, it was not possible to edit the header widget.
* Fixed a permission issue on the task endpoint that prevented assignee details from being resolved for users without permission to look up other users.
* Fixed a bug where the enumeration display type when configuring task columns was not editable.
* Quick search tooltip on the case list no longer gets cut off when the trigger is near the viewport edge; the tooltip now repositions automatically to stay on screen.
* Fixed a bug where the frontend code could not be compiled because of error: `Can't resolve ...@ibm/plex...`
* **Recover from stuck migration locks**

  If an application instance was killed mid-migration, the migration lock could stay held and prevent other instances from starting. Valtimo now releases such stale locks automatically on startup and on graceful shutdown.


---

# 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.valtimo.nl/release-notes/13.x.x/13.28.1.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.