Configure dispatchers

You can configure a number of dispatchers to handle different ways of sending messages. SmartPost is delivered with 6 default dispatchers.

You can modify the default dispatchers to match your organization's needs or you can create new dispatchers.

You can create dispatchers of the following types:

  • NgDP - The message is to the recipient's digital mailbox.
  • e-Boks - The message is sent to the recipient's digital mailbox in e-Boks.
  • Strålfors - The message is sent to Strålfors that handles the printing, enveloping, and handover to PostNord.
  • OneTooX – The message is sent to KMD Print Center that handles the printing, enveloping, and handover to PostNord.
  • Local print - The WorkZone user receives a smarttask that includes the SmartPost messages in PDF format. The user handles printing, enveloping, and sending of the messages manually.
  • Exchange - The message is sent to the recipient's email address.

Configure dispatchers

You create and configure dispatchers in WorkZone Configurator.

  1. In WorkZone Configurator, click Process
  2. Click Process dispatchers.
  3. Point to the dispatcher you want to use, for example NgDP, and click Edit. Change the values so that they match your organization, such as the name and description of the dispatcher, start and end date, and access rights. See Process Dispatchers in the WorkZone ConfiguratorAdministrator Guide for a description of the dispatcher settings.

    4. - Or -

    Click to create a new dispatcher. In the Select dispatcher dialog, select the type of dispatcher you want to create.

The dispatcher version number, which is displayed next to the dispatcher type, corresponds to the WorkZone Process release that you are running. When you upgrade WorkZone Process, a new version of the dispatcher is created with a version number that corresponds to the new release, and the previous dispatcher version automatically gets an end date. Ongoing SmartPost processes will continue to run using the previous version, and new SmartPost processes will use the new version of the dispatcher. On the Process dispatcher tab in WorkZone Configurator, all dispatcher versions are listed.

Note: It is not recommended to make changes to old dispatchers nor remove the end dates of old dispatchers

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 have been configured to use NgDP will be transferred to the corresponding NgDP dispatchers with relevant parameters. Ongoing SmartPost processes will continue to run using the e-Boks dispatcher, and new SmartPost processes will use the new NgDP dispatcher.

If you have existing e-Boks dispatchers that are not configured to use NgDP, you will need to recreate them after upgrading to 2024.0.

If you create a new dispatcher, remember to select NgDP (not e-Boks) in the Create dispatcher dialog.

  1. Click Save to save the changes you made to an existing dispatcher, or Create to create a new dispatcher.

The next step is to customize the default dispatcher parameters according to your organization, or if you created a new dispatcher, define the parameters from the start.

Edit dispatcher parameters

  1. Point to , and click Edit dispatcher parameters.
  2. Fill in the values for the parameters. The parameters are specific to the dispatcher type.
Note: The NgDP dispatcher cannot be used with WorkZone Mass Dispatch. If you use WorkZone Mass Dispatch, you must use the e-Boks dispatcher with NgDP settings. See Configure SmartPost to use NgDP on the 2023.3 Documentation Portal.
Name Default Description

URL

https://api.digitalpost.dk/apis/v1

The URL for the NgDP service.

Enter one of the URLs depending on whether the configuration is made for test or production.

Test system: https://api.test.digitalpost.dk/apis/v1

Production system: https://api.digitalpost.dk/apis/v1

CertificateThumbPrint

  

The thumbprint that identifies the NgDP certificate. The certificate must be a FOCES3 or a VOCES3 certificate with a correct CVR number.

MaxDocumentSize

7864320

The maximum size of an NgDP MeMo message in bytes. Messages that exceed this limit will not be sent. The default value is 7864320 bytes.

Refer to Digitaliser.dk for recommendations on document size.

SenderName

 

The name of the organization that sends the message.

SenderCvr

 

CVR number of the organization that is sending messages.

SystemGuid

 

The GUID of the NgDP Sender/Receiver system.

See Create a sender/receiver system.

ContactPointGuid

 

The GUID of your organization's NgDP reply point (mailbox for replies). You can see the GUID in the ID field on the Kontraktstruktur page in the NgDP portal.

To receive messages, it is required to set up a contact hierarchy in the NgDP portal.

See Configure contact points.

AuthorizationHeader

 

The GUID of the NgDP Sender/Receiver system.

The AuthorizationHeader is generated by the Administrativ Adgang portal when the sender/receiver system is defined.

Protocol

 

The NgDP protocol that is used by the Sender/Receiver system that is specified in the SystemGuid parameter. Set to REST_PULL or REST_PUSH depending on which protocol you use. By default, it set to REST_PULL.

RemotePushServiceEndPoint

 

The endpoint of the remote push service. It is only required if you use REST_PUSH protocol.

