> For the complete documentation index, see [llms.txt](https://abb-vlaanderen.gitbook.io/informatie-oph/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://abb-vlaanderen.gitbook.io/informatie-oph/release-notes/release-notes/versie-2.4.2-08-09-2025.md).

# Versie 2.4.2 08/09/2025

Releasenotes voor versie 2.4.2, gereleased op 08/09/2025 in het Nederlands en het Engels. App: v2.4.1 - Frontend: v1.4.0 - BPMN service: v2.1.0 - Visio service: v1.0.0

## Verbetering

* Er werd een knop toegevoegd naast de naam van het proces dit toelaat om snel en eenvoudig de URL voor de informatiepagina van het proces te kopiëren (je kan ook gewoon de URL kopiëren). 
* De URL van een proces brengt je meteen naar de informatiepagina van het proces. 

## Bugfixes

* Een nette "Niet gevonden" pagina wordt getoond als een niet-bestaande proces-URL wordt gebruikt. 
* Als een gebruiker toegang wil krijgen tot procesinformatie op een moment dat de gebruiker nog niet is geauthenticeerd, wordt de gebruiker omgeleid om aan te melden. 
*

## Enhancements

* A button next to the process name allows for quickly copying the process's URL (or just copy URL)
* URL for a process will take the user directly to that process

## Bugfixes

* A proper *Not found* page is shown when a non-existent process URL is accessed
* When trying to access a process unauthenticated, the application redirects to the login page


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://abb-vlaanderen.gitbook.io/informatie-oph/release-notes/release-notes/versie-2.4.2-08-09-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.