¶ Releasenotes JOIN version 2022.12
On this page you will find all actions that are included in version 2022.12. This is a so-called major release in which new functionalities are also included for the various modules (Case & Document, Integrations and JOIN Customer Contact) and released on 21 December 2022.
Support for version 2022.6 will expire after February 28, 2023. If you have not updated your JOIN Environment since the previous major release (2022.6), you will find the intermediate minor updates in the wiki. We recommend that you also read these. Actions included in versions 2022.8 (JKC only) and 2022.10 (JKC and JZD) are automatically part of version 2022.12
Do you want us to update your environment to this version? Please contact our support team JOIN Support
Did you know that we can install this update for you on your On-premise environment and/or support you in testing? See on this page for all the possibilities.
If you want to know until when we support older versions of JOIN Zaak & Document, please look here: click here for the SLA
¶ Planning update cloud environments
If you use the Decos Private Cloud (Azure VM or Azure Kubernetes), you will find here the planning for the installation in your underwriting and production environment.
¶ Standard documentation
¶ Installation Guide
The installation manual can be found 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: Join Integrations Upgrade Manual (Link and JIA)
¶ System Requirements
.NET: JOIN Case & Document (& integrations!) requires version 4.8 of .NET
Search: JOIN Case & Document requires the installation of Elastic Search. We support Elastic supported versions up to version 7.17.1
Databases: We support SQL Server and Oracle databases (Azure Cloud is SQL Server only).
¶ Whitepaper
The JOIN Whitepaper can be found here:
[Whitepaper JOIN] (https://wiki.decos.com/nl/whitepaper)
¶ Case types integration
The integration layer between JOIN Case & Document and JOIN Case Types has been updated. The most up-to-date version can be found here:
[Integration layer JOIN Case Types] (https://joinsupport.decos.com/a/solutions/articles/17000099724?lang=nl)
¶ JOIN Case & Document
¶ Downloadlink 2022.12
[JOIN Case & Document 2022.12 EXE] (https://support.decos.nl/qa/JOIN-patch2212631-20221220-exe.zip)
[JOIN Case & Document 2022.12 MSI] (https://support.decos.nl/qa/JOIN-patch2212631-20221220-msi.zip)
Azure KS: 2022.12.631.18872
[JOIN Client 32 bit 2022.12 EXE] (https://support.decos.nl/qa/JOINNowClient2212631-20221215-exe.zip)
[JOIN Client 32 bit 2022.12 MSI] (https://support.decos.nl/qa/JOINNowClient2212631-20221215-msi.zip)
[JOIN Client 64 bit 2022.12 EXE] (https://support.decos.nl/qa/JOINNowClientX64-2212631-20221215-exe.zip)
[JOIN Client 64 bit 2022.12 MSI] (https://support.decos.nl/qa/JOINNowClientX64-2212631-20221215-msi.zip)
Zip code update: As of version 2021.3, no zip code update will be released. From now on, the postal codes will be updated every day on the basis of the LAND REGISTRY BAG-Extract (part of the BAG API / BAG 2.0).
¶ Hotfix 2022.12
We strongly recommend that you install the latest hotfix or have it installed. If you are using Azure KS, Decos will install the hotfix. In this case, a hotfix automatically contains the actions that were included in the previous hotfixes. For non-Azure KS environments, this depends on the components that are included in the hotfix.
No hotfix is yet available for this release
¶ Highlights JOIN Case & Document
¶ JOIN Teams integration
New from version 2022.12 is an integration with MS Teams. Where Teams is increasingly used in organizations to collaborate, meet and do projects, JOIN Zaak & Document remains the collective “conscience” of your organization. After all, a new risk has also been introduced with Teams, namely the risk of incorrect information management and the loss of important documents.
You can solve this by connecting the best of MS Teams and JOIN Zaak & Document. A link with MS Teams ensures that you can archive your channels and documents in teams in JOIN Case & Document.
All information about the JOIN Teams integration can be found on this page
¶ Automatic reading of mailboxes
An existing functionality in a new look. It has been possible for some time to have your mailboxes automatically read into JOIN Zaak & Document. This saves a lot of time, especially with large volumes.
This feature has now been rewritten, following a significant change at Microsoft (phasing out BasicAuth). The new feature uses Exchange Online mailboxes and is based on the Oauth authentication principle.
More information about this feature can be found here.
¶ Stability Elastic Search
In the past period we have worked hard to improve the stability of Elastic Search (the search function that is used for global search (top right of the screen) and loading lists, such as the business warehouse). It often happened that registrations were correctly updated in the database but not correctly in the index. This led to an annoying discrepancy and the lack of information for end users.
The following adjustments have been made to the application:
- The Elastic search service returns an error message when the index could not be updated
- If the search service has not been able to update the index, JOIN Case & Document will call the index again with an interval so that it can be successfully updated.
The problem occurred (until version 2022.12) with both local and cloud installations. If you use a local installation of JOIN Case & Document, we would like to ask you to check the following setting:
You should disable this setting.
¶ Datamask link (JOIN Anonymize)
You can use the datamask link via the JOIN Anonymization Service. Then from version 2022.12 you can choose not to save the audit PDF, which is automatically created by Datamask, in JOIN Case & Document. The setting can be found in JOIN Admin:
¶ Maintain decoupled workflow
When you unlink a workflow and link a new workflow, the open action of the original workflow is deleted. This also happens automatically when, for example, a case is rebooked to another case type (e.g. from customer contact to a specific process). For example, this data (from which case type it originally came) can be useful information in a report (how many cases come in via the customer contact form, for example).
In order not to delete the worklfow action, an option has been added in JOIN with which this behavior can be changed:
¶ Link with i-navigator
The link between JOIN Case Types/JOIN Case & Document will be available via the https connection from version 2022.12. Please contact the Decos support team for the necessary adjustments.
¶ Actions JOIN Case & Document
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 detail page of the function.
| ID | Ticket | Description | Description |
|---|---|---|---|
| 187381 | [JOIN Teams] develop an API that allows files from Teams to be read into JOIN Case & Document (part 1) | [JOIN Teams] Develop Cloud API for BG process to get data from blob storage and azure DB (part 1) | |
| 187382 | [JOIN Teams] develop an API that allows files from Teams to be read into JOIN Case & Document (part 2) | [JOIN Teams] Develop BG service to call cloud API and store data in Join DB. | |
| 183594 | 59675 | some older cases can no longer be handled in JZD | [Freshdesk - 59675] : Some old cases can no longer be handled in JZD |
| 179389 | 57316 | [Freshdesk - 57316] : When a docx file is converted to PDF, an (unnecessary) extra version of the docx file is created | [Freshdesk - 57316] : When converting docx file to pdf via the on-demand pdf button, JOIN creates an extra (unnecessary) version file of the docx source file. |
| 195142 | 65953 | [Decision-making] [PDF] the proposal PDF becomes corrupted in the agenda step (side-effect of the aspose update 2022.10) | [JZD] [DMD] Decision making PDF gets corrupted once it reaches the approval phase for the board |
| 195805 | 63931 | [Freshdesk - 63931] : [Elastic] implements a retry mechanism when the Elastic index cannot be reached from JOIN | [Freshdesk - 63931] : Items are frequently not indexed, apparently due to intermittent failures of the Elastic Search service |
| 195824 | 65725 | 2022.10: Data statement cannot be merged with template | DOT merge does not work properly for related documents overview |
| 196009 | [JZD] [Elastic] cause the search engine service to return an error message if you cannot update the search index | [JZD] SearchService should return proper error code in case of failure | |
| 196168 | 65692 | [EMAIL] supports reading Exchange Online mailboxes via IMAP based on OAUTH (due to end of support Basic Auth | [EMAIL] [Freshdesk - 65692] : Implement OAuth application access to read mailbox contents from Exchange Online via IMAP, as Basic Authentication is no longer supported |
| 196212 | 64399 | improvements in the clean up service for deleted registrations | Improvements in clean up service for deleted items |
| 190144 | [PDF] when uploading a password-protected PDF, the correct notification must be toned | [PDF] Uploading encrypted PDF files should display correct text in the scantree view window | |
| 191105 | [Anonymize] [Datamask] make saving the “anonymization report” from Datamask optional | [Anonimization] [datamask] introduce option to send anonimization report with transaction | |
| 191280 | [JZD] make sure that the background service can generate thumbnails of files | [JZD] Generate file previews in Background Service | |
| 191392 | [JZD] [CONNECT] various performance improvements | [JZD] [CONNECT] - Long running queries - Part 1 | |
| 189429 | [Workflow] make sure (optionally) that active actions are not deleted when unlinking a workflow | [Workflow] Do not delete the active item when unlinking workflow | |
| 196765 | [JZD] Clear SUBJECT2 for deleted BLOB records in 2022.12 update only if DeleteFiles setting is enabled | ||
| 196897 | 66111 | [Freshdesk - 66111] : PDF Signing has stopped working since the last client update (after security updates) | [Freshdesk - 66111] : PDF signing stopped working |
| 197059 | 66208 | [TOOL] {User import] make sure that when importing users via the user import tool, a personal work stock is always created | [TOOL] [USERIMPORT] The user created by the tool , is not having there personal pending item container when logged in JOIN |
| 197085 | [Admin] Boolean settings (checkboxes) are unintentionally set to True in Admin configuration and cannot be unchecked | ||
| 197088 | [Connect] common error message in logging “identifier is empty and can not be generated” | [Connect] Identifier is empty and can not be generated exceptions in Connect | |
| 197217 | [JZD] Join occasionally shows blank pages when SAML is enabled | ||
| 197230 | [StUFZKN] Performance improvements | [StUFZKN] improvements in database query (performance) | |
| 193455 | 65269 | [Freshdesk - 65269] : Office files larger than 30 MB cannot be opened through Office Online | [Freshdesk - 65269] : [OOS][WebDAV] Consider Office file size limits when generating Office Online or WebDAV links in JOIN Portal |
| 193630 | 60208 | [Azure KS] various performance and stability improvements in the XML Crawler (XMLL Import module) | [Azure KS] Improvements in XML Crawler |
| 193683 | 65358 | [Signing service] bug fixes since the last major release of Validsign | [Signing service] A signing service transaction with sender as signer is no longer visible in ValidSign since their summer release |
| 194149 | [JZD] Not all JPEG files can be uploaded correctly in JOIN Case & Document | [JZD] Not all jpeg files can be uploaded in JOIN Case & Document although the jpg and jpeg file extensions are white-listed | |
| 194503 | [Azure KS] timeouts when loading status and result tables in the workflow editor | [Azure KS] Status and result tables load too slowly in workflow editor, causing time-outs | |
| 188667 | [Admin] introduce maximum values for the settings “max preview page height” and “max preview page width” to avoid performance issues | [Admin] Restrict maximum values for “Max. preview page height” and “Max. preview page width” configuration settings | |
| 158393 | 43656 | [Freshdesk - 43656] : Destruction Wizard does not remember column choice | [Freshdesk - 43656] : [Disposal lists] Disposal list wizard, column selection is not remembered |
| 163104 | 42826 | [JZD Admin] after removing parts in bulk is incorrectly shown “2 objects not shown because you do not have enough rights” | [JZD ADMIN] Bulk remove in JOIN Admin will show "X Users not shown because you do not have |
| 185376 | [Anonymize] makes it possible to exclude fields and item types when pseudonymizing the JOIN Database | [AnonymizeDB] Allow to configure exceptions for fields by item type and items by parent key & bugfixes | |
| 180549 | 58980 | [Freshdesk - 58980]: Support integration with the I-Navigator web service via the HTTPS protocol | [Freshdesk - 58980] : support https for i-navigator webservice |
| 188486 | [Admin] [Azure KS] email summary URL is not populated correctly in Azure Kubernetes environments | [ADMIN] [AKS] EmailImageURL is not set correctly for Email overviews |
¶ JOIN Integrations
¶ Downloadlink 2022.12
[JOIN Integrations - StUF BG] (https://support.decos.nl/setups/Integrations/DC-StUFBG_Basisgegevenskoppeling_op_DecosConnect/2022.12/StUFBG-3_2022.12.631_20221221.84456.zip)
Azure KS:: 2022.12.631.18921
[JOIN Integrations - Admin (JIA)] (https://support.decos.nl/setups/Integrations/!JIA_JOIN_Integration_Administration/2022.12/JIA.zip)
Azure KS: 2022.12.631.18920
[JOIN Integrations - StUF ZKN] (https://support.decos.nl/setups/Integrations/StUFZKN_Generieke_zaakkoppeling/2022.12/StUFZKN-4.0_2022.12.631_20221221.84457.zip)
Azure KS:: 2022.12.631.18922
Other components (such as StUF-DCR) have not been modified in this version. Please check previous release notes to see if you still need to update them.
¶ Hotfix 2022.12
We strongly recommend that you install the latest hotfix or have it installed. If you are using Azure KS, Decos will install the hotfix. In this case, a hotfix automatically contains the actions that were included in the previous hotfixes. For non-Azure KS environments, this depends on the components that are included in the hotfix.
No hotfix is available yet
¶ Highlights Integrations
The most important developments regarding integrations are:
- improving the stability of the StUF platform (in particular StUF-ZKN) and the further development of the new Case-oriented working APIs
- Various improvements in the JOIN Integration Admin
¶ ZGW APIs
in version 2022.12 the following functionalities have been added
- support version 1.1 of the APIs. This includes support for uploading and downloading large files
- support for linking citizens and businesses to business (via the StUF-BG link)
- support for storing case objects
¶ JOIN Integration Admin
In the JIA, we have made several improvements to improve the management and monitoring of messaging. The following items have been modified/introduced:
- the log files are visible via the JIA when you use the Azure Kubernetes Cloud
- When a message has not been sent and is offered again, we establish a relationship between both messages so that it is immediately clear that a not working message has still been successfully offered to the StUF application
- the StUF-BG clean up tool has been adapted in such a way that it is now better able to process large numbers of messages
- the filtering capabilities in the JIA have been improved: from version 2022.12, both date and time filtering can be done. For example, all messages between 11 and 12 o’clock in the morning.
- If you switch from version 2022.6 to version 2022.12 immediately, you will also experience that a better distinction can be made between messages that have failed due to a so-called business rule (e.g. a document that cannot be added to a closed case or the case that cannot be created because the case type does not exist).
- Finally, we have improved the stability of the JIA in various places in the application.
.
The jia’s updated manual can be found on this page
¶ Actions Integrations
In the 2022.12 release there are improvements such as:
- for Azure KS customers it is now possible to view logs themselves via the JIA
- from now on, better distinguish between types of messages that do not succeed in JIA (configuration, wrong message types or instability)
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 detail page of the function.
| ID | Ticket | Definition | Description |
|---|---|---|---|
| 171449 | [ZGW API] support version 1.1 | [ZGW] [DRC] Update to support v1.1 | |
| 190139 | [ZGW API] support role functionality in ZRC API | [ZGWAPI] [ZRC] Request a specific ROLE in a CASE | |
| 187950 | [ZGW API] support linking non-natural persons via StUF BG | [ZGWAPI] [ZRC] Link address (company) to case using StUF integration | |
| 187943 | [ZGW API] support linking natural persons via StUFBG | [ZGWAPI] [ZRC] Link address (natural person) to case using StUF integration | |
| 188766 | {AKS] introduce heartbeat monitoring for search and background service | [AKS] Heartbeat is not monitoring searchsvc, backgroundsvc | |
| 196515 | [JIA] error loading log files in JIA | [JIA] Application logs are not being loaded | |
| 189150 | [INTG] [JIA] improvements when resending messages | [INTG] [JIA] As a User I want corelate reprocessed message transaction | |
| 189292 | improvements to the DeDuplicateUnknownCitizen Tool | [DeDuplicateUnknownCitizenTool] Tool throws error if no any extended properties are set for unknown citizen entity definition | |
| 189585 | [StufZkn] out of Memory exceptions stufzknsend notification service | [StufZkn] out of Memory exceptions stufzknsend notification service | |
| 194563 | 64920 | [Freshdesk - 64920] : Query enhancements to prevent high response times in Connect | [Freshdesk - 64920] : Query improvements to avoid high response times in connect |
| 194588 | [INTG] Installation error message for local installations | [INTG] package not released error for setup | |
| 137306 | 32311 | [Connect] Status details are not fed back correctly in Case Update Response | [Connect] Default Status details are not returned in Case update response |
| 146571 | [StUFBG] Allow organizations to search ves in MAC search queries | [StUFBG] Include organizations with VES number from MAC search response | |
| 163974 | 46346 | [Freshdesk - 46346] : MAC notification messages do not include a chamber of commerce number | [Freshdesk - 46346] : StUF-BG Notifications on MAC are not correct |
| 164711 | [StUFZKN] [JIA] Successfully processed messages are incorrectly marked as failed in JIA Messagemanager | [StUFZKN] [JIA] Successfully processed messages are marked as failed | |
| 176801 | [KVK Update] update KVK link with the most recent API endpoints | [Chamber of Commerce] Update KVK API endpoints to latest version | |
| 178308 | 58489 | JOIN Connect: Identifier is empty and can not be generated | [Freshdesk - 58489] : JOIN Connect: Identifier is empty and can not be generated |
| 182414 | [Freshdesk 58473]: House letter is missing from EDP (DDS) Search query | [Freshdesk 58473]: house letter is missing in EDP search request | |
| 185745 | [JIA] Make it possible to specify both a date and time range in JIA message manager | [JIA] allow to filter on date and time range |
¶ JOIN Customer contact
¶ Downloadlink 2022.12
JOIN Customer Contact 2022.12 web setup
JOIN Customer Contact 2022.12 install
¶ Hotfix 2022.12
We strongly recommend that you install the latest hotfix or have it installed. If you are using Azure KS, Decos will install the hotfix. In this case, a hotfix automatically contains the actions that were included in the previous hotfixes. For non-Azure KS environments, this depends on the components that are included in the hotfix.
No hotfix is available yet
¶ Actions
In the 2022.12 release there are improvements such as:
-
Configure additional fields in the contact session note
Two additional fields ‘Forwarded to’ and ‘Handled on behalf’ can be configured in Customer Contact Management for the contact session note. These extra fields are also included in the reports of JOIN Customer Contact. [Learn More] (/en/jkc/exta-fields-contact-session-note) -
Whatsapp integration via CM.com
It is again possible to receive and send Whatsapp messages from JOIN Customer Contact. A requirement from Meta (parent company Facebook and Whatsapp) is that the link goes through a Business Solution Provider. JOIN Customer contact only has an integration with CM.com (BSP). [Click here for more information about the Whatsapp link.] (https://wiki.decos.com/nl/jkc/whatsapp)
The Whatsapp integration is a paid module. Are you interested in a link with Whatsapp? Please contact your account manager.
- Improvements in the ticket module
These improvements have already been released to a number of customers in 2022.10, but will now also be available for the major release. We have made several improvements in the ticket module, such as making fields mandatory in a ticket, adjusting the action menu, adding a treatment screen for tickets. [Read more] (https://wiki.decos.com/nl/jkc/ticket/verbeteringen) to see all changes.
Attention: A change has been made to the sorting by employees. Click the hyperlink in the list of actions for more details
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 detail page of the function.
| ID | Ticket | Definition | Description |
|---|---|---|---|
| 192383 | [Additional fields in contact session note and reports] (/en/jkc/exta-fields-contact-session-note) | Extra field in contact session notes + reports | |
| 181370 | 60143 | [Sort by first name at Employees] (/en/jkc/sort-by-firstname) | Sorting on firstname at Employees |
| 190662 | 64027 | [Whatsapp] On weekends, the automatic message of the holiday is shown and not the out of office message | [Whatsapp] In weekend JKC send out the ‘Out of office’ configured message |
| 190878 | 62370 | [Whatsapp] Task error message when opening Social Media post | [Whatsapp] Error message while opening social media message |
| 188102 | 63085 | [Whatsapp] Type/Channel (WhatsApp) is not shown on recent activity | [Whatsapp] Type/channel wasn’t displayed at recent activity |
| 188975 | 63422 | [Whatsapp] After clicking on a relationship in the Contact Session Note, it disappears | [Whatsapp] After clicking on a relation in the Contact Session Note, it disappears |
| 195093 | 60234 | [Whatsapp] Parked Whatsapp conversation could no longer be found | [Whatsapp] Parked Whatsapp conversation was lost |
| 196905 | 65853 | [Whatsapp] Not visible that linked people are loading | [Whatsapp] Not visible that linked persons are loading (spinner is missing) |
| 193692 | 65389 | [Whatsapp] Start message is sent too quickly | [Whatsapp] Start message is send too soon |
| 191370 | 63921 | [Whatsapp] Start message is not always sent | [Whatsapp] Start message is not (always) sent |
| 190661 | 64028 | [Whatsapp] Holidays only per day and not to be added as a period | [Whatsapp] Holidays are only configurable per day and not as a period |
| 196217 | 65398 | [Whatsapp] Show latest post in social media list | [Whatsapp] Show latest message in social media list |
| 184650 | [Ticket] Show work stock of logged-in user and add an extra column | [Ticket] Show only workload from logged in user in tickets and add 1 extra column | |
| 192393 | 64803 | [Ticket] Name remains with Reassign Ticket (Customer Question) | [Ticket] After clicking on search results the input remains in the handler field |
| 192408 | 64814 | [Ticket] Customer demand (ticket) is not shown in Recent Activity at Person | [Ticket] Ticket wasn’t displayed at recent activity at Person |
| 192409 | 64813 | [Ticket] Reassignment is not shown in the Route Task and Ticket Change History | [Ticket] Reassign wasn’t displayed in Task route and history of the ticket |
| 184652 | [Ticket] Reset button to clear fields in a ticket | [Ticket] Reset button to clear the fields in the ticket | |
| 194731 | 65807 | [Ticket] Filter result for tickets does not work from My Work Stock | [Ticket] Filtering results in tickets from ‘My workload’ are not correct |
| 194771 | 65242 | [Ticket] After clicking in the mail, the treatment screen is not always shown | [Ticket] After clicking on deeplink in email the handle screen is not always displayed |
| 194749 | 65809 | [Ticket] Mail is not only sent to new ticket handler, but to everyone who has been a handler | [Ticket] Email wasn’t only send to assigned handler, but also to all previous assigned handlers |
| 194747 | 65808 | [Ticket] Session will run in JKC after open customer request from mail | [Ticket] Session starts in JKC after opening ticket via email |
| 193389 | 65220 | [Ticket] TBN Mailbox customer questions are not shown under My | [Ticket] CBN Mailbox tickets aren’t showed at ‘My’ |
| 192431 | 64825 | [Ticket] Clickable area for magnifying glass too small/limited | [Ticket] Clickable area to small for magnifying glass |
| 194769 | 65828 | [Ticket] Reassign reason in The Tickets/Customer Questions Treatment Screen | [Ticket] Show Reassign reason in handle screen of tickets |
| 192443 | 64827 | [Ticket] Updating the number of work stock of customer questions does not update correctly | [Ticket] Workload count is incorrect |
| 190794 | 63700 | JKC reminders callback request were sent several times | JKC reminders are send multiple times |
| 161106 | 45081 | Number of tasks on the dashboard tile does not display the correct number in the overview | Count in task dashboard tile is not correct with the task overview |
| 162757 | 46162 | When treating TBN, going back on crumb path results in an empty overview in JKC | Empty task overview after handling callback note and click on bread crum |
| 182414 | 58473 | House number is missing when searching in EDP | House number is missing in EDP search request |
| 194312 | 46425 | Working hours for Monday were shown as ‘Mo’ instead of ‘Ma’ | Working hours value present ‘Mo’ instead of 'Ma |
| 194889 | 47699 | Added two new sections for tasks per mailbox in Callback note Excel export | Two new section added in Task per mailbox sheet in Callbacknote excel |
| 195145 | 57027 | Related organizations are not shown to persons from the JKC database | Related organizations are showing against person for CDR |
| 195675 | 65890 | Phone number does not work when it starts with a + | Phone prefix is not working when dial number start with + |
| 188084 | After completing the task (via a dashboard tile), the task list was empty | After handling task from “open the task on my name”, we can’t see task any more. |