version 2025.5 was released on May 30, 2025
¶ Introduction
On this page you will find all the actions included in version 2025.5. This is a so-called major release that also includes new functionalities for the various modules (Case & Document, Integrations, and JOIN Customer Contact) and was released on May 30, 2025.8 weeks after the release of version 2025.5, support for version 2024.11 and the interim minor release 2025.2 will be discontinued. Therefore, make sure to update your locally installed JOIN environment to version 2025.5. See also our SLA.
WDo you want us to update your (locally installed) environment to this version? Then please contact our support team. JOIN Support
Did you know that in addition to installing the update in your on-premise environment, we can also assist with testing? Check this page for all the options.
If you want to know until when we support older versions of JOIN Case & Document, please click here: click here for the SLA
¶ Planning
update cloud environmentsThe schedule for updating your cloud environment can be found on this page.
¶ Installation manual
You can find the installation manual here:
JOIN Case & Document: Upgrade manual JOIN Case and Document
JOIN Customer Contact: Upgrade manual JOIN Customer Contact (upgrade manual JOIN Customer Contact)
JOIN Integrations: Upgrade manual JOIN Integrations (connections and JIA) (Upgrade manual JOIN Integrations)
Update Elastic Search: elastic manual
¶ System requirements
(for local installation) > NOTE: In JOIN Case & Document version 2025.5, Elastic Search 8.15.0 (in addition to the 7.x.x version) is also supported. Reindexing is not necessary if you upgrade Elastic Search to version 8.15.0.
.NET: For JOIN Case & Document (& integrations!) version 4.8 of .NET is required.
Search: for JOIN Case & Document the installation of Elastic Search is required. We support the versions supported by Elastic up to and including version [8.15.0].(https://www.elastic.co/downloads/past-releases/elasticsearch-8-15-0)
Databases: We support SQL Server and Oracle databases (Azure Cloud is SQL Server only). MySQL is not supported.
Server: from version 2023.5 we support JOIN in combination with Windows Server 2022. Our cloud environments have now been updated to this version. We advise you to combine the update of JOIN 2023.5 and higher with Windows Server 2022. Our technical consultants can assist you with this.>
We highly recommend always setting up a new server when you want to upgrade to Windows Server 2022. It is strongly discouraged to upgrade an existing server to a higher server version. We also advise that during the installation of a new server, the installation of JOIN Case & Document should be carried out by a technical consultant from Decos.
¶ Whitepaper
The JOIN Whitepaper can be found here:
Whitepaper JOIN
¶ Case types integration
The documentation for the integration layer between JOIN Case & Document and JOIN Case Types has been updated to version 2023.11. The most current version can be found here: Case types integration
¶ JOIN Case & Document
we advise you to always install the most recent hotfix. Therefore, check this page regularly to see if there are any relevant hotfixes for you.
¶ Downloadlink 2025.5
JOIN Case & Document 2025.5 EXE
JOIN Case & Document 2025.5 MSI
Server version: 2025.5.632.35528
JOIN Client 32 bit 2025.5 EXE
JOIN Client 32 bit 2025.5 MSI
JOIN Client 64 bit 2025.5 EXE
JOIN Client 64 bit 2025.5 MSI
Client version: 2025.5.632.33888
Note: with local installations, you may encounter a login issue. This problem only occurs when you have installed a JOIN Client on the JOIN Server (which we do not recommend). If you encounter this problem, you can check this page for troubleshooting:
Note: Use of the JOIN client in Microsoft Intune
From version 2023.11, it is possible to deploy the JOIN client via Microsoft Intune across your organization. To do this, register the JOIN Client MSI as a Windows app (Win32) in Intune. Choose the MSI that corresponds to the version of Office you are using, 32-bit or 64-bit Office. Both MSI setups must be registered as a Windows app (Win32) in Intune.
If you need support with the rollout of the client, you can (for a fee) make use of the deployment of a technical consultant.
¶ Security
Prior to each release, security tests are conducted to assess whether any new vulnerabilities can be identified based on the latest knowledge. Depending on the severity of the vulnerabilities, we resolve them before the release, and they are included in this release. In release 2025.5, we found 3 vulnerabilities that have been resolved in JOIN Case & Document.
¶ Hotfix 2025.5
A new hotfix is released weekly.
Below you will find the most recent hotfix.
hotfix 1103 was released on June 18, 2025
hotfix 1103 for the actions below
version number: 2025.2.632.38704
- 333243: [Freshdesk - 106565] : performance improvements when using computer actions in the workflow
- 334209: [Freshdesk - 101760] : extra logging added to investigate the issue with the processor field
- 334734: [Freshdesk - 107328] : [ZGWAPI][ZRC] issue with retrieving case information objects via ZRC
- 334736: [Freshdesk - 107331] : [ZGWAPI][DRC] problem with retrieving files via the DRC API
- 334971: [Freshdesk - 107388] : [ZGWAPI][ZRC] problem with passing a role to a case in ZRC API
- 336003: [Freshdesk - 107688] : [RESTAPI] unique field validation is missing in the RESTAPI of JOIN JZD
- 336009: [Freshdesk - 107070]: Deleted items cleanup service is not working correctly
hotfix 1102 was released on June 11, 2025
hotfix 1102 for the actions below
version number: 2025.5.632.37916
- 331979: [AKS] make it possible to optionally generate overviews of the backup database
- 334228: [Freshdesk - 105401]: issues with the DecosDirectDropFile function- 334251: [Freshdesk - 107174]: a copy of an email is sent to the configured default sender instead of the logged-in user
- 334789: [Freshdesk - 97662]: the incorrect file version is converted to PDF when the option ‘open office files directly’ is used
- 335831: When creating an overview in JOIN Admin, a 403 error page is displayed
- 334999: [Freshdesk - 107356]: [Admin] Error 404 is displayed when a user tries to log in to admin via AD login (default.aspx page shows an error message)
For action 334228, a new client is needed:
32-bits Office:
JOIN Client 32 bit 2025.5 EXE
JOIN Client 32 bit 2025.5 MSI
64-bits Office:
JOIN Client 64 bit 2025.5 EXE
JOIN Client 64 bit 2025.5 MSI
Client version: 2025.5.632.37595
hotfix 1098 was released on June 3, 2025
hotfix 1098 for the action below
version number: 2025.5.632.36329
-333203: [Freshdesk - 106336]: when using the Add-in for Outlook Save in JOIN, the error message pop-up is not displayed correctly
- 334205: JZD] performance issue due to incorrect indexes
- 334314: [Freshdesk - 106818]: [JZD] issue with iTextSharp (only on-premise)
- 334318: [Freshdesk - 106565]: performance issues when using autocomplete on the COMPANY field from the list
- 333861: [ZGW][ZRC] 500 server error message when using case type and BSN filter
¶ Highlights JOIN Case & Document 2025.5
In version 2025.5, various actions have been included. Below is a selection of the highlights:
¶ ZGW API’s: version 1.5
The developments surrounding Common Ground are currently gaining momentum. More and more initiatives are emerging in the market to utilize the API layers of the Common Ground program for various purposes, and an increasing number of suppliers are working on the transition from the StUF platform to the ZGW API structure.
In version 2025.5 of JOIN Case & Document, of which the APIs for case-oriented work are a part, we have implemented a major upgrade in all our relevant APIs. All these APIs now use the most recent version per API. For this reason, the version numbers may also differ:
Business API (ZRC): this has been updated from version 1.0.1 to version 1.5.1 link
Documents API (DRC): this has been updated from version 1.0.1 to version 1.5.1 link
Decisions API (BRC): this has been updated from version 1.0.0 to version 1.0.2 link
Case Types API (ZTC; also known as Catalogs API): this has been updated from version 1.0.0 to version 1.3.1 link
Notifications API (NC; reference implementation): we use the so-called reference implementation here, which has not been updated. link
Authorizations (AC; reference implementation): we use the so-called reference implementation here, which has not been updated. link
and one of the bigger changes we introduced with this version is the so-called expand mechanism that should ensure better performance of the APIs. The expected load of the APIs is so high and the nature of common ground to store and unlock data at the source ensures that good performance is necessary.
more information about the expand mechanism can be found here: link
In order to use the ZGW APIs, you must have a valid license. In addition, it is of course important that the other supplier is able to communicate using the APIs. Our integration specialists can of course help you with this.
¶ JONI: the AI assistant of JOIN Case & Document
¶ Welcome Joni
We would like to introduce you to a new face within Decos: Joni!
Joni is the handy assistant that can help your users with the use of JOIN Case & Document. Not only with questions about the use of JOIN combined with the configuration of your JOIN installation, but also with searching for all information stored in JOIN. Of course, we do this in a secure manner:
- only logged-in users of JOIN Case & Document may use the chat function
- data is not shared with other customers and remains within the customer environment
- the chatbot AI function complies with the GDPR guidelines
- we use Azure Open AI in combination with the GPT model
¶ How does Joni work?
With Joni it is now possible to ask questions, such as “how do I register an event permit?” or “where can I find the contracts in JOIN?”. Very soon (early June) we expect that Joni will also be able to help with searching for information in JOIN. For example, think of a question “where can I find the contract that we concluded with supplier A or B in 2018?”. Joni will then be connected to the JOIN search engine and can also retrieve information from JOIN and share it via the chat.
Joni is available via the JOIN screen. The button to open Joni’s chat window is located at the top left of the application.
And of course we are continuing to work on other features that we want to introduce in the coming period. So keep a close eye on our information channels!
¶ We also want to use Joni? How does that work?
Great that you are interested! From version 2025.5, the first features of Joni will be available in JOIN Case & Document. You can try out Joni in your own JOIN environment. We will activate Joni for everyone as soon as 2025.5 has been installed on the acceptance environment. We will inform you as soon as this has happened.
¶ We are not in the cloud, can we still use Joni?
Joni is initially only available to customers in the JOIN Cloud (Azure Kubernetes). If your organization does not use the JOIN Private Cloud, please contact your Decos or Doclogic Account Manager so that we can discuss the possibilities together.
¶ What is Joni’s roadmap?
We have just developed the first functions of Joni, so you can already start a chat with her. But of course it doesn’t stop there. In the coming weeks, Joni will learn a lot and she will become smarter and smarter. For example, within a few weeks she will be able to extract information from the data of JOIN for you and we are now also working on functionality with which Joni will take over registration work from you. We will also inform you about this.
¶ How much does it cost?
We activate Joni free of charge in your acceptance and production environment. From that moment on, all users can get started with Joni. We use the first period to further improve Joni and expand the functionality. We will contact you soon to see if you like Joni and want to continue using the functionality. From that moment on, we will charge costs to be able to use Joni in JOIN.
¶ Actions JOIN Case & Document 2025.5
The full list of actions included in the release can be found below. When an action is described in more detail, click on the link to go to the feature’s detail page.
| ID | Freshdesk Ticket | Description | Title |
|---|---|---|---|
| 246498 | 88715 | [Freshdesk - 88715] : [JOIN Now Office add-in] add-ins not shown in group mailboxes | [Freshdesk - 88715] : Not possible to save a shared e-mail using the Office 365 Outlook add-in |
| 248211 | 89583 | [Freshdesk - 89583] : [Elastic] despite there being only 1 page with results, pagination buttons are still displayed | [Freshdesk - 89583] : [Elastic] when result is displayed on 1 page, pagination buttons should not be active |
| 285764 | 94109 | [Freshdesk - 94109] : Improvements in the interface for renewing a case | [Freshdesk - 94109] : improvements in the feature to extend a case |
| 291070 | 100590 | [Freshdesk - 100590] : Office files with % percent sign do not open correctly in combination with the setting “directly open office files” | [Freshdesk - 100590] : “Directly open Office files” doesn’t work for files with a % sign in their name |
| 293556 | 101610 | [Freshdesk - 101610] : an email created via an MSG template (DDMerge function) is not always saved correctly in JOIN | [Freshdesk - 101610] : Sent mail is sometimes not saved in JOIN after using an MSG template |
| 294872 | 102411 | [Freshdesk - 102411] : allow to fill in layered tables via the RestAPI | [Freshdesk - 102411] : allow to fill in multilayered tables in JOIN ZD through the RestAPI |
| 295049 | 101649 | [Freshdesk - 101649] : it is not possible to filter on document type specific data in case documents | [Freshdesk - 101649] : Filter issue in case documents with fields that are document type specific |
| 295190 | 97662 | [Freshdesk - 97662] : incorrect file version is converted to PDF | [Freshdesk - 97662] : incorrect file version is converted to PDF |
| 295215 | 102359 | [Freshdesk - 102359] : Disable autofill for emailaddress in admin | [Freshdesk - 102359] : Disable autofill options for emailaddress in admin |
| 295290 | 102544 | [Freshdesk - 102544] : When Elastic is enabled for overviews, the correct overview is not created in hierarchical books | [Freshdesk - 102544] : Filtered personal overview of a hierarchical document book does not have correct result |
| 295460 | 101327 | [Freshdesk - 101327] : Issues with pagination on linked items | [Freshdesk - 101327] : Issues with pagination on linked items |
| 295745 | 102199 | [Freshdesk - 102199] : viewer in 4 frame mode does not always display excel files correctly | [Freshdesk - 102199] : JOIN viewer cannot show full worksheet of Excel document |
| 295929 | 101763 | [Freshdesk - 101763] : in specific cases JOIN Now screen turns white | [Freshdesk - 101763] : JOIN Now screens unexpectedly shows a white screen in specific scenario’s |
| 297071 | 103227 | [Freshdesk - 103227] : Unable to login with local password authentication in clientless template editor | [Freshdesk - 103227] : Clientless Template Editor issues: not able to login with local user |
| 297638 | [JZD] change support link in JOIN to decos.freshdesk.com | [JZD] Change support URL from “joinsupport.decos.com” to “decos.freshdesk.com” in code | |
| 298012 | [JZD] Sort order in download window of JOIN is incorrect | [JZD] improve sort order incorrect in Download Window of JOIN Portal | |
| 299266 | 103942 | [Freshdesk - 103942] : problems opening files | [Freshdesk - 103942] : problem with opening files |
| 299563 | 104042 | [Freshdesk - 104042] : [Decisionmaking] incorrect pagination displayed in proposal PDF when it contains more than 2 pages | [Freshdesk - 104042] : [Decisionmaking] incorrect pagination in proposal PDF displayed |
| 299959 | [Teams] Only sync case types and document types for users authorized for the MS Teams connection | [Teams] Only sync allowed users to Teams Cloud | |
| 300675 | 104293 | [Freshdesk - 104293] : Download fails when downloading a file that was added and renamed via the “link existing file” | [Freshdesk - 104293] : Creating download zip fails when a renamed symbolic blob is selected |
| 300833 | 104423 | [Freshdesk - 104423] : Document type field is not mandatory when creating a case document | [Freshdesk - 104423] : Document type field is not mandatory in item creation window |
| 301209 | 104165 | [Freshdesk - 104165] : PDF Creator gives error message causing parts to disappear from the original PDF | [Freshdesk - 104165] : PDF created from PDF conversion service is corrupted |
| 301303 | 104589 | [Freshdesk - 104589] : add support for sending mail via MS Graph and Exchange SMTP | [Freshdesk - 104589] : Support sending Exchange Online mail using Microsoft Graph as well as Exchange SMTP |
| 301485 | 104369 | [Freshdesk - 104369] : JOIN 365 add-in for Outlook stopped working after Microsoft updated authentication policy | [Freshdesk - 104369] : JOIN 365 add-in for Outlook (clientless add-in) stopped working due to updated authentication policy at microsoft |
| 301653 | 104480 | [Freshdesk - 104480] : Line spacing is too big in emails sent from JOIN | [Freshdesk - 104480] : Too much line spacing in the email sent from JOIN |
| 302095 | 104800 | [Freshdesk - 104800] : Font size for numbering, bullets and checkboxes differs in decision making | [Freshdesk - 104800] : Font size for numbering, bullet points and check boxes differs |
| 302446 | 104633 | [Freshdesk - 104633] : MORE menu does not respond for users | [Freshdesk - 104633] : More menu in JOIN does not respond for users |
| 302767 | [JZD] Clientless Outlook 365 add-in does not always show files being uploaded | [JZD] Outlook 365 add-in sometimes stops receiving uploaded files in AKS environment | |
| 303342 | [JZD] Allow users to widen the column of displayed workflows in the link workflow window | [JZD] Allow users to change the width of the “workflow name” column in the link workflow window | |
| 303803 | [JZD] issue with the font in excel files in JOIN | [JZD] Excel SVG Generation doesn’t use the custom fonts settings | |
| 304348 | 105662 | [Freshdesk - 105662] : [Decision Making] allow the width in the decision making template to be adjustable | [Freshdesk - 105662] : [Decisionmaking] allow to adjust the width in decisionmaking templates |
| 307079 | 104561 | [Freshdesk - 104561] : [Connect] Improve Connect logging in load balanced on premise environments (Connect High available) | [Freshdesk - 104561] : [Connect] Improve Connect logging for load-balanced on-premise environments |
| 314699 | [Freshdesk - 97662] : “Use direct PDF conversion” setting is not used when converting to PDF in a computer action | [Freshdesk - 97662] : “Use direct PDF conversion” configuration setting is ignored in PDF conversion from workflow | |
| 315098 | [JZD] when sending mail, the settings for sending data and files are not applied correctly | [JZD] Issue with mail data settings when configured with multiple mail addresses | |
| 319446 | [JOIN] Update System.Text.Json to v8.0.5.0 | [JOIN] Update System.Text.Json to v8.0.5.0 | |
| 329959 | [AI] Introducing Joni, the AI Chat agent for JOIN | [AI] Introduction of Joni, the AI Chat agent for JOIN | |
| 330241 | 105876 | [Freshdesk - 105876] : Not all scan pages are shown when opened as PDF | [Freshdesk - 105876] : Scan PDF sometimes does not contain all scan pages |
| 331519 | [JZD][AI] Make it possible to call the AI Chat agent “Joni” from JOIN | [JZD][AI] allow to activate AI Assistant from JOIN Portal (Joni AI Chatbot) | |
| 331747 | [Freshdesk - 97662] : workflow uses old version of document when converting to PDF (via computer action) | [Freshdesk - 97662] : Even when “Use direct PDF conversion” is set, workflow still creates PDF from old version of document | |
| 333152 | [JZD][AI] integrate the Joni AI assistant into the JOIN Cloud installation | [JZD][AI] Docker build and AKS hosting for JOIN AI | |
| 333308 | 106818 | [Freshdesk - 106818] : [JZD] issue with creating a PDF from a scan in the latest hotfix of version 2025.2 / 2024.11 | [Freshdesk - 106818] : [JZD] Scan PDF creation fails in latest hotfix (on-premise) |
¶ JOIN Integrations (Integrations)
¶ Downloadlink 2025.5
JOIN Integrations - StUF BG 2025.5
Azure KS: 2025.5.631.34860
JOIN Integrations - Message Box 2025.5
Azure KS: 2025.5.631.33980
JOIN Integrations - StUF ZKN 2025.5
Azure KS: 2025.5.631.33978
JOIN Integrations - StUF DCR 2025.5
Azure KS: 2025.5.631.34861
JOIN Integrations - JIA 2025.5
Azure KS: 2025.5.631.34004
Other components (such as StUF-LVO) have not been adjusted in this version. Please check previous release notes to see if you still need to update them.
¶ Security
Prior to each release, security tests are performed to check with the latest knowledge whether new vulnerabilities can be found. Depending on the severity of the vulnerabilities, we will resolve them prior to the release and include them in this release. In release 2025.5, we have not found any new vulnerabilities in JOIN Integrations.
¶ Hotfix 2025.5
A hotfix is not yet available.
¶ Actions Integrations 2025.5
Here you will find the full list of actions included in the 2025.5 release.
¶ StUF integrations
| ID | Freshdesk Ticket | Description | Title |
|---|---|---|---|
| 240980 | 86444 | [Freshdesk - 86444] : [StUFBG]MAC : StUF055 - Message body is not according to schema in sector model | [Freshdesk - 86444] : [StUFBG] Maclv01 is not according to StUF standard |
| 243957 | [StUFEF MessageManager] The function to open messages in the message manager is not working correctly | [StUFEF MessageManager] Open/View request message functionality is not working | |
| 251940 | 90881 | [StUFZKN] Implement a so-called retry mechanism for uploading files when the upload is not successful | [StUFZKN] Implement a retry mechanism for uploading file |
| 289873 | 68151 | [Freshdesk - 68151] : [JIA][StUFDCR] successful StUFDCR messages are incorrectly shown as failed in the JIA | [Freshdesk - 68151] : Successful StUFDCR documents being created and saved in JOIN are marked as failed |
| 292632 | 101591 | [Freshdesk - 101591] : [StuFZKN] Missing status of document as sent in StUFZKN message | [Freshdesk - 101591] : [StuFZKN] Status is not mapped with Document |
| 292665 | 101587 | [Freshdesk - 101587] : [JIA] Number and ExtID columns are missing in the JIA when using multiple StUF integrations | [Freshdesk - 101587] : [JIA] Columns missing when you have more than 1 StUF integration in JIA |
| 292669 | 101581 | [Freshdesk - 101581] : [StUFZKN] Implement a retry mechanism for case documents that are added through “VoegZaakdocumentToe” operation | |
| 293138 | 101516 | [Freshdesk - 101516] : A case can be added via StUFZKN when the case type has expired | [Freshdesk - 101516] : Case is created by StuFZKN application while the case type has already been expired |
| 296467 | 101919 | [Freshdesk - 101919] : [StUFZKN] problems with checking in events (case documents) | [Freshdesk - 101919] : [StUFZKN] issues with Check-in events |
| 297273 | 103300 | [Freshdesk - 103300] : the description in the StuFDCR message is longer than the maximum allowed length of 80, which means that the messages are not processed properly | [Freshdesk - 103300] : Subject in outgoing StUFDCR message should be truncated if its passed the max of 80 characters |
| 300173 | [StUFEF] Login problem for StUF-EF | [StUFEF] stufef beta is not working with new release (IDP error) |
¶ ZGW API
| ID | Freshdesk ticket | Description | Description |
|---|---|---|---|
| 297686 | [ZGWAPI][ZRC] Update CaseInformationObjectsService entity to Ver. 1.5.1 | [ZGWAPI][ZRC] Update CaseInformationObjectsService entity to Ver. 1.5.1 | |
| 331219 | [ZGWAPI] Update API version for ZRC and DRC to 1.5.1 | [ZGWAPI]Update API version for ZRC and DRC to 1.5.1 | |
| 297663 | [ZGWAPI][ZRC] Update Roles entity to Ver. 1.5.1 | [ZGWAPI][ZRC] Update Roles entity to Ver. 1.5.1 | |
| 297694 | [ZGWAPI][ZRC] Update Query Parameters for the Cases entity to version 1.5.1 | [ZGWAPI][ZRC] Update Query Parameters for Zaken (Business) entity to Ver. 1.5.1 | |
| 297658 | [ZGWAPI][ZRC] Update Statuses Entity to Ver. 1.5.1 | [ZGWAPI][ZRC] Update Statuses Entity to Ver. 1.5.1 | |
| 297688 | [ZGWAPI][ZRC] Update ZaakObjectenService entity to Ver. 1.5.1 | [ZGWAPI][ZRC] Update ZaakObjectenService entity to Ver. 1.5.1 | |
| 297686 | [ZGWAPI][ZRC] Update ZaakInformationObjectenService entity to Ver. 1.5.1 | [ZGWAPI][ZRC] Update ZaakInformationObjectenService entity to Ver. 1.5.1 | |
| 299799 | [ZGWAPI][ZRC] Update Request-Response Body Properties for Business Entity to Ver. 1.5.1 | [ZGWAPI][ZRC] Update Request-Response Body Properties for Business Entity to Ver. 1.5.1 | |
| 297694 | [ZGWAPI][ZRC] Update Query Parameters for Business Entity to Ver. 1.5.1 | [ZGWAPI][ZRC] Update Query Parameters for Business Entity to Ver. 1.5.1 | |
| 297588 | [ZGWAPI][ZRC] Update Header Parameters in ZRC API 1.5.1 | [ZGWAPI][ZRC] Update Header Parameters in ZRC API 1.5.1 | |
| 302670 | 103063 | [Freshdesk - 103063] : [ZGWAPI][DRC] repetitive issue with retrieving documents with the DRC API | Bug 302670: [Freshdesk - 103063] : [ZGWAPI][DRC] Retrieving documents through ZGWAPI is working incorrectly |
| 296436 | 103063 | [Freshdesk - 103063] : [ZGWAPI][DRC] retrieving documents with the DRC API is causing issues | [Freshdesk - 103063] : [ZGWAPI][DRC] Retrieving documents through ZGW API is not working properly |
| 302377 | [ZGWAPI][DRC] Update fetch a single information object response to version 1.5.1 | [ZGWAPI][DRC] Update fetch a single information object response to version 1.5.1 | |
| 303060 | [ZGWAPI][DRC] Implement new properties and query string parameters in DRC API 1.5.1. | [ZGWAPI][DRC] Implement newly added properties in query string parameters and request body schema in DRC API 1.5.1 | |
| 302450 | [ZGWAPI][ZRC] Update header parameters in ZRC API 1.5.1 | [ZGWAPI][DRC] Update Header Parameters in DRC API 1.5.1 | |
| 297709 | [ZGWAPI][ZRC] Introduce the “Expand mechanism” in the Business Entity for ZRC version 1.5.1 | [ZGWAPI][ZRC] Introduce Expand Property in Business Entity for ZRC Ver. 1.5.1 | |
| 297695 | [ZGWAPI][ZRC] Introduce Expand Property in RolenService for ZRC Ver. 1.5.1 | [ZGWAPI][ZRC] Introduce Expand Property in RolenService for ZRC Ver. 1.5.1 | |
| 297699 | [ZGWAPI][ZRC] Introduce Expand Property in ZaakObjectenService for ZRC Ver. 1.5.1 | [ZGWAPI][ZRC] Introduce Expand Property in ZaakObjectenService for ZRC Ver. 1.5.1 |
¶ JOIN Customer contact
¶ Download link 2025.5
JOIN Customer Contact 2025.5 websetup
JOIN Customer Contact 2025.5 install
¶ Security
Prior to each release, security tests are performed to check with the latest knowledge whether new vulnerabilities can be found. Depending on the severity of the vulnerabilities, we will resolve them prior to the release and include them in this release. In release 2025.5, we did not have to resolve any vulnerabilities in JOIN Customer Contact.
¶ Hotfix 2025.5
There is no hotfix available yet for version 2025.5.
¶ Actions JOIN Customer Contact 2025.5
The 2025.5 release contains many improvements for the new frontend and new developments such as:
Contact Session Note adjustments during incoming and active phone call
It is no longer possible to end a contact session during an incoming or active phone call.
Read more
More channels in Contact History search screen
In the contact history search screen, all available options for which a contact history can be created are now shown for the channel.
Read more
Unlinking persons or organizations from Contact History
From the contact history, (incorrectly) linked persons or organizations can now be manually unlinked.
Read more
Keywords for Theme page
It is now possible to add a maximum of 100 keywords to a theme page.
Read more
Bulk handling on behalf of practitioner
Outstanding callback notes can now be handled in bulk on behalf of the assigned practitioner.
Read more
Department in employee selection
The department of employees is also shown in the dropdown menu that is shown in the employee selection.
Read more
The full list of actions that are included in the release can be found below. When an action is described in more detail, click on the link to go to the detail page of the function.
| ID | Ticket | Description | Description | Part |
|---|---|---|---|---|
| 131417 | 30991 | Customer name entry is not consistent between contact history and completed callback note | Inconsistent way of showing salutation in contact history | Contact History |
| 135692 | 32440 | Don’t show mergefield content when no data is available | Don’t display mergefields without value | Templates |
| 167989 | 42847 | Channel type missing in contact history search | Not all channeltypes are showing in the contacthistory search | Contact History |
| 163264 | 46600 | Selection contact history period for yesterday also contains data from today | Search contact history period for yesterday also contains data from today | Contact history |
| 172570 | 56553 | Incorrect translation header in Report employee JKC | Translation error in Reports | Reports |
| 186200 | 56671 | Don’t allow users to update email address of Person from Eduarte integration | Don’t allow users to update email address of Person from Eduarte integration | Eduarte |
| 199434 | 67339 | Age counts for deceased people | Deceased people keep on aging | People |
| 205355 | 67552 | Do not show that the travel document has expired when the end date is not known. | Don’t display document is expired if there is no enddate known | Pepole |
| 226671 | 78811 | Deleted users should not have any influence on the login for users with the same email. | IsDeleted users should not impact the login for users with the same e-mail | Login |
| 226629 | 79935 | Make it possible to unlink relationships/people in the editing screen of the contact history | Make it possible to unlink relations/persons in edit screen of contact history | Contact history |
| 238184 | 84324 | Increase the number of keywords on a theme page and show a warning | Increase the amount of keywords for a themepage and show a warning message | Topic pages |
| 242796 | 87105 | Show the mailing address in the search result when the residential address is missing. | Show the correspondence address in the search result when the residence address is not known | Pepole |
| 249786 | 90258 | Bulk handling callback note not in the name of the handler | Bulkhandling callbacknote not on name of assigned handler | Callback notes |
| 291342 | 93032 | Improvement of performance note on the dashboard | Improved performance for fetching notes on the dashboard | Notes |
| 257408 | 93306 | Show department during employee selection | Show department for employee dropdown | Employees |
| 285920 | 96327 | Problems with closing screens when zoomed in | Closing panel when zoomed in | UI |
| 285949 | 98440 | Mismatch between report database and CDR database | Mismatch between report database and CDR database | Reports |
| 288460 | 99187 | The email address of the linked person is incorrectly filled in when forwarding an email. | Email is incorrectly prefilled when forwarding an email | |
| 290486 | 100453 | Problems with minimizing a screen | Problems with minimizing screen | UI |
| 299898 | 104163 | Edited by incorrectly adjusted for all dashboards after editing a dashboard | Management Console Changed by and date all the same | Management Console |
| 302563 | 104877 | After opening the contact history, it is not possible to return to recent activity. | Recent activity is not part of the breadcrumb | Module Recent activity |
| 331190 | 105163 | Error message when searching in the contact history for more than 1000 users (Oracle) | Error message when search contacthistory with more than 1000 users (Oracle) | Contact history |
| 300377 | Make it possible to make the email field in a callback note mandatory. | Make it possible to configure mandatory e-mail field for CBN | Callback note | |
| 301440 | Searching by department not possible with popular number | Searching on department for popular number does not work via the phone menu | Telephony | |
| 302844 | Do not allow a contact session to be terminated during a phone call. | Don’t allow ignore, park or end during phone call | Telephony | |
| 302856 | Remove the first empty line when using an email template | Remove empty line when selecting an e-mail template | Templates | |
| 302878 | Allow images to be added in notes | Allow images to be added via TinyMC in Notes | Notes | |
| 303413 | Allow adding images in call-back notes / tasks | Enable add image into task functionality | Callback notes / Tasks | |
| 303450 | The field for the contact person in a callback note is not displayed as mandatory. | Contact person field for terugbelnotitie is not displaying as mandatory | Callback notes | |
| 320158 | Problems with dragging the screen of an incoming call | Dragging the incoming call screen via the image causes issues | Telephony | |
| 320245 | Vinkveld is displayed in the recording bar when no person or organization is known. | Checkbox displayed for a phone call when there is no person or organization | Telephony | |
| 329973 | Age is not displayed for persons stored locally (CDR). | Age (in years) is not showing for CDR person | Pepole*(CDR)* | |
| 332452 | Console error and crashing JOIN Customer contact environment with linked FAQ items that can no longer be found | Continuous console error for undefine question if load entity which has question in relation and further functionality block | FAQ |