¶ Releasenotes JOIN version 2022.6
On this page you will find all actions that are included in version 2022.6. 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 at the beginning of July 2022.
The support of version 2021.12 will therefore expire on 15 September 2022. If you have not updated your JOIN Environment since the previous major release (2021.12), you will find the intermediate minor updates in the wiki (https://wiki.decos.com/en/releasenotes). We recommend that you also read these. Actions included in version 2022.2 and 2022.4 are automatically part of version 2022.6
Do you want us to update your environment to this version? Please contact our support team JOIN Support
If you want to know until when we support older versions of JOIN Zaak & Document, please look here: click here for the SLA
*The release of JOIN Customer Contact has been postponed. At the moment it is not yet clear when JOIN Customer Contact version 2022.6 will be released.
¶ 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 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.
¶ Whitepaper
The JOIN Whitepaper can be found here:
[Whitepaper JOIN] (https://wiki.decos.com/en/whitepaper)
¶ Integration case types
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)
¶ Hotfix 2022.6
We strongly recommend that you install or have installed the most recent hotfix. If you use Azure KS, Decos will install the hotfix. In that case, a hotfix also automatically includes the actions that were included in the previous hotfixes. For non-Azure KS environments, this depends on the components included in the hotfix.
- hotfix 810:see actions below
AKS - 2022.6.631.15389
188766: introduce a heartbeat check on Azure KS components (search & backgroundservice)
189885/191700: error when creating thumbnails (thumbnails) in JOIN
191391/191392: performance improvements (database) - part 1
191720: performance improvements (database) - part 1 - hotfix 806:see actions below
AKS - 2022.6.631.12671
188769: [Freshdesk - 62390] : [performance] workflows are slow to link when there are many available workflows
188667: [Admin] introduce maximum values for “max preview page height” and “max preview page width” settings to avoid performance issues
188867: [Freshdesk - 62724] : problem when uploading word documents in an old link with SmartDocuments
189139: [AKS] Various performance improvements for JOIN Case & Document in Azure KS environments (database query optimizations) - [hotfix 805 for action 186475 "use Azure Servicebus premium to handle StUF messages]
AKS - 2022.6.631.12030 (StUF-ZKN) - hotfix 804 for action 187326 "performance issue when recalculating macros
AKS - 2022.6.631.11768 - hotfix 803 for action 186495 “duplicate workflows”
AKS - 2022.6.631.11603 - hotfix 802 for action 186512 "StUF-BG persons are created in book “unknown persons”
AKS - 2022.6.631.10840 - [hotfix 794 for action 183411 “error in template editor”]
AKS - 2022.6.631.9786 (for non AKS customers, the hotfix actions are included in a new version of 2022.6, released on August 18) - [hotfix 792 for actions 180480, 183903 (“Migration Docker to Microsoft Container D”) and 184469 (“Error in Connect System import”) ]
AKS - 2022.6.631.9682 (for non AKS customers, the hotfix actions are included in a new version of 2022.6, released on August 18) - [hotfix 791 voor acties 180054 (StUF Volgindicaties) en 181954 (On prem ADFS issues)]
AKS - 2022.6.631.8872 (for non AKS customers, the hotfix actions are included in a new version of 2022.6, released on August 18) - [hotfix 788 for action 182437 (Connect security)]
AKS - 2022.6.631.8651 (only AKS) - [hotfix 787 for action #180783 introduce an extra check for the right to delete items]
AKS - 2022.6.631.73923 (for non AKS customers, the hotfix actions are included in a new version of 2022.6, released on August 18) - [Hotfix 785 for JZD actions #180194, #180709 and #181113 (dataindexer & duplicate workflows)]
AKS - 2022.6.631.73810 (for non AKS customers, the hotfix actions are included in a new version of 2022.6, released on August 18)
¶ JOIN Case & Document
¶ Downloadlink 2022.6
[JOIN Case & Document 2022.6 EXE] (https://support.decos.nl/qa/JOIN-patch226631-20220812-exe.zip)
[JOIN Case & Document 2022.6 MSI] (https://support.decos.nl/qa/JOIN-patch226631-20220812-msi.zip)
Azure KS: 2022.6.631.8001
[JOIN Client 32 bit 2022.6 EXE] (https://support.decos.nl/qa/JOINNowClient226631-20220610-exe.zip)
[JOIN Client 32 bit 2022.6 MSI] (https://support.decos.nl/qa/JOINNowClient226631-20220610-msi.zip)
[JOIN Client 64 bit 2022.6 EXE] (https://support.decos.nl/qa/JOINNowClientX64-226631-20220610-exe.zip)
[JOIN Client 64 bit 2022.6 MSI ] (https://support.decos.nl/qa/JOINNowClientX64-226631-20220610-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).
¶ Actions
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 | Freshdesk Ticket | Description | Description |
|---|---|---|---|
| 148144 | 37740 | [Freshdesk - 37740] : Enabling and disabling audit functions is not audited | [Freshdesk - 37740] : [Audit] enabling and disabling options in audit (admin) are not audited |
| 165745 | [Freshdesk - 56690] : After a validation notification in the new document screen, a file is uploaded 2x in JOIN | [Freshdesk - 56690] : [JZD] Duplicate files gets attached to the document with each validation message. | |
| 166481 | 46375 | [Freshdesk : 46375] - [Decision making] permissions for new approval routes are not synchronized correctly with JOIN | [Freshdesk - 46375] : Rights on the access roles for new approval routes are not synced |
| 170951 | 45969 | [Freshdesk - 45969] : [Decision Making] The list of approval routes is sorted only for an administrator | [Freshdesk - 45969] : The list of approval route is not sorted if user is not an Admin user |
| 167944 | 47371 | [Freshdesk - 47371] : [Audit] When a book is deleted, the audit does not state by which user it was done | [Freshdesk - 47371] : [Audit] when book is deleted, it doesn’t record the user who performed the action |
| 171465 | 50330 | [Freshdesk - 50330] : Macro in Subject field (Main Profile Profile Case Document) does not work correctly when using a BLOCK macro | [Freshdesk - 50330] : Macro in Subject field of “Case document profile main profile” does not work |
| 174991 | [Freshdesk - 50390] : duplicate item profiles arise when the ZTC Sync service cannot communicate with the database and/or ZTC Mapping table | [ZTC SYNC] Customer is facing creation of duplicate itemprofiles | |
| 172650 | 49282 | [Freshdesk - 49282] : [AzureKS][JOIN Admin] management overviews are not generated in Azure KS environments | [Freshdesk - 49282] : [AzureKS][JOIN Admin] Management report not working for AKS customer |
| 175362 | 49717 | [Freshdesk - 49717] : Date in March is not displayed correctly in dotx template when an MMMM format template block and English language is used | [Freshdesk - 49717] : Date in March is not resolved in dotx template when a template block with MMMM format and Dutch language is used |
| 174571 | 57157 | [Freshdesk - 57157] : Mutations in excel, opened from Join Now, are not always saved | [Freshdesk - 57157] : Changes in an Excel document opened via JOIN Now are not always saved |
| 175784 | 49854 | [Freshdesk - 49854] : [Decision-making] when relinking the workflow, paragraphs are doubled | [Freshdesk - 49854] : Relinking of workflow creates duplicate Document chapters |
| 175983 | 50786 | [Freshdesk - 50786] : workflow actions remain visible after completing the only visible field | [Freshdesk - 50786] : Workflow items stay visible after filling item applies to field |
| 176364 | 57525 | [Freshdesk - 57525] : If two fields in an item profile use a template building block, the output of both fields is the same | [Freshdesk - 57525] : If two fields in an item profile use a template block, the output of both fields is the same |
| 177127 | [Decision-making] Do not allow paragraphs to be changed in the “take decision step” unless the user is the practitioner | [JZD] [DM] Chapter edition is possible in process step for unauthorized users | |
| 177355 | [BAG] Data is not updated correctly in an existing BAG object when it is retrieved again via the new BAG API | [BAG] JZD DecosGeo table is not updated when a new BAG object is linked | |
| 177430 | 58307 | [Freshdesk - 58307] : Join shows the drag and drop files window on wrong screen | [Freshdesk - 58307] : JOIN shows the drag files window on wrong screen |
| 177876 | Scheduling management overviews does not work in Azure KS environments | Scheduled Overview does not work for Management Overview Reports | |
| 178542 | It is not possible to send management overviews by email in Azure Kubernetes environments | Email Report feature does not work on Management Overview Reports | |
| 178661 | [Anonimizer] incorrect endpoint in Anonimizer function | [Anonimizer] Incorrect endpoint in Anonymizer SDK | |
| 178707 | Preview feature does not work in management overviews in Azure Kubernetes environments | Query Preview feature does not work on Management Overview Reports | |
| 179385 | [Anonymize] stability improvements in the link with TM7 | [Anonymizer] TM7 anonymization improvements | |
| 179556 | 59176 | [Freshdesk - 59176] : Templates will be incorrectly removed after updating to 2022.4 | [Freshdesk - 59176] : Template items are incorrectly removed by deleted items cleanup task in JOIN 2022.4 |
| 179603 | 59142 | [Freshdesk - 59142] : Anonymizing in case created by stuf-zkn shows stuf-zkn message instead of transactions | [Freshdesk - 59142] : Anonymizer editor cannot be opened when anonymization is started for a StUF-ZKN case |
| 179927 | 58586 | [Freshdesk - 58586] : JOIN does not generate a PDF and does not open the generated PDF for a newly linked scan when JOIN File Control is used | [Freshdesk - 58586] : JOIN does not generate a PDF or open the generated PDF for a newly linked scan when JOIN File Control is used |
| 180194 | 48100 | [Freshdesk - 48100] : Indexing of new files does not happen correctly in Oracle environments | [Freshdesk - 48100] : New files are not indexed by DecosDataIndex.exe (indexing service) |
| 180697 | [RestAPI] allows the allowed URL in the API to contain both uppercase and lowercase letters | [REST API] Support case insensitive check for Allowed URL in API | |
| 181128 | [Freshdesk - 59480] : [Join Mobile] JOIN Mobile has not been functioning correctly since the introduction of the “disallowed file types” feature | [Freshdesk - 59480] : [Join Mobile] Join mobile stopped working after disallowed file extension feature changed | |
| 180514 | Various performance improvements in JOIN Case & Document for loading forms and retrieving linked objects | [Performance] Ensure that controls use the same cached DecosApp object as the page where they are hosted | |
| 180170 | Changes to the “case history” tool for a specific customer | [Case History Tool] Add details for Customer contact center handler in tool | |
| 179725 | Update version number to 2022.6 | Increment JZD version to 2022.6 | |
| 178800 | [admin] supports more than 62 allowed file types in configuration for “allowed filetypes” | [Admin] Support Allowed file extensions list longer than 250 characters | |
| 179008 | 58981 | [Freshdesk - 58981] : stability improvements in background service for the scanning process | [Freshdesk - 58981] : Backgroundservice improvements for on-demand scan processing |
| 179378 | [Anonimizer] stability improvements in the link with Datamask | [Anonymizer] DataMask anonymizer improvements | |
| 178365 | Adding Xential and Smartdocuments templates to the allowed file types | Whitelist Xential and smart document templates | |
| 177917 | [JOIN Teams] admin configurations | [JOIN Teams] admin configurations | |
| 174231 | 56969 | [Freshdesk - 56969] : [PDF Converter Service] Improvements in Out-of-Memory Services | [Freshdesk - 56969] : [PDF Converter Service] Improvement in PDF converter service for when service encounters OutOfMemoryException exception |
| 175606 | 57441 | [Freshdesk - 57441] : Improve cyclical recalculation of macros in linked registrations | [Freshdesk - 57441] : Improve cyclic macro recalculation in linked items |
| 175663 | 50404 | [Freshdesk - 50404]: Improvements to the database anonymization/pseudonymization tool | [Freshdesk - 50404]: [Anonymization Tool] Improvements |
| 171539 | Support JZD Jukebox tool in Azure Kubernetes environments | Transition JZD Jukebox to AKS | |
| 168754 | 49075 | [Freshdesk - 49075] : [Mergetool] Workflow does not show item profile and associates a role | [Freshdesk - 49075] : [Mergetool] The itemprofile that is linked in the Automatic Decision step from Workflow in source DB is not linked anymore in target DB after the merge |
| 140550 | 34419 | [JOIN Decision Making] only allows the action holder (user or role) to edit proposal (paragraphs and attachments) after submitting the proposal | [Freshdesk - 34419] improve the lock of files during decision making process |
| 145983 | [Search] Search is not returning result when max highlight offset is reached for one or more records | [Search] Search is not returning result when max highlight offset is reached for one or more records | |
| 159784 | [JZD] Make selecting an address role optionally mandatory when linking an address to a registration | [JZD] make addressrole selection mandatory | |
| 159785 | [Checklists/workflow] Change the behavior of checklists | [Checklists/workflow] change checklistbehavior | |
| 162808 | 46460 | [Freshdesk - 46460] : Decos Sjabloon Editor kan niet met de JOIN Server verbinden wanneer TLS 1.2 wordt gebruikt | [Freshdesk - 46460] : Template Editor cannot connect to JOIN server unless TLS 1.0 and 1.1 are allowed |
| 174986 | Update BAG service from .NET Core 3.1 to .NET 6.0 | Update BAG service from .NET Core 3.1 to NET 6.0 | |
| 174987 | Update anonymizer service from .NET 5.0 to NET 6.0 | Update anonymizer service from .NET 5.0 to NET 6.0 | |
| 180194 | 48100 | [Freshdesk - 48100] : Indexing of new files does not happen correctly in Oracle environments | Bug 180194: [Freshdesk - 48100] : New files are not indexed by DecosDataIndex.exe (indexing service) |
| 181113 | 47732 | [Freshdesk - 47732] : sometimes a worklfow is started twice on a case document in combination with StUF-DCR | Bug 181113: [Freshdesk - 47732] : Duplicate workflow are being started for Exclusive documents |
Points of attention:
177127: In the decision-making process, it is very important that the right people have access to the proposal (paragraphs and annexes) at the right moments in the process. editing a proposal (paragraphs and annexes) must be limited:
- in the drafting phase, the author may edit the proposal (fill in paragraphs, link and unlink attachments, edit the content of attachments
- in the drafting phase, the advisor may edit the proposal if this is allowed in the configuration of JOIN (option “Allow to edit proposal in feedback action”)
- in the approval phase, the approval role may edit the proposal if this is indicated in the configuration (in JOIN Case types)
- in the decision-making phase, the decision-maker (role) may edit the proposal.
- in all other stages, the proposal cannot be edited. The attachments can be consulted but are blocked for changes. This also applies to the drafter.
With the adjustments we have made, all possible inconsistencies have been removed from the process and the editing rights have been made very restrictive (based on the above principles).
We can well imagine that you want to analyse your decision-making processes again. We therefore advise you to contact one of decos’ decision-making specialists.
159785: We are introducing a major extension of our checklist functionality in version 2022.6:
- the “optional” option already existed. A check does not have to be set to YES. The outcome of the checklist is not influenced by this check.
- the option “default empty” is new. A check does not yet have an answer when starting the checklist action. The practitioner must therefore explicitly give an “answer” here (YES or NO). this makes the check more of a question (for example, “has the applicant submitted a copy of passport”)
- the option “answer has no influence on outcome” is new: although a check must be completed, the outcome of the checklist (positive or negative) will not be influenced by this. So you can, for example, force someone to perform a certain task or give an answer, but the workflow just keeps going through the right route.
The strength of the above is mainly in the amount of combinations you can make. Especially when automatic checks are going to be used.
We advise you to call in advice and support from one of our specialists (consultants / digital professionals) to set up these checks.
It is important to know that the same functionality is also available in JOIN Case Types:
159784: New in version 2022.6 is the ability to make the selection of address roles mandatory. This functionality is used to a large extent in the case system, but can also be used in non-case configurations (and in different registration types).
How does it work? In JOIN Admin you can check the setting “mandatory address role selection” in the book options. When this is checked. then when linking an address, an address role must be selected.
When you check the option on the “business” book, the functionality works for all case types. If you do not want this, you will have to configure it per case type.
In JOIN Case & Document, the following is done:
- in the address pairing screen, the address role column is visible by default. It also can’t be turned off
- for new addresses to be linked, you will receive an error message if you do not select the address role
- for new addresses to be created, you must select an address role from the registration screen.
We have ensured that the function is “backwards compatible”. This means that we do not show the notification for already linked addresses.
¶ JOIN Integrations
¶ Downloadlink 2022.6
JOIN Integrations - StUF DCR
Azure KS:
[JOIN Integrations - Admin (JIA)] (https://support.decos.nl/setups/Integrations/!JIA_JOIN_Integration_Administration/2022.06/jia.zip)
Azure KS:
JOIN Integrations - StUF ZKN
Azure KS:
¶ Actions
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 | Freshdesk | Description | Definition | |
|---|---|---|---|---|
| 176828 | 58040 | [Freshdesk - 58040] : Hyphen in e-mail address prevents failure notifications e-mails from being send. | [Freshdesk - 58040] : Dash (hyphen) in email address ensures that failure mails for StUF-ZKN cannot be sent | |
| 179489 | [INTG] [JIA] JIA not able to Resend failed messages with StUFZKN HA version | [JIA] resending failed mesages does not work when StUF-ZKN is running in high available mode | ||
| 179657 | [StUFDCR] [AKS] Dll issue in the StUFDCR 2022.4 version | [StUFDCR] update error in StUFDCR version 2022.4 | ||
| 179666 | [JIA] [AKS] Error while logging the request in DatabaseMessageLogger | [JIA] error in the databasemessage logger | ||
| 180027 | [Connect] Object null reference fix | [Connect] error message “object null reference” in logging | ||
| 180442 | [INTG] Unable to get logs for StUF DCR in Kiabana | [INT] Unable to retrieve logs for StUFF DCR in Kibana | ||
| 177713 | 58414 | [Freshdesk - 58414] : STUFZKN cannot send e-mail to valid e-mail address | [Freshdesk - 58414] : STUFZKN cannot send mail to a valid email address in an Azure KS environment | |
| 178227 | [JIA] High CPU usage issue | [JIA] High CPU issues when starting JIA in AzureKS environments | ||
| 178823 | 58223 | [Freshdesk - 58223] : issues with merging external templates | [Freshdesk - 58223] : Problems Merging External Templates | |
| 147191 | 35939 | [Freshdesk - 35939] : [Connect] Macro in status notification mail not evaluated properly if the case is created via Connect | [Freshdesk - 35939] : [StUFZKN] address macros are not executed correctly when a case is created via StUFZKN | |
| 165802 | [SETUP] Update to ModifyAssemblyVersioning tool to resolve build version max limit issue | [SETUP] Update to ModifyAssemblyVersioning tool improvements | ||
| 176347 | [StUFZKN] Send notification mail using AWS SES | [StUFZKN] [AzureKS] makes it possible to send emails in Azure KS environments for failed StUF-ZKN messages | ||
| 173207 | [ZGW] [NC] Make NRC deployable on AKS | [ZGWAPI] ensure that NRC API (notifaction API) can be installed in Azure Kubernetes environments | ||
| 173208 | [ZGW] [NC] Implement retry mechanism for NRC | [ZGWAPI] Implement a retry mechanism for NRC [Notification API] ]when notifications cannot be delivered to the receiving consumer party | ||
| 174510 | [ZGW] [NC] Create database for Notification API | [ZGWAPI] create a central database for the notification API | ||
| 175296 | [ZGW] [AC] Create project structure and database for Authorization API | [ZGW API] WBS and database for AC (authorization API) | ||
| 175302 | [ZGW] [AC] Make Authorization API deployable in AKS cluster | [ZGWAPI] Enable authorization API (AC) to be installed in Azure Kubernetes environments | ||
| 175304 | [ZGW] [AC] User should be able to retrieve all applications, with associated authorizations | [ZGWAPI] User must be able to retrieve all linked systems based on authorizations (AC) | ||
| 175305 | [ZGW] [AC] User can request an application and associated authorizations based on clientid | [ZGWAPI] user must be able to retrieve application and authorizations using ClientID (AC) | ||
| 175306 | [ZGW] [AC] User can request a single application with associated authorizations using application unique id | [ZGWAPI] user must be able to retrieve application and authorizations based on ApplicationID | ||
| 175307 | [ZGW] [AC] Implement authentication in Authorization API | [ZGWAPI] implement authentication in Authorization API (AC) | ||
| 175308 | [ZGW] [AC] Implement authorization in Authorization API | [ZGWAPI] Implement authorizations in authorizations API (AC) | ||
| 175309 | [ZGW] [AC] [Case Types] User should be able to register application with associated authorizations for AC and NC components | [ZGWAPI] [Case types] user should be able to register application with associated authorizations for both AC and NC | ||
| 175312 | [ZGW] [AC] [Case Types] User should be able to link external application and configure authorization scopes for Document Type | [ZGWAPI] user must be able to link external application and configure authorization scopes by document type | ||
| 175313 | [ZGW] [AC] [Case Types] User should be able to link external application and configure authorization scopes for Decision Type | [ZGWAPI] user must be able to link external application and configure authorization scopes by decision type | ||
| 176277 | [ZGW] [ZTC] Refactor ZTC (Catalog API) solution to use common projects in solution | [ZGWAPI] improvements in the implementation of the ZTC API | ||
| 177517 | [ZGW] [ZTC] Authorization scopes functionality for Case type, Decision and Document should only enabled if ZGW license is enabled. | [ZGWAPI] [Case Types] ZGW API functionality in case types is available with a valid license | ||
| 179375 | [ZGW] [ZRC] In Case ObjectsController–>ReadAsync(), ListAsync() should return empty value instead of NotImplementedException for Rx-Mission | [ZGWAPI] return “blank” instead of “unimplemented” for ReadAsync(), ListAsync() operations, | ||
| 180260 | [ZGW] [AC/NC] Not getting proper forbidden (403) response while authorization fails | [ZGWAPI] incorrect error message when authorization is not successful (must be 403) | ||
| 157682 | [ZGWAPI] Audit for ZRC, DRC, BRC | {ZGWAPI] add support to write audit for API transactions (ZRC, DRC, BRC) | ||
| 159153 | [ZGWAPI] Fetch all audit trail rules associated with the ZRC, DRC and BRC | [ZGWAPI] retrieve all audit trail rules associated with the ZRC (Cases), DRC (documents) and BRC (decisions) APIs | ||
| 159155 | [ZGWAPI] NC for ZGW API implementation | [ZGWAPI] Implementation of the Notification component for the Case-oriented working APIs (NC) | ||
| 159160 | [ZGWAPI] Retaining of audit trail data for ZRC, DRC and BRC | [ZGWAPI] Save all audit trail data for ZRC (cases), DRC (documents) and BRC (Decisions) | ||
| 173187 | [ZGW] [NC] Make Notification API deployable in AKS cluster | [AzureKS] [ZGWAPI] Enable NC to be installed in AzureKS environments | ||
| 173189 | [ZGW] [NC] Implement Subscription Notification API action methods | [ZGWAPI] implement Notification subscriptions (NC API) | ||
| 173197 | [ZGW] [NC] Implement Channel action methods in Notification API | [ZGWAPI] Implement channels in Notification API (NC API) | ||
| 173199 | [ZGW] [NC] Implement notification action method of Notification API | [ZGWAPI] Implement Notification actions in Notification API (NC API) | ||
| 173202 | [ZGW] [NC] Implement authentication in Notification API | [ZGWAPI] implement authentication in Notification API (NC-API) | ||
| 173204 | [ZGW] [NC] Implement authorization in Notification API | [ZGWAPI] Implement authorizations in Notification API (NC API) | ||
| 173205 | [ZGW] [NC] Implement notification routing component (NRC) service | [ZGW] Implement notification routing component (NRC) service in Notification API (NC-API) | ||
| 173207 | [ZGW] [NC] Make NRC deployable on AKS | [ZGWAPI] ensure that NRC API (notifaction API) can be installed in Azure Kubernetes environments | ||
| 173208 | [ZGW] [NC] Implement retry mechanism for NRC | [ZGWAPI] Implement a retry mechanism for NRC [Notification API] ]when notifications cannot be delivered to the receiving consumer party | ||
| 174510 | [ZGW] [NC] Create database for Notification API | [ZGWAPI] create a central database for the notification API | ||
| 175296 | [ZGW] [AC] Create project structure and database for Authorization API | [ZGW API] WBS and database for AC (authorization API) | ||
| 175302 | [ZGW] [AC] Make Authorization API deployable in AKS cluster | [ZGWAPI] Enable the Authorization API (AC) to be installed in Azure Kubernetes environments | ||
| 175304 | [ZGW] [AC] User should be able to retrieve all applications, with associated authorizations | [ZGWAPI] User must be able to retrieve all linked systems based on authorizations (AC) | ||
| 175305 | [ZGW] [AC] User can request an application and associated authorizations based on clientid | [ZGWAPI] user must be able to retrieve application and authorizations using ClientID (AC) | ||
| 175306 | [ZGW] [AC] User can request a single application with associated authorizations using application unique id | [ZGWAPI] user must be able to retrieve application and authorizations based on ApplicationID | ||
| 175307 | [ZGW] [AC] Implement authentication in Authorization API | [ZGWAPI] implement authentication in Authorization API (AC) | ||
| 175308 | [ZGW] [AC] Implement authorization in Authorization API | [ZGWAPI] Implement authorizations in authorizations API (AC) | ||
| 175309 | [ZGW] [AC] [Case Types] User should be able to register application with associated authorizations for AC and NC components | [ZGWAPI] [Case types] user should be able to register application with associated authorizations for both AC and NC | ||
| 175312 | [ZGW] [AC] [Case Types] User should be able to link external application and configure authorization scopes for Document Type | [ZGWAPI] user must be able to link external application and configure authorization scopes by document type | ||
| 175313 | [ZGW] [AC] [Case Types] User should be able to link external application and configure authorization scopes for Decision Type | [ZGWAPI] user must be able to link external application and configure authorization scopes by decision type | ||
| 177517 | [ZGW] [ZTC] Authorization scopes functionality for Case type, Decision and Document should only enabled if ZGW license is enabled. | [ZGWAPI] [Case Types] ZGW API functionality in case types is available with a valid license | ||
| 179375 | [ZGW] [ZRC] In Case ObjectsController–>ReadAsync(), ListAsync() should return empty value instead of NotImplementedException for Rx-Mission | [ZGWAPI] return “blank” instead of “non-implemented” for ReadAsync(), ListAsync() operations |
Points of attention:
176347 It is possible to receive an e-mail for so-called “failed messages” (StUF-ZKN messages that could not be processed). However, this functionality was never developed for customers in the Azure Kubernetes Cloud.
The functionality has now been developed and will be available from version 2022.6. The functionality will be activated by our technical consultant during the update.
ZGW APIs in the past period we have worked very the further development of the Case-oriented Working APIs:
- a fully working audit functionality is available and operational
- we have our own implementation of the Notification API (including management functions in JOIN Case types)
- we have our own implementation of the Authorization API (including management functions in JOIN Case types)
At the moment we are still in a test process with both Genetics (Powerbrowser) and Roxit (RxMission). As soon as there is more clarity about this, you will hear from us through the various channels.
¶ JOIN Customer contact
The release of JOIN Customer Contact version 2022.6 has been postponed. At the moment it is not yet known when this version will be released.