Known issues

This might happen, if you have manually removed the custom font installed by WorkZone for Office.

Workaround: Reinstall the WorkZone for Office client on your local machine and do not remove the custom font.

This issue is only relevant for customers with extended Office 2016 support.

Excel crashes on Office 2016 when it is opened from WorkZone Client. This is not a WorkZone issue. To solve the issue, install all Microsoft Office updates. For information about updating Office, see the Microsoft article Update Office with Microsoft Update.

For AI suggested redactions (available under Advanced PDF > Redaction pane > Search using AI), the following entities might work incorrectly: 

• Legal code section: The resulting suggestions are not exact. We recommend not to use this entity in the 2023.3 version.
• Dates: Sometimes not all digits within the dates are found and/or suggested for redaction.
• Phone numbers: Sometimes the resulting suggestions include other numbers than the phone numbers.

PDF/UA validation often fails for standard and custom reports, as well as case documents selected for print to a PDF file. These reports are still available as regular PDF files.

When you reply to an e-mail that has been saved in WorkZone with the Save on send feature, a message will appear confirming which case the e-mail will be saved to. If you reply in Outlook Web and click Pop out to open the draft in a new window, this notification may disappear. The e-mail will still be saved on the selected case, even though the text is not displayed.

This is a known issue that is caused by two known issues from Microsoft Office:

• Notification message set using Office.js for an email item disappears if mail opened in pop-out view (External link)
• InsightMessage getting removed once we pop out the compose pane to new Window. (External link)

When you work in Outlook on a macOS, your replies to an e-mail that has been saved on a case in WorkZone, will not automatically be saved on the case.

Workaround: You can use the Outlook web version instead of the app, or manually select a case to save the reply e-mail on in the WorkZone pane.

If the Create new case dialog has been configured to show the Primary party field, but no default party role has been selected for the primary parties that are added via Outlook, the primary parties will be saved to WorkZone without a party role, and it is not possible to change it.

Workaround: A user with the CONFIGADM access code must select a default party role to be applied to primary parties that are added via the Create new case dialog in Outlook. To select a default party role, click Configure in the Create new case dialog, go to the Primary party field, and click the Advanced settings icon, where you can select your party role to be applied. When you have done this, go to the relevant case in WorkZone Client and, in the Primary party field, select a new party from the dropdown list. When you change the primary party, the default party role is automatically updated, and you can change it back to the initial primary party.

Workaround: Clear the Office cache, as described in this Microsoft article.

Workaround: If you enter an invalid date format, the last valid date from this field will be automatically inserted instead. If you enter an invalid time format, the last inserted valid time will be automatically inserted instead.

On Office 2019 with Internet Explorer 11, when configuring a new case dialog from WorkZone 365, a warning that "This add-in is not responding" is shown after you add a few fields.

Workaround: Close the warning and continue to add the needed fields.

For purposes of security and privacy, Safari 12 includes the Intelligent Tracking Prevention (ITP) 2.0, which does not allow the browser to set any 3rd party cookies and treats the cookies set by Identity Providers as 3rd party cookies.

Workaround: Disable the ITP setting (go to Preferences > Privacy tab, and deselect the Prevent cross-site tracking option under Website tracking).

On macOS machines, if the Outlook meeting does not contain any text in the email body, the WorkZone Meeting pane will be stuck on loading.

Workaround: When creating a new meeting event, add some text to the email body before opening the WorkZone Meeting pane.

When you switch to a different user account, the WorkZone 365 add-in fails to load, showing the '404' error. This happens, because WorkZone 365 stores information to get the token for your user account in the local storage, but it is not invalidated when you switch to a different user.

Workaround: Clear the Office cache, as described in this Microsoft article.

When you try to merge WorkZone information into a Word template, no data is merged for the merge fields placed inside the page header or within shapes. This happens, because API is not supported for Office 2019 and 2021.

Workaround: Upgrade your Word application to a later version, or use the Merge as copy option to merge the needed WorkZone information. See Merge as copy.

When you create an appointment series in your Outlook calendar and save any of these appointments to WorkZone, they all share the same agenda and represent the same WorkZone meeting.

If you upgrade from 2024.1 or earlier releases to 2026.1 and use SmartPost, you must cancel running SmartPost processes and restart them using the Send SmartPost dialog (not from the Processes Overview). This is to ensure that SmartPost uses the upgraded NgDP dispatcher.

The reason for restarting the SmartPost processes is that in 2024.1, an HTTP error 429 may occur when getting receipts due to changes of the Digital Post API from Digitaliseringsstyrelsen. The 429 error is shown in the history document. Upgrading to 2026.1 does not fix the issue for running SmartPostprocesses that were started in 2024.1, but new SmartPost processes that are started after the upgrade do not result in this error.

If the SmartPost message contains attachments with different file formats, for example, Word and PDF documents, the first PDF/UA validation of the original documents is successful, but the second PDF/UA validation that validates the merged document sometimes fails due to an Aspose issue. The merged document is generated but it is not PDF/UA compliant. A correction is pending Aspose at the time of this release.

You can click Approve in the task/smartmail to send the message with a non-PDF/UA compliant document or cancel the process and disable PDF/UA before you start a SmartPost process with attachments of mixed file formats.

When users try to forward a submission task by using the Forward button, the search for the contact to forward to fails when the there is a large number of contacts. The issue occurs when opening the Approve Submission task from Outlook when there is a large number of contacts on the list. The search works when opening the Approve Submission task from WorkZone Client.

If you have specified a default deadline for the Extended distribution process, it will be ignored when the process is started automatically as part of the distribution phase of the Ministerial and Parliamentary Question phase processes. Only the default deadline of the phase process applies.

