2024.3

Expanded SmartPost logging

You can now use the DebutOutput setting in the NgDP dispatcher to expand the SmartPost logging. If you turn on this setting, all requests to the NgDP service will be written to the workflow log.

See DebugOutput and Logging communication with the NgDP service.

Case activities

New ProcessName parameter in the StartProces and SendSmartPost activity effects

When you specify a process to be started by an activity effect, you can now use the process name instead of the process GUID. You can use the parameter if you want to run a case activity across different WorkZone environments, for example if you want to run the same case activity in both a test and a production environment. In this case, you cannot use the process GUID to identify the process to start because the GUID is unique to each environment.

See StartProcess and SendSmartPost activity effects.

SmartPost

Performance improvement

Sometimes the NgDP response times became slow on lookup in the EventLog and in the receipts, which affected other processes. The issue has been fixed in the NgDP dispatcher.

Repair invalid MeMo messages

The NgDP dispatcher has a new ReceiveMemoTransformation parameter that you can use if errors occur when saving incoming messages in WorkZone. You can specify an XSLT transformation that will be applied to a received MeMo messages before WorkZone processes the MeMo message. The XSLT transformation can repair invalid messages that WorkZone cannot receive.

See ReceiveMemoTransformation.

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 Map fields using a WZ_ODATA page.

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.