What's new

New features and functionality in WorkZone Process

2024.0

Monitor cases that are locked by inactive processes

Prerequisite: This functionality is only available in WorkZone Process HF03.

The process monitor also monitors cases that are locked by inactive processes. The process monitor service workflow can monitor if processes fail and release cases that are locked by the SJPROCESSUSER even though the process is no longer active. In such situations the process monitor removes the write access codes from the case and thereby also from the documents that are connected to the cases and inherits the write access code, which makes it possible to work with the case and its documents in WorkZone again.

See Process Monitor.

Create a Process monitor service workflow

New service subprocess: Update municipality party

Update municipality party is a new service subprocess that you can enable to ensure that a party on a case is always synchronized to match the value of the AddressKey/Municipality property of a party role that you specify. An example where this service subprocess can be useful could be in instances where you have a case with a primary case party with the Citizen role and a case party with the Municipality role. When the citizen changes municipality of residence, it is important that the municipality party on the case is also automatically updated. See Configure an Update municipality party service subprocess.

New service workflow parameters

New service workflow parameters have been introduced that you can use to optimize performance of the Interact connector and Case monitoring service workflows.

Interact connector

Two new parameters have been added to the service workflow. A FetchInterval parameter that you can use to set the interval between fetching and processing data from Interact forms, and a RunParallel parameter that you can turn on, if you want the service workflow to run in parallel on all available servers with an agent profile.

See Configure an Interact connector service workflow.

Case monitoring

Two new parameters have been added to the service workflow. A FetchInterval parameter has been added to the Case monitoring service workflow. You can use this parameter to set the interval between identifying new cases and starting processes or case activities, and a RunParallel parameter that you can turn on, if you want the service workflow to run in parallel on all available servers with an agent profile.

See Configure a Case monitoring service workflow.

Enhanced Interact field mapping

The new way of mapping Interact form data to WorkZone data using a custom XML format (introduced with the 2023.3 release) has been enhanced.

The documentation has been update with a new topic that describes how to map fields using the WZ_ODATA page in Interact. You will also find a sample XSLT transformation and a sample XSD schema in this topic that you can copy and customize.

See Field mapping in Interact forms to WorkZone data, Map fields using a WZ_ODATA page, and Sample XSLT transformation and XSD schema.

SmartPost: New NgDP dispatcher

SmartPost now includes a new NgDP dispatcher.

When WorkZone is upgraded to 2024.0, new NgDP dispatchers will be created instead of new versions of e-Boks dispatchers. The configuration of existing e-Boks dispatchers that is set up to use NgDP will be transferred to the corresponding NgDP dispatchers with relevant parameters. See e-Boks dispatcher upgrade to NgDP dispatcher.

See Configure dispatchers for a description of the NgDP dispatcher parameters.

Note that in this release you cannot use the NgDP dispatcher with WorkZone Mass Dispatch. You must use the e-Boks dispatcher. See Configure SmartPost to use NgDP on the 2023.3 Documentatation Portal.

Case activities

Activity types are now called activity effects to reflect the terminology change in the DCR Portal.

This release includes a number of new and updated activity effects.

New CreateEntity activity effect

Using the new CreateEntity activity effect, you can create new WorkZone entities, such as cases, documents, contacts, or custom types.

See CreateEntity.

New MergeDocument activity effect

With the new MergeDocument activity effect, you can merge values from WorkZone with merge fields in a document.

See MergeDocument.

SendSmartPost activity effect supports PDF/UA

SendSmartPost now uses the ValidatePDFUA setting in the SmartPost process parameters in WorkZone Configurator. If this setting is turned on, letters and attachments are validated for PDF/UA compliance.

Apply access codes

The SetValue, CreateEntity, and UpdateEntitities activity effects now supports applying access codes, which makes it possible to control access to information in WorkZone when you update information automatically by using case activities. You can, for example, fetch the access code from one entity and set this access on another entity, for example on cases.

See Apply access codes.

Reference values from DCR activities

Some activity effects return values such as IDs of new cases, documents, contacts, process instance IDs, or values from properties. You can now reference these values in other activities by using the syntax {DCR.ID}, where DCR is a prefix and ID is the ID of the activity effect which value you want to refer to.

See Reference values from DCR activities.

Query options

You can now use OData clauses such as $top, $ordeby, $count, $skip, and $Aggregate in a new QueryOptions parameter in the GetValue and ValidateEntities activity effects.

See Use query options.

Flexible mapping of Interact form data to WorkZone data

The Interact connector service workflow now supports that you can create field mappings by using a custom XSLT transformation. You can create more advanced mappings in a custom XML format compared to what the WorkZoneInteract add-in offers. You can, for example, handle multiple contacts, contact roles, and that a contact has more than one address. An XSLT transformation is required for the Interact connector service workflow to retrieve Interact data from a custom XML format.

To support both the use of the existing Interact add-in and the custom XML format, the Interact connector service workflow has three new parameters:

  • UseLegacyFormat

  • CustomTransformationRecordId

  • CustomSchemaRecordId

See Create and configure an Interact connector service workflow for a description of the parameters.

Mailbox monitor

It is now possible to set a default processing status on documents that are created by the Mailbox monitor service workflow. A new InitialDocumentProcessingStatus parameter has been added to the Mailbox monitor parameters.