It points to a centralized push service. It must be the same push server that is configured to receive memos and receipts in the Administrativ Adgang portal.

UseCompression

 

Turn on this parameter if you want to compress the message before sending it.

By default this parameter is turned on.

About the NgDP dispatcher

The NgDP dispatcher supports sending and receiving messages using the PULL model. It is also possible to use the NgDP dispatcher with the PUSH model, but it is not recommended because both the infrastructure and the configuration is more complex than for the PUSH model.

Sending SmartPost messages using NgDP

When using NgDP to send messages, SmartPost converts outgoing messages to the MeMo format used by Digital Post before sending the messages.

The NgDP flow that is used to send messages from SmartPost is illustrated below:

For more information about MeMO, please refer to MeMo on the Agency for Digital Government's website.

Receiving messages in SmartPost using NgDP

When receiving messages from Digital Post, SmartPost converts the incoming MeMo messages to XML that SmartPost can retrieve.

The NgDP flow that is used to retrieve messages from Digital Post is illustrated below:

Name Default Description

SenderSystemId

 

The sender system identifier, which is retrieved during the configuration of the system in the e-Boks administration portal.

ReceiverSystemId

  

The receiver system identifier, which is retrieved during the configuration of the system in the e-Boks administration portal.

URL

https://rest.e-boks.dk/v1.svc

The URL for the e-Boks service.

Enter one of the URLs depending on whether the configuration is made for test or production.

Test system: https://demo-rest.e-boks.dk/v1.svc

Production system: https://rest.e-boks.dk/v1.svc

CertificateThumbPrint

  

The thumbprint that identifies the e-Boks certificate.

MaxDocumentSize

78643200

The maximum size of an e-Boks message in bytes. Messages that exceed this limit will not be sent to e-Boks. The default value is 78643200 (75 MB).

Note: e-Boks determines the maximum size. If e-Boks changes the size, you can change this configuration accordingly but due to encoding you must reduce the size set by e-Boks by 25%. For example, if the size set by e-Boks is 99,5 MB, you must set the MaxEBoksDocumentSize parameter to 99,5 MB * 75% = 75 MB.

ResponseThreshold

1800

Defines the maximum time that SmartPost expects that it takes e-Boks to process a message. Specify the threshold in seconds. The default value is 1800 seconds (30 minutes).

Note: The default value is most often used. In situations where the communication with e-Boks is slow, you can increase it.

SenderName

 

The name of the organization that sends the message.

ReceiverUrl

https://<host-or-database>/EboksPushService/api/MeddelelseV2

The URL for receiving messages using Digital Post 2. If the parameter is left empty, the default URL in the Url parameter is used.

DP2Url

https://demo-api.e-boks.com/oio/rest/srv.svc/2

The URL for receiving messages using Digital Post 2. If the parameter is left empty, the default URL in the Url parameter is used.

NgDpGuid

 

The GUID of the NgDP combined sender/receiver system. You can see the GUID in the NgDP Portal.

Note: This parameter is only relevant if you use the NgDP integration.

SenderCvr

 

CVR number of the organization that is sending messages.

Note: This parameter is only relevant if you use the NgDP integration.

NgDpContactPointGuid

 

The GUID of your organization's NgDP reply point (mailbox for replies). You can see the GUID in the ID field on the Kontraktstruktur page in the NgDP portal.

To receive messages, it is required to set up a contact hierarchy in the NgDP portal.

Note: This parameter is only relevant if you use the NgDP integration.

NgDpAuthorizationHeader

 

The AuthorizationHeader is generated by the Administrativ Adgang portal when the sender/receiver system is defined.

Note: This parameter is only relevant if you use the NgDP integration.

NgDpProtocol

 

Set to REST_PULL or REST_PUSH depending on which protocol you use.

Note: This parameter is only relevant if you use the NgDP integration.

RemotePushServiceEndPoint

 

Point to point to a centralized push service. It must be the same push server that is configured to receive memos and receipts in the Administrativ Adgang portal.

Note: This parameter is only relevant if you use the NgDP integration and set up the dispatcher to use the PUSH model.

For more information about configuring an e-Boks dispatcher to NgDP, See Configure SmartPost to use NgDP on the 2023.3 Documentation Portal.

 

Name Default Description

SenderSystemID

  

The system identifier, which is provided when configuring the system in the Strålfors administration portal. Either Strålfors or the person, who configures the portal for Strålfors, must provide this identifier.

Url

https://prodprint.

sconnect.dk/

fjernprint/1.0.0

The URL for the Strålfors Connect service. Depending on whether the configuration is made for test or production, enter one of the two URLs.

Test: https://testprint.sconnect.dk/fjernprint/1.0.0

Production: https://prodprint.sconnect.dk/fjernprint/1.0.0

