> For the complete documentation index, see [llms.txt](https://docs.valtimo.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valtimo.nl/release-notes/13.x.x/13.33.0.md).

# 13.33.0

{% hint style="info" %}
**Release date 17-06-2026**
{% endhint %}

## New Features

* **Load a zaak in a form flow**

  A new `zakenFormFlow` bean lets form flows load a zaak from the Zaken API by its `identificatie` through a `getZaak` method that can be used in SpEL expressions (for example `onOpen` or `onComplete`). The full zaak is returned, so any of its fields can be used in subsequent steps or conditions. Access is secured with PBAC: a new `Zaak` resource type with a `view` action ensures only users authorized for the matching zaaktype can load a zaak. See [Load a zaak in a form flow](/features/case/zgw/load-zaak-in-form-flow.md) for details.

## Enhancements

* **Configurable modal size for start forms**

  The process link configuration of a start event now offers the **Modal size** option (Extra small, Small, Medium, Large). When a case is created via the **Start case** button, the start form modal opens in the configured size instead of always being small. If multiple processes can create the case, the modal opens in the size configured for the selected process. When no size is configured the modal keeps its previous default.
* **Value resolver support for Besluiten API plugin date fields**

  In the Besluiten API plugin, the *create besluit* action can now resolve the publication date, shipment date and response deadline from a value resolver expression (e.g. `pv:publicatiedatum` or `doc:/besluit/publicatiedatum`) instead of only a fixed date, selectable per field via an input-type toggle.
* **Building blocks support nested document properties**

  Input and output mappings on building block call activities can now reference nested paths in the case or building block document (e.g. `/person/name`), instead of only top-level properties.
* **Selectable widget layout algorithm**

  The algorithm used to arrange widgets can now be chosen per case widget tab, IKO tab and dashboard. Three options are available:

  * **Default (less gaps)** (`MUURI_GAP_FREE`) — Muuri masonry with gap filling. This is the original behaviour and is used when nothing is configured, so existing configurations are unaffected.
  * **Default** (`MUURI`) — plain Muuri masonry without gap filling.
  * **Gap free** (`BEAUTIFUL`) — a new custom dense-packing algorithm that may reorder widgets within a section to remove gaps, almost always producing a clean layout without holes.

  *Default* and *Default (less gaps)* keep the widgets in their configured order as much as possible but can leave empty space, while *Gap free* reorders widgets to eliminate gaps. The choice can be made in the admin UI (the dashboard edit modal, the case **Edit widget tab** modal and the IKO tab modal) and via auto-deployment through the optional `widgetLayout` property on the dashboard, case widget tab and IKO tab definitions. See the [dashboard](/features/dashboard.md#layout-algorithm), [case widget tab](/features/case/case-detail/tabs/widgets.md#layout-algorithm) and [IKO tab](/features/iko/tabs.md#layout-algorithm) documentation for details.

## Bugfixes

* **Empty building block mapping dropdowns**

  Existing input and output mappings on a building block process link sometimes showed up with empty dropdowns. This has been fixed.
* **Keycloak-based database migrations failed against newer Keycloak servers**

  Database migrations that look up users in Keycloak could fail to start when running against a newer Keycloak version than the one Valtimo ships with. This has been resolved.
* **Misleading plugin configuration error when configuring a building block call activity**

  When a call activity to a building block was missing the required business key configuration, saving the process link failed with a confusing "No plugin configuration mapping provided" message. Valtimo now checks the call activity up front and shows a clear error that points to the missing business key configuration.

## Security

* **Spring Boot upgraded for CVE fixes**

  Upgraded Spring Boot to 3.5.15 to resolve several HIGH-severity CVEs.