×

    Filters

    Didn't find what you were looking for?

    Extend your Search in Community

    Questions?

    We're always happy to help with questions you might have. Contact Us

Results

Receipts Overview

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    System Manager / DevOps  |  v5.1 & Higher This feature is related to v5.1 and higher.

Journey Manager provides form users with receipts that are an uneditable statement acknowledging the data they have submitted. Receipts are an essential part of the form submission process. Receipts are viewable PDF forms generated for all completed transactions and contain unique receipt numbers, which can be used to identify these transactions.

Receipts are primarily delivered by email. There are two options available to send receipts to users via email:

  • Email the PDF receipt directly to the user as an attachment.
  • Email a secure link that allows the user to directly download the PDF receipt.

Manager still supports downloading PDF receipts from form confirmation pages. However, this method is not recommended, due to performance scaling considerations.

Manager allows you to use the following orchestrations for receipt generation:

Manager generates user receipts in the background by using dedicated PDF receipt server nodes. This approach offers the following improvements:

  • PDF receipt generation can be performed on dedicated PDF receipt generation servers that can be scaled independently.
  • PDF receipts should only be generated by a background thread to improve server efficiently. This is the default option.

The receipt generation process consists of the sub-systems as shown below.

Each of the sub-system uses the following core global services:

  • The Generate Receipt service renders the PDF receipt.
  • The Dynamic PDF Receipt service generates a receipt as it appears on a form. This is the legacy receipt render service.
  • The Dynamic PDF Receipt 2 service provides more receipt customization options.  |  v17.10 This feature was introduced in v17.10.
  • The Process Receipt service submits the receipt in the background. This is achieved by using a load balancing mechanism that queues the receipt to a chosen node (in the above diagram, it's a Node 1, Node 2 or Node 3), which can then be processed by one or more threads, depending on the Manager configuration.

Next, learn how to configure receipts server node.