See InitialDocumentProcessingStatus.

SmartPost

A new ValidatePDFUA parameter has been added to the SmartPost process parameters.

SmartPost

The SmartPost process has been extended with a new Exchange dispatcher that can be used to send documents by email.

See Configure dispatchers.

Case activities

DCR Engine

WorkZone now supports DCR Engine 4.3.0. For more information about new features in the 4.3.0 release, please refer to Release notes in the documentation from DCR Solutions.

GetValue activity type

You can now use the GetValue activity type to fetch values from custom types.

Advanced submission process

The STEPSUBMISSION access code is no longer required to access the Advanced submission process.

Interact connector

AddressType_value is no longer a mandatory field.

See Mandatory fields and dependencies and What's new in the WorkZone Client User Guide.

No new features in this release.

Next generation Digital Post (NgDP)

The NgDP integration has been adapted to reflect the latest changes to NgDP released by the Agency for Digitisation. The WorkZoneNgDP integration can be used in production when the Agency for Digitisation releases NgDP November 30, 2021.

The WorkZoneNgDP integration now also supports the PULL model.

The NgDP documentation has been updated accordingly. See Configure SmartPost to use NgDP in this guide and Install and configure WorkZone e-Boks Push Service in the WorkZone Installation Guide.

If you need help with the implementation of the NgDP integration, KMD WorkZone Consulting offers NgDP relevant services. Please contact your Service Delivery Manager for more information.

Case activities

Graphs are now called processes in the DCR Design Portal. The case activities topics in this guide have been revised according to the name change.

See About case activities .

Service workflow check when started

When a service workflow is started and an identical service workflow is already running or scheduled to start on any WorkZone agent server, the newly started workflow will be canceled in favor of the already running or already scheduled workflow.

Previously, it was possible to start the same service workflow multiple times, for example starting multiple e-Boks Handler service workflows would result in the same e-Boks message being received and saved multiple times.

e-Boks dispatcher ignores incoming messages that already exist

If an already received e-Boks messages is received again, the incoming e-Boks message will be ignored in order to avoid duplicates of identical e-Boks messages in WorkZone.

Previously, duplicates of identical e-Boks messages could occur due to inconsistent checking of incoming messages.

Next generation Digital Post (NgDP) - Experimental

The WorkZone integration has been adjusted and improved to align with the latest changes to NgDP. A new parameter NgDpAuthorizationHeader has been added to the e-Boks dispatcher configuration in WorkZone Configurator and the NgDP documentation has been updated.

See Configure next generation Digital Post (NgDP).

The integration makes it possible to test NgDP with WorkZone. KMDWorkZone Consulting offers NgDP relevant services. Please contact your Service Delivery Manager for more information.

As the Agency for Digitisation is still developing NgDP, and therefore the WorkZone integration will be continuously adjusted and improved accordingly. The improvements to the integration will be part of coming WorkZone releases.

DCR Processes/Case Activity enhancements

Maximum number of activity loops

If there are more than 50 automatic activities executed in a loop or just sequentially in the DCR process, an error will be triggered at the 51st activity with the error message: "Maximum number of loop iterations of graph execution reached. Loops or automatic execution flows with more than 50 executions are not allowed."

This restriction helps prevent endless loops which can result in Case Activity processes remaining locked in the Running status.

The Running status and idle processes

Whenever an activity is executed, the DCR process status will be changed to Running. If a DCR process remains in the Running status for more than 5 minutes without signs of active activities, the process will be considered to be idle, which enables users and the WorkZone system to perform operations on the process. A DCR process will be considered idle, even in the case of serious long-present network errors which could result in a Case Activity process not being able to switch back to Persisted status.

Microsoft

Microsoft Graph support for service workflows using Microsoft Exchange Online

The Mailbox monitoring, Process monitoring, and F2 requisition handler service workflows now use Microsoft Graph. With the Microsoft Graph library, the service workflows can be used with Exchange Online. Three new cloud service workflows are now available in WorkZone Configurator:

  • Cloud Mailbox monitoring
  • Cloud Process monitoring
  • Cloud F2 requisition handler

Compared to the on-premises versions of the service workflows, these workflows contain the following new Exchange Online specific parameters:

  • ExchangeOAuthClientId
  • ExchangeOAuthTenantId
  • ExchangePassword
  • ExchangeOAuthClientSecret

See:

Configure a Mailbox Monitor service workflow

Process Monitor

Install and configure F2 integration

Next generation Digital Post (NgDP) - Experimental

WorkZone now supports next generation Digital Post (NgDP) in an experimental version. WorkZone supports sending and receiving through NgDP as a new channel for SmartPost. As this is a regulatory change, this release will be followed by hotfixes to previous WorkZone release where relevant. The new NgDP feature makes it possible to test the new Digital Post with WorkZone. KMD WorkZone Consulting offers NgDP relevant services. Please contact your Service Delivery Manager for more information.

The Agency for Digitisation (Digitaliseringsstyrelsen) is still developing NgDP, and therefore the WorkZone integration will be continuously adjusted and improved accordingly. The improvements to the integration will be part of coming WorkZone releases.

See Configure SmartPost to use next generation Digital Post (NgDP).

No new features in this release.