Delivery Channels Overview

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    System Manager / DevOps  |   21.05 This feature was updated in 21.05.

Journey Manager comes with several delivery channels to allow you to send user form submissions to a platform backend or a third-party system for processing. After a user submits a form, a delivery channel determines what happens to the submitted, abandoned or invalid form transactions.

A delivery channel transfers submitted user form details to a platform back-end or to a third-party system using one of the following mechanisms:

  1. PDF receipt - a readable copy of a form with user details.
  2. Form XML data - a machine-readable copy of form details in XMLXML (Extensible Markup Language) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. format.
  3. Attachment - a file which is a part of a form submission, for example, a copy of a driver license.

You can configure different delivery channels for:

  • An organization - you can configure the organization-wide delivery channels, which are used by all forms and form versions if their delivery channels are not configured.
  • A form level - you can configure a delivery channel, different to the organization's one, for individual forms. This gives you an extra flexibility to have different delivery flows for various forms within one organization.
  • A form version level - you can configure a delivery channel, different to the form's one, for individual form versions. This means you can implement requirements when each form version of a form should use various delivery channels.  |  21.05 This feature was introduced in 21.05..

Manager determines a delivery channel to use in this order:

  1. The form version's delivery channel
  2. The form's delivery channel, if the above is not set
  3. The organization's delivery channel, if the above is not set
  4. The Trash Can delivery process, if the above is not set

A delivery channel can have one of the following delivery methods, which you can customize to suit your specific requirements and your company policies.

Delivery Process

Note

This is the most widely used method and is recommended as a more customizable approach for an immediate and secure form of delivery.

Delivery Process invokes a service definition in Manager to perform delivery of submission details. This is typically a customizable Groovy delivery service.

Delivery is marked as complete if the service indicates that delivery was successful.

If delivery has not been completed (by default 72 hours after the form was submitted), escalation emails are sent out to all global and organization administrators in the Receive Delivery Escalation Alerts group.

Email

The Email method sends the submission details as attachments to one or more configured email addresses. This email can include a link to the submission attachments (if any were included by the user). In Manager, delivery is marked as complete as soon as the email is sent.

Email Secure

The Email Secure method differs from Email in that the email sent does not contain any submission details. Instead, it contains a link to a secure page in Manager where the submission details can be downloaded.

Delivery is marked complete only after a user has accessed this secure page and confirmed that the submission has been received.

If delivery has not been acknowledged within a certain period, which is 24 hours by default, reminder notifications are sent to the recipients defined in the delivery channel. This continues daily until a recipient acknowledges it.

If the delivery channel's Email Addresses field is left blank, a reminder is sent to all global and organization administrators in the Receive Delivery Escalation Alerts group.

If delivery remains unacknowledged (by default 72 hours after the form was submitted), escalation emails are sent out to all global and matching organization administrators in the Receive Delivery Escalations Alerts group.

REST Service

The REST Service method stores the submission details within Manager and offers a secure method of the enterprise retrieving these submission details, using a REST endpoint, when convenient.

For more information on REST service delivery, see the services guide.

Web Service

The Web Service method notifies your enterprise by making a web service call, using a pre-defined API. For more information, see the Manager Web Service API documentation.

Web services may be either defined as part of the Integration AgentTransact Integration Agent is a software appliance hosted inside the client organization’s data center, which receives form submission deliveries and file attachments from the Journey Manager server. or defined separately by a developer.

Delivery is marked as complete once the web service client confirms that it has received the submission.

If delivery has not been completed (by default 72 hours after the form was submitted), escalation emails are sent out to all global and organization administrators in the Receive Delivery Escalation Alerts group.

Trash Can

The Trash Can Delivery process is a do-nothing delivery process for form testing. This is usually configured as the default and won't be available in the organization configuration, but is available in the form configuration.

Next, learn how to create a delivery channel.