¶ Major release 2023.11
On this page, you will find all actions included in version 2023.11. This is a so-called major release that also includes new functionalities for the various modules (Case & Document, Integrations and JOIN Customer Contact) and released on November 30, 2023.
8 weeks after the release of version 2023.11, support for version 2023.5 and the intermediate minor release 2023.7 and 2023.9 will expire. Therefore, make sure to update your locally installed JOIN environment to version 2023.11. See also our SLA.
Would you like 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 with testing? Watch on this page for all possibilities.
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 environments
The schedule for updating your cloud environment can be found at this page.
¶ Standard Documentation
¶ Installation Guide
The installation manual can be found here::
JOIN Zaak & Document: JOIN Case and Document Upgrade Guide
JOIN Customer Contact: JOIN Customer Contact Upgrade Guide (upgrade manual JOIN Customer Contact)
JOIN Integrations: JOIN Integrations Upgrade Guide (links and JIA) (Upgrade manual JOIN Integrations)
¶ System Requirements
JOIN Case & Document (& integrations!) requires version 4.8 of .NET
Search: JOIN Case & Document requires the installation of Elastic Search. We support the versions supported by Elastic up to and including version 7.17.13
Please note: version 8 of Elastic is not yet supported in combination with JOIN Case & Document
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 recommend that you combine the JOIN 2023.5 and later update with Windows Server 2022. Our technical consultants can guide you through this.
¶ Whitepaper
The JOIN Whitepaper can be found here:Whitepaper JOIN
¶ Integration case types
The documentation for the integration layer between JOIN Case & Document and JOIN Case Types has been updated up to version 2023.11. The most up-to-date version can be found here:
JOIN Case Types Integration Layer
¶ JOIN Case & Document
¶ Downloadlink 2023.11
JOIN Case & Document 2023.11 EXE
JOIN Case & Document 2023.11 MSI
JOIN Client 32 bit 2023.11 EXE
JOIN Client 32 bit 2023.11 MSI
JOIN Client 64 bit 2023.11 EXE
JOIN Client 64 bit 2023.11 MSI
Please note that you may run into a login problem with local installations. This problem only occurs if you have a JOIN Client installed on the JOIN Server (which we do not recommend). If you encounter this problem, you can check this page for troubleshooting:
¶ Hotfix 2023.11
There are no hotfixes available yet for version 2023.11
¶ Highlights JOIN Zaak & Document 2023.11
Various actions are included in version 2023.11. Below is a selection of the highlights:
¶ Delete lists in Excel
A long-cherished wish of many administrators is to be able to generate deletion lists in Excel instead of the PDF that was generated. As of 2023.11, this feature has been implemented and the deletion list will be executed in excel from now on. This gives you the ability to organize data more flexibly and allows you to choose how you further distribute the list for review. The rest of the removal process remains unchanged.
¶ AAD Sync (module)
From version 2023.11, if you use SAML or OpenID Connect (OIDC), it is possible to purchase an additional module for synchronizing users from your AD. Where SAML and OIDC are used to securely log in your users based on the authorizations you set up in the AD, you can use the AD Sync module for the following:
- synchronization of users and user data from the AD
- synchronizing the e-mail addresses of your users to be able to use in the mail function of JOIN.
The link below will take you to a page with more information about this module. If you want to use the module, please contact your account manager.
This functionality requires an additional license
¶ Case System Confidentiality
In version 2023.9, we have introduced a new field that allows you to record the confidentiality of every registration in JOIN Case & Document. Confidentiality is mainly used outside the application, such as in the link to the E-depot, publications to the WOO portals, etc.
Confidentiality can be defined in the “CONFIDENTIALITY” field. By always recording it in the same field, you can ensure that information is always shared outside your organization with the right data, thereby reducing the risk of data breaches.
Starting with version 2023.11, we’re also adding confidentiality support to the case system. As soon as you publish a new version of the case type from version 2023.11 from JOIN Case Types, the following will happen:
- the CONFIDENTIALITY field is added to the case type item profile
- the field is described as “confidentiality” and placed above the result field (so always in the same place)
- The field is writable and not mandatory
- The field inherits the default confidentiality of the case type if it is configured that way in the case type. If this is not the case, the confidentiality can be taken over manually. (So make sure that you fill in the confidentiality on the case type!)
- The field is linked to a table with sensitivity values, as defined in the IMZTC and RGBZ information model. These values (see screenshot above) are not changeable.
If you would like to know more about the integration layer between the case type and the case system, please refer to the documentation.
¶ Custom functions (module)
New in version 2023.11 is the ability to add new features to the registration and workload screens of JOIN Case & Document. These new features, which were previously known as “custom buttons”, have been renamed to “custom functions” and can be used for a variety of purposes:
- a custom function allows you to call a particular function outside of JOIN Case & Document
- With a custom function, you can call a function of our data integrator, such as starting a collaboration in Teams, opening a meeting in a meeting application (this can also be “JOIN on the agenda”) or starting a signing or anonymization request.
There are a number of important differences and improvements compared to the original custom buttons:
- you can configure the custom function yourself from JOIN Admin
- You can set per user or user profile whether the function can be used and from which right the function can be used
- The function can be called from both a registration and from the work stock (action screen)
- You have various configuration options (see image below)
Once the feature is configured and activated, you can start using it in JOIN Case & Document. Depending on your configuration, you can start using the button in a registration or task (workload).
This functionality requires an additional license
¶ 2-factor authentication (module)
Adding an extra factor to the authentication process (authentication/login) increases the security of your accounts and makes it more difficult for an attacker to access your data. If you use an AD link (WS-FED, SAML, OIDC), you arrange the extra step in your authentication process via the AD. However, there are also often users who log in via the local login function of JOIN Case & Document.
To this end, we now offer the option of so-called “native 2-factor authentication”. This allows you to set locally created users (who do not use an external authentication feature such as via Azure AD) to have to sign in via an additional authentication step (mail) before they can access JOIN Case & Document. After registration, the user will receive an email with a code, which must be entered in the JOIN login screen. If you are using a local installation of JOIN Case & Document, you can link the administrator to your AD & impersonate all actions of the administrator.
All information related to the 2-factor authentication module can be found here
This functionality requires an additional license
¶ JOIN Mobile - clickable fields
Many of our customers who use the mobile app “JOIN Mobile” have expressed the desire to make certain fields such as phone number, website and email address “clickable”. These customers make extensive use of JOIN Mobile to look up the phone numbers of business relations, for example. By making the fields “clickable”, you as a user can, for example, click on an email address and open the mail app on the phone. Or click on a URL and go directly to the website on your phone.
We have chosen to make this configurable per field. For example, because the EMAIL1 field is not always used to record an email address, we have made the function more flexible. You can now choose per field per item profile to make the field clickable.
You can configure the clickability of fields from JOIN Admin via the option “show as link”:
The function can not only be used for JOIN Mobile, but can also be used by other applications that retrieve data from JOIN via the RestAPI of JOIN Case & Document.
Please note that the function in JOIN Case & Document can only be used when you disable the configuration option “prevent dynamic link”.
The functionality works for both IOS and Android mobile phones:
¶ Integrations: StUFBG Search by RSIN
For StuF-BG version 03.10, we add full support for searching on all organization types (non-natural persons) by also applying search on RSIN.
If you are interested in converting your StUFBG link to version 03.10 (StUF version), please contact one of our integration experts.
¶ Stability improvements
We are continuously working on stabilizing the functions in the application that are widely used. In previous versions, we have made important stability and performance improvements for the case type integration and the Elastic search functions, for example.
The 2023.11 release includes the following improvements:
- a so-called retry mechanism has been built in for the events that are sent from JOIN Connect to connected applications. You can find information about this in the 2023.9 release notes.
- For the link with signatory suppliers (e.g. ValidSign), we have also built in a retry function that ensures that transactions that have not been sent can be sent again.
- at the moment we are still working on a similar mechanism for PDF creation in the application. This feature is expected to be released in version 2024.2 (February 2024).
¶ Actions JOIN Case & Document 2023.11
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 details page.
| ID | Freshdesk Ticket | Description | Title |
|---|---|---|---|
| 229898 | [StUFZKN] [AKS] spike in memory usage when uploading a file whose extension is not allowed in JOIN | [StUFZKN][AKS] Investigate and resolve memory spike when file extension not allowed | |
| 231108 | 82226 | [Freshdesk - 82226] : Errors Installing JIA on a Local Machine | [Freshdesk - 82226] : JIA.ZIP not complete in all versions |
| 230830 | 82423 | [Freshdesk - 82423] : Improve performance when moving registrations | [Freshdesk - 82423] : Improve performance of “Move to” operation |
| 230981 | 77244 | When opening an Office file via the “Open in JOIN” add-in, an empty file is opened in Powerpoint, Excel and Word | [Freshdesk - 77244] : Issues found when using JOIN File control from JOIN Now |
| 225075 | 77425 | [Freshdesk - 77425] : Improvements for (faster) opening JOIN Now | [Freshdesk - 77425] : Update EO components and rewrite preloader to make JOIN Now window open faster |
| 230040 | 81757 | [Freshdesk - 81757] : always show the PDF extension in ZKN:format when converting file to PDF | [Freshdesk - 81757] : The original file format is indicated in a StUF message for a file converted to PDF in JOIN |
| 229094 | 79945 | [Freshdesk - 79945] : when converting an outline to excel, characters D and 9 are removed from the overview when not allowing dynamic links | [Freshdesk - 79945] : When converting an overview to Excel, leading characters “D” and “9” are removed in the values converted to Excel |
| 229661 | 81777 | [Freshdesk - 81777] : AnonymizeDB tool: anonymizing ALL case types books doesn’t work well and gives a lot of timeout errors | [Freshdesk - 81777] : AnonymizeDB does not work properly in a large database |
| 186057 | [Admin] Introduce a function that allows so-called custom functions to be configured in JOIN Case & Document (part 1) | [Admin] Introduce custom function configurator in JOIN Admin [Part-1] | |
| 201574 | [AAD Sync] Develop a separate module to synchronize users and email addresses in bulk from AAD to JZD | [AAD Sync] develop AAD Sync module | |
| 205907 | [Admin] Introduce a function that allows so-called custom functions to be configured in JOIN Case & Document (part 2) | [Admin] Introduce custom function configurator in JOIN Admin (part 2) | |
| 207503 | [Admin] [Deletion lists] replace the PDF form with an Excel sheet when generating the deletion list | [Admin][Disposal lists] replace the PDF generation of disposal list with Excel generation | |
| 209235 | 67082 | [Freshdesk - 67082] : [Admin] Management overviews are not sent monthly but daily | [Freshdesk - 67082] : [Admin] Management report which are scheduled monthly , but the user are getting mail daily |
| 215328 | [ZTCSYNC] Add the “confidentiality” field to the item profile case type when republishing the case type | [ZTCSYNC] add property “CONFIDENTIALITY” to the casetype itemprofile | |
| 215755 | 71411 | [Freshdesk - 71411] : Original files cannot be opened with the “signed PDF replaces original file” setting | [Freshdesk - 71411] : Cannot open original file after signing when the option “Signed PDF replaces original file” is used |
| 226345 | 79978 | [Freshdesk - 79978] : incorrect object in the XML export when creating an export of cases | [Freshdesk - 79978] : Wrong root item type is written in XML export |
| 226405 | 80122 | [Freshdesk - 80122] : synchronization issues with AD users after update to version 2023.7 and 2023.9 | [Freshdesk - 80122] : AD users are not synchronized correctly when they log in immediately after upgrading a a JOIN environment using ADFS to 2023.7 |
| 230663 | [JZD-Admin] AADSYNC Client Id is Flushed in JOIN Admin Configuration | [JZD-Admin] AADSYNC Client Id gets auto-erased after some time from Admin Configuration. | |
| 222586 | [JOIN Mobile] support calling phone and mail app in JOIN Mobile | [JOIN JZD] create phonenumber and mailto link in JOIN Mobile | |
| 223276 | 77184 | [Freshdesk - 77184] : Files originating from ValidSign are sometimes not stored in JOIN | [Freshdesk - 77184] : SIGNED background worker sometimes runs out of memory when processing a signed PDF |
| 224811 | 79055 | [RestAPI] enable retrieval of more than 10000 records through the API when using Elastic Search | [RestAPI] paging with results above 10.000 records not working - results keep the same after 10.000 |
| 216162 | 74840 | [Freshdesk - 74840] : In the screen to link documents to a file, the option to select a file tab is missing | [Freshdesk - 74840] : in link document frame the option to link folder tab is missing |
| 216593 | 74912 | [Freshdesk - 74912] : [Signing] Introduce a mechanism to resubmit unsuccessful signing requests | [Freshdesk - 74912] : [Signing] JZD Portal should resubmit signing requests when they are not acknowledged by the background service |
| 216957 | [2FA] Native 2FA feature enhancements | [MFA] improvements in native MFA feature | |
| 218988 | [Admin] Introduce a function that allows so-called custom functions to be configured in JOIN Case & Document (part 3) | [JZD-Portal] Introduce custom function configurator in JOIN Admin (part 3) | |
| 189025 | 62559 | [TOOL] extend the capabilities of the MarkDeletedZtcBooks tool | [TOOL] Extend the functionality of MarkDeletedZtcBooks tool |
| 200641 | 68252 | [Freshdesk - 68252] : mail cannot be sent from JOIN | [Freshdesk - 68252] : Mail can not be sent from JOIN |
| 185050 | 48278 | [Freshdesk - 48278] : [JZD] In a specific book configuration, it takes a very long time to link an existing file | [Freshdesk - 48278] : [JZD] “Link existing file” (Koppel bestaand bestand) window takes too much time to load |
| 225758 | 79222 | [Freshdesk - 79222]: [Signing service] JOIN Cloud (AzureKS) does not always process Validsign files | [Freshdesk - 79222]: [Signing service] JOIN on AKS regularly does not correctly process signed document received from ValidSign |
| 224932 | 79221 | [Freshdesk - 79221] : [JOIN Now] Errors when uploading files (Error 500 message) | [Freshdesk - 79221] : [JOIN Now] Client cannot upload files due to error 500 being raised in DecosDirect/DecosDirect.asmx/WebSvcAddRecentItem |
| 224970 | 79221 | [Freshdesk - 79221] : JOIN Now does not use the File Control, although it is configured | [Freshdesk - 79221] : JOIN Now does not use JOIN File control although that is configured |
| 228532 | 80084 | [Freshdesk - 80084] : [Besluitvorming] Users who are renamed from LDAP to ADFS will not be able to change their proposals after the change | [Freshdesk - 80084] : Users renamed from LDAP to ADFS user name cannot edit their own decision making proposals anymore |
| 228955 | 76938 | [Freshdesk - 76938] : [Portal]]Elastic] improvements to re-indexing missing registrations | [Freshdesk - 76938] : [Portal]]Elastic] Improvement for Reindex missing item task , add check for IT_TIMESTAMP_SEARCH |
| 227905 | 78694 | [Freshdesk - 78694] : Performance improvement for registrations with many linked registrations in combination with the use of the download function | [Freshdesk - 78694] : [JZD] [Performance] Performance improvement for enabling download button when entity is linked with 2k+ document |
| 228165 | 79503 | [ADFS][AADSYNC] the “synchronize user groups” and “ADFS/JOIN user groups” setting does not work correctly | [ADFS][AADSYNC] “Synchronize user groups” and “ADFS/JOIN user groups” settings appear to not work properly |
| 229763 | 78357 | [JZD] Changes to the icon for the custom object type “commissions” | [JZD] Make colored image in tree view for Custom item Type COMMITTEE in aspx images |
| 229878 | [Freshdesk - 80084] : [Besluitvorming] When a proposal is returned, the Originator field is cleared | [Freshdesk - 80084] : [JZD][Decisionmaking] “back to creator” option is not working properly for DMD Document | |
| 229416 | [JZD] increase the version of JOIN to 2023.11 | [JZD] Increment version to 2023.11 | |
| 229568 | [Tool] ExportDbNet exports newly added database tables for JZD | [Tool] ExportDbNet does not export newly added JZD database tables | |
| 230292 | 78694 | [Freshdesk - 78694] : Performance improvement when saving a new document to which an address with many documents is linked | [JZD] Performance problem when saving new document linked to address with many document links |
| 230319 | 82225 | [Freshdesk - 82225] : [JZD] it is not possible to sign a PDF with the setting “Copy content” set to “not allowed” | [Freshdesk - 82225][JZD] Cannot sign PDF having restrictions |
| 227499 | [Freshdesk - 82423] : [JZD] Gray screen when moving a document | [Freshdesk - 82423] : [JZD Portal] issue with moving item/document | |
| 227642 | 80657 | [Freshdesk - 80657] : [AADSYNC] delay and 404 errors when reading a large AD | [Freshdesk - 80657] : [AADSYNC] Synchronizing a large active directory is slow, many 404 errors are visible in the log |
| 227080 | 78694 | [Freshdesk - 78694] : Slowness in loading related information | [Freshdesk - 77425] : [JZD] Performance issue while loading relation information |
¶ JOIN Integration (Integrations)
¶ Downloadlink 2023.11
JOIN Integration - StUF BG 2023.11
Azure KS:: 2023.11.631.49605
JOIN Integration - StUF ZKN 2023.11
Azure KS:: 2023.11.631.49606
JOIN Integration - StUF DCR 2023.11
Azure KS:: 2023.11.631.49607
JOIN Integration - JIA 2023.11
Azure KS:: 2023.11.631.49608
Other components (e.g. StUF-LVO and Berichtenbox) have not been modified in this version. Please check with previous release notes to see if you need to update it.
¶ Hotfix 2023.11
Hotfix is not yet available
¶ Action Integration 2023.11
| ID | Freshdesk Ticket | Description | Title |
|---|---|---|---|
| 225569 | [Connect] introduce the measurement of message traffic (numbers) in Connect | [Connect] Add analytics in Connect and Rest Api JZD Part -1 | |
| 226340 | [Freshdesk - 74676] : [Connect] rights issue in Connect service (which prevents Connect from viewing registrations) | [Freshdesk - 74676] : [Connect] Cannot find table 0 exception in connect service and MayView rights issue in connect service | |
| 227179 | [INTG][StUFBG] add support for NNPLV01 in StUFBG 03.10 | [INTG][StUFBG]Create NNPLV01 request response flow | |
| 231108 | 82226 | [Freshdesk - 82226] : errors when installing JIA on a local machine | [Freshdesk - 82226] : JIA.ZIP not complete in all versions |
|
¶ JOIN Customer contact
For version 2023.11, no build of the old frontend is provided. The latest hotfix (2023.9) of the old frontend is available here. All future changes will only be taken care of for the new frontend!
¶ Downloadlink 2023.11
JOIN Customer Contact 2023.11 websetup
JOIN Customer Contact 2023.11 install
¶ Hotfix 2023.11
There is a Hotfix #3 build available which is in the downloadlink that is displayed above 2023.11.8.19!
There is currently a problem in the telephony link for on-premise customers with the new frontend. We will provide a hotfix for this as soon as possible. If you use JOIN Customer Contact on-premise and you have a telephony link, wait a while for the 2023.11 hotfix. All Cloud customers can already switch after extensive testing.
¶ Actions JOIN Customer Contact 2023.11
The 2023.11 release includes important improvements such as:
- Improvements in the new frontend
Over the past few months, we have received feedback from customers and improved the new frontend. In addition, our QA department has also found many improvements and these have now been implemented. In the meantime, the new frontend is already being used by a number of customers in the production environment and we want to expand this further in the coming period.
To update the production environment, we advise you to test the test environment extensively.
-
Telephony link with Communicativ
We have established a link between JOIN Customer Contact and Communicativ. The KCC employee is called on the Communicativ software, after which the phone number is automatically forwarded to JOIN Customer Contact. This phone number is entered in the Contact Session Notes and if it is a known caller, the customer card is immediately opened. -
Pairing with Embrace
With the integration of Embrace, it is possible to show extra fields for an Employee in the details screen that are not in the Active Directory of the organization. Read More
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 details page.
| ID | Ticket | Definition | Description |
|---|---|---|---|
| 223041 | Telephony link with Communicativ | Phone integration with Communicativ | |
| 228476 | Integration with Embrace for data for Employees | Integration with Embrace for data of Employees | |
| 141937 | Show documents and files for cases from the InProcess case system | Fetch documents and files for Cases from InProces | |
| 228268 | Show url of the environment in JOIN Customer Contact Management | Show url of environment in the customer overview in JKC admin | |
| 162980 | 44751 | Sequence adjusted from recent activity and contact history | Changed sequence of recent activity and contact history |
| 180114 | 59184 | [Ticket] Excel overview of the list of tickets | [Ticket] Add Export to Excel in action menu list |
| 228143 | 79100 | JOIN Opening customer contact in a second screen doesn’t work | Open application in a second tab doesn’t work |
| 228145 | 81058 + 81621 | Niet alle ingevulde gegevens worden bewaard bij een geparkeerde sessie | Not all data is correctly saved in a parked session. |
| 230046 | 81469 | Toevoegen van de topbalk geeft problemen bij het tonen van bijv. Medewerkers | Adding top bar is giving problems with displaying f.e. employee panel |
| 230392 | 81061 | Tegels voor contactgeschiedenis tonen geen aantallen | No count in dashboard tiles for contact history |
| 230439 | 82232 | E-formulier werd niet weergegeven in de Terugbelnotitie-dropdown | Eform is not displayed in Callback Note dropdown |
| 230669 | 82541 | Zoeken in contact geschiedenis op behandelaar werkt niet naar behoren | Searching in contact history on handler doesn’t work properly |
| 223128 | 77790 | Verbeteringen in het SSO inloggen | Improvement in SSO login |
| 221457 | No more showing the login screen when refreshing JOIN Customer Contact | Don’t show login screen while refreshing application | |
| 212949 | Improve the display of numbers in the dashboard | Task count not reflecting correctly when handled task | |
| 229340 | [Hotfix #1] Niet mogelijk om Whatsapp gesprekken te verzenden | Not able to send whatsApp message from JKC until we send message to JKC from portal | |
| 230192 | [Hotfix #1] Verbeteringen in de agenda | Display multiple relative slots as one | |
| 230398 | 81229 | [Hotfix #1] Geen melding ‘nummer in gesprek’ | No message ‘Number is busy’ |
| 231893 | [Hotfix #1] Recente activiteiten bij inkomend gesprek ontbrak | Show recent activity on incoming call feature missing | |
| 232000 | [Hotfix #1] Opneem knop verdween achter inkomend gesprek pop up | Pickup button disappear outside of the incoming phone screen | |
| 232001 | [Hotfix #1] Bij het doorsturen van een sessie werd er geen pop up getoond ‘accepteer de sessie’ | When forwarding session people getting notification without having an option to accept the session | |
| 232517 | [Hotfix #1] Niet tonen van een spinner wanneer gebruiker de extentie nummer registreerde | Not showing loading spinner when registering extension | |
| 232518 | [Hotfix #1] Niet tonen van een pop up met ‘incorrect nummer’ na het bellen | Not showing invalid number popup information after dialing | |
| 232868 | [Hotfix #1] Inkomend gesprek pop up was niet te verplaatsen | Incoming call popup is not draggable | |
| 232960 | [Hotfix #1] Inkomend gesprek pop up toonde niet de persoonsgegevens wanneer deze opgehaald waren | Incoming call popup not fetching person details if known | |
| 233762 | [Hotfix #1] Terugnemen/hou in de wacht pop up werkte niet goed | Take back/ keep on hold popup broken (Dutch culture) | |
| 230748 | [Hotfix #1] Tonen van horizontale scrollbar bij ‘Mijn taken’ | Showing horizontal scrollbar on task ‘My’ section | |
| 231021 | [Hotfix #1] Klikken op Enter sloot alle popups bij het opnemen van een telefoongesprek | Using ‘Enter Key’ after phone pickup(pickup call using enter key) closing all popups | |
| 231265 | [Hotfix #1] Deeplink van Taken/Tickets werkte niet tijdens de eerste keer klikken | Ticket/Task deeplink not working in first attempt | |
| 231805 | [Hotfix #1] Eerste login van nieuwe gebruiker liet JKC crashen | First login of a new user breaks application | |
| 231858 | [Hotfix #1] Tonen van meerdere velden in het Medewerker paneel | UI issue on employee panel when employee have some more fields | |
| 231859 | [Hotfix #1] Zoeken menu verdwijnt achter het dashboard wanneer er voor de tweede keer gezocht wordt | The search dropdown menu is displayed “behind” the dashboard the second time you open it. | |
| 232155 | [Hotfix #1] E-mailadres wordt niet gecontroleerd in toevoegen/bewerk scherm | Email address is not validating on add/edit screen | |
| 232410 | [Hotfix #1] Notificatie webpart geeft spinner wanneer het aantal 0 is | Notifications webpart shows infinite spinner if result gives 0 notifications | |
| 232826 | [Hotfix #1] Nieuws werd niet geopend in een nieuw scherm bij optie ‘alle bronnen’ | News not opening in new window if search in option ‘All source’ and then open | |
| 232870 | [Hotfix #1] Terug gaan naar Employee search geeft ‘No records found’ | Using back button showing employee search result screen with availability ‘No record found’ | |
| 233239 | [Hotfix #1] Sorteren op behandelaar werkt niet in Contactgeschiedenis | Sorting on handler is not working | |
| 234058 | [Hotfix #1] Bewerk scherm verscheen niet voor Taken | Edit screen not appears for task | |
| 224815 | 79088 | [Hotfix #2] niet geselecteerde medewerker in kruimelpad | Not selected employees also appear in the breadcrumb trail |
| 234090 | 80703 | [Hotfix #2] tegels contacten afgehandeld worden geen aantallen vermeld | Tiles for contacts handled don’t show the count |
| 226597 | 80175 | [Hotfix #2] issues koppeling JCC afspraken | Issues with JCC appointments (integration) |
| 234690 | 84472 | [Hotfix #2] Bij Maak brief wordt altijd het eerste sjabloon gebruikt | The first template is always used when creation a letter from JKC |
| 235458 | 84461 | [Hotfix #2] Testomgeving: knop e-formulier komt niet tevoorschijn | The e-Form button does not (directly) appear |
| 233929 | 83461 | [Hotfix #2] Openen geparkeerde sessie met gestopt whatsapp gesprek werkt niet goed | Opening a parked session for a handled WhatsApp conversation is not working as intended |
| 225194 | 79399 | [Hotfix #2] Ontbrekende hyperlink in whatsapp gesprekken acceptatieomgeving | Hyperlinks are not displayed correctly in WhatsApp conversations |
| 235580 | QA Issue | [Hotfix #2] [Roger365] Klantnaam is niet ingevuld, maar Persoon gevonden wordt getoond | [Roger365] Customer isn’t filled in and we show the text ‘Fetching details’ |
| 232871 | QA Issue | [Hotfix #2] [InProces] Gerelateerde bestand wordt niet getoond wanneer het document wordt geladen in de viewer | [InProces] Related file not showing in document when document load in viewer |
| 237541 | 85700 | [Hotfix #3] Vraagveld bij aanmaken terugbelverzoek mist regeleindes en scrollbar na update | Question field is missing line breaks and scrollbar |
| 237807 | 85813 | [Hotfix #3] Na het klikken van de TBN link, komt de gebruiker uit in het hoofdscherm van JKC | The TBN deeplink does not open the handle screen in JKC |