When you upgrade to WorkZone 2025.0 or later, it is required that the MunicipalityIdentifierFilter parameter is filled in. The parameter cannot be empty despite the parameter listed as optional. The documentation has been revised accordingly. See Configure an Update municipality party service subprocess.

If you have entered a date in the CasesCreatedFrom parameter in the Case monitoring process parameters and the selected rule set includes a rule that starts the Update Municipality Party service subprocess, and you have turned on the AllowCaseMonitorOnUpdatedCase parameter in the Update Municipality Party service subprocess, you should only have this rule turned on in the rule set. If there are additional rules, the rules can be activated on cases that are from before the date specified in the CasesCreatedFrom parameter.

When a user takes over another user’s task or refreshes a task in WorkZone for Office while the task is locked by another user, the task is sometimes open for editing for both users.

When SmartPost is configured with the RemergePdfEnabled and AllowOfficeRemerge settings enabled in WorkZone Configurator, it is expected that SmartPost remerges recipient fields whenever contact information is changed, for example if a contact’s type or name is changed. However, SmartPost does not remerge the recipient merge fields and continues to send the message with the original recipient information in both the file name and merge fields.

If you upgrade from 2024.1 or earlier releases to 2026.1 and use WorkZone Mass Dispatch, you must complete all mass dispatch processes before you upgrade. Any active mass dispatch processes will not continue to run after the upgrade.

If a user deletes the case template, the default case, or any of the recipient cases that are specified in the Cases sheet sheet, while the Mass dispatch process is running, the messages that had these cases as recipient cases will not be sent. The Mass dispatch process completes successfully but no error message is shown to the user or in the history document.

To avoid this issue, do not delete recipient cases that are mapped to contacts in the Case sheet, the case template, or the default recipient case.

Mass dispatch processes fail if a contact that exists in the recipient list is deleted while the process is running.

Mass Dispatch does not send messages to recipients whose contact information is changed, for example if a contact’s type or name is changed. Messages are successfully sent to all other recipients.

When editing an existing authentication profile in WorkZone Configurator > Contact synchronization > Auth profiles tab, a validation error may appear and the profile cannot be saved.

Workaround: Delete the existing authentication profile and recreate the profile with the desired configuration instead of editing it.

The Update legal guardians and parental custodian setting in WorkZone Configurator > Services > Contact synchronization > CPR tab is part of an upcoming feature and is not supported in this release.

Workaround: Pull to refresh.

If you get the error message "404 Not Found" when trying to access cases and case documents through a client, portal, or form, it is because the WorkZone Citizen Access IDS enabled feature is not enabled in WorkZone Configurator. To enable it, go to Global > Feature settings > WorkZone Citizen Access.

If you get the error message "405 Internal Server Error " when trying to access cases and case documents through a client, portal, or form, it means that the access is denied due to invalid credentials, or you may not be authorized to access WorkZone cases and documents. This error will occur when an invalid token is passed.

The rendering of PDF documents fails if the WorkZone PDF Engine and WorkZone PDF Crawler configurations for header, footer, and watermark contain Japanese characters.

An incorrect error message is displayed: “The document may be password protected or corrupted. Check that the document is not corrupted and try again. You can view the errors in the preview pane”.

When generating a Classification Scheme report containing approximately 5000 entries or more, the report generation fails with a "504 Gateway timeout" error.

When using SmartPost with the LocalPDFMerge setting enabled and documents are sent as separate attachments, custom fonts are applied inconsistently.

• For recipient, custom fonts are applied correctly to attachments.
• For recipients, the letter and protected cover page are generated without custom fonts.
• For copy recipients, the letter, cover page, and attachments are all generated without custom fonts.

When custom fonts have been deleted from WorkZone Configurator or from the FontsCase case in WorkZone Client or WorkZone One, the fonts are still applied when generating PDF documents.

When adding fonts to the FontsCase case in WorkZone Client or WorkZone One, the filtering on allowed file extensions is incorrect. This makes it possible to add files that are not valid font files, for example a Word file. As a result, invalid files may appear on the Fonts tab in WorkZone Configurator.

To ensure only valid fonts are added, use WorkZone Configurator when uploading custom fonts.

If you get the error message "Could not load fonts" when uploading a custom font in WorkZone Configurator > PDF > Fonts, it is likely because the FontsCase case (the case used to store font files) could not be created.

To solve the issue, you can temporarily enable case creation for the REPORTS case group and create the required FontsCase case manually.

1. In WorkZone Configurator, go to Taxonomy > SJ-SYSTEM.

2. Edit the REPORTS case group, enable Case creation, and click Save.

3. In WorkZone Client, create a new standard case, and do as follows:

   • Name the case FontsCase.

   • In the Case group field, select the REPORTS case group.

   • Clear the Case handler and Responsible unit fields.

   • Ensure that the Write access field is set to CONFIGADM.

4. Click Save.

5. Return to WorkZone Configurator and disable Case creation for the REPORTS case group.

Previously rendered documents cannot be re-rendered using newly uploaded fonts.

When you run the command "Kmd.WZIE.exe --version", WorkZone Export/Import will display "1.0.0" as the version number.

This number, though displayed, is incorrect.

Workaround: To see the correct version number, go to the Kmd.WZIE.exe your file explorer, right-click the file and go to Properties > Details, where you can se the correct version number in the File version field.

When running an export/import job, the WorkZone Export/Import.exe program displays warning messages both in the console and in the log file. Warnings should only be logged in the log file.

Very large FK Claims (having more than 100 http://sts.kombit.dk/constraints/orgenhed/1 entries) are not supported and can lead to errors during data restriction filtering.

This issue only affects municipality customers.

On Ubuntu, documents cannot be opened in a desktop application from WorkZone Client or WorkZone One. Opening documents in a browser works as expected.

In WorkZone Process, documents cannot be opened from process tasks.