CertificateThumbprint

  

Enter the thumbprint that identifies the Strålfors certificate.

ResponseThreshold

-1

Defines the maximum time that SmartPost expects that it takes to send a message to Strålfors. This value is used to calculate the deadline (supervised by the deadline monitor). The value is an integer, which (if positive) specifies the threshold in seconds.

Normally, the default setting is used.

If the communication with Strålfors is very slow, you can specify a high value.

MaxDocumentSize

375000000

The maximum number of bytes that a message for remote print can contain. Messages that exceed this limit will not be sent for remote print. The default value is 375000000 bytes (375 MB).

Note: Unless otherwise communicated, it is recommended to keep the values provided at the installation.

SenderName

KMD

The name of the company that is used in the postal address. The postal address is used when Strålfors produces the letters. The company name is taken from the address on which the authority will receive letters and returned mail.
Name Default Description
URL

https://privat.doc2mail.dk/

delivery/FileUploader.asmx

The URL for the OneTooX service.

Test:

https://test.doc2mail.dk/delivery/FileUploader.asmx

Production:

https://private.doc2mail.dk/delivery/FileUploader.asmx
SystemKey  

Enter the system key in clear text. Copy and paste the content of the system key file (PKE file) that you have received from KMD Printcenter in to this field.

If you work with WorkZone Configurator in Microsoft Internet Explorer and encounter problems with the system key not being pasted correctly, please open WorkZone Configurator in Google Chrome and try to paste the key again.
ResponseThreshold 600

The maximum time in seconds that a communication channel with OneTooX is open. Default is 600 seconds (10 minutes).
MaxDocumentSize 1000000 The maximum number of bytes that OneTooX will send. Numbers higher than 99600000 will be truncated.
SenderName   The name of the company.
Name Default Description
LocalPrintResponseThreshold 1800

Defines the maximum time that SmartPost expects that it takes for local print to process a message. This value is used to calculate the deadline (supervised by the deadline monitor). Specify the threshold in number of seconds. The default value is 1800 seconds (30 minutes).

The default value is most often used.
SenderName  

The name of the organization that sends the message.

The configuration of the Exchange dispatcher parameters depend on your Exchange configuration. See Configuration of Exchange parameters.

Name Description

ExchangeMailbox

The email address of the mailbox that emails will be sent from.

It is recommended to configure a No-Reply mailbox because recipients cannot reply to emails that are sent with the Exchange dispatcher.

ExchangeUserPassword

The password to the Exchange user's email address that is specified for the ExchangeMailbox parameter and used in the Resource Owner Password Credentials (ROPC) flow.

It is recommended to choose between this parameter and the ExchangeOauthClientSecret parameter.

ExchangeServerUri

The URL endpoint for the Exchange amsx service. For example, https://dc1.lmdom.ocal/EWS/Exchange.asmx.

If this parameter is not specified, autodiscover will be used to resolve the endpoint.

ExchangeUserName

Name of the user account used for accessing the Exchange service. If the parameter is left empty, the mailbox from the ExchangeMailbox parameter will be used.

ExchangeUserDomain

The domain for the Exchange user.

ExchangeOauthClientID

The OAuth2 Client ID that is used to access the mailbox in Exchange Online.

ExchangeOauthTenantID

The OAuth2 Tenant ID used to access the mailbox in Exchange Online.

ExchangeOauthClientSecret

The OAuth2 Client secret used to access the mailbox in Exchange Online. If set, the client credentials flow is used.

It is recommended to choose between setting this parameter and the ExchangeUserPassword parameter.

EmbeddedPrimaryDocument

Turn on this parameter if you want to show an image of the first page of the main document in the email body.

StoreMessages

Turn on this parameter if you want to save the sent email in the Sent folder of the mailbox that is specified in the ExhangeMailbox parameter.

Note that the SmartPost process will wait for the emails to be moved to the Sent folder before reporting that the dispatch has been successful.

Configuration of Exchange parameters

Depending on your Exchange configuration, fill in the following parameters in the Exchange dispatcher.

ExchangeMailbox

ExchangeOauthClientID

ExchangeOauthTenantID

ExchangeOauthClientSecret

ExchangeMailbox

ExchangeOauthClientID

ExchangeOauthTenantID

ExchangeOauthClientSecret

ExchangeUserPassword

ExchangeMailbox

ExchangeServerUri

ExchangeUserPassword (The password for the account specified in the ExchangeMailbox parameter).

ExchangeMailbox

ExchangeServerUri

ExchangeUserName

ExchangeUserDomain

ExchangeUserPassword (the password of the account specified in the ExchangeDomain\ExchangeUserName parameters).

See Command line configuration in the WorkZone Installation Guide.