Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | All versions This feature is related to all versions.
Manager lets you identify form transactions by using a receipt number or a tracking code. A receipt number is used to identify a submitted transaction in Manager. A tracking code is a unique alphanumerical code that is generated when a transaction is created and is used to track this transaction that is yet to be submitted. Tracking codes are generally shorter than receipt numbers and by their nature are identified before a receipt number is generated. Manager allows you to use the same value for both the receipt number and tracking code of a submission.
Tracking codes are generated using the TrackingCodeBuilder
class and are 29 characters long. They are stored in a database table, called tracking_number
, to ensure every new tracking code is unique. The table is never purged to make sure the codes are unique for as long as the Manager server runs. In the unlikely event of the table growing too large so it needs to be purged, the uniqueness of tracking codes can be compromised. In reality, it won't happen because transactions are not that long-lived and once a transaction is purged, that tracking code is technically available and can be reused.
Check Top Table Sizes to see a number of records that the tracking_number
table has. In some installations, this table is not listed.
Tracking codes and receipt numbers are only unique to the environment and hence may be duplicated across systems, such as Prod, Dev, UAT etc. If you need a really unique key, you should use a submission key (submitKey
) which is unique globally. Alternatively, you can prefix or suffix a tracking code with some other piece of unique information, such as day, month and year time stamp.
To configure a form’s tracking code or receipt number, follow these steps:
Next, learn how to configure receipt headers and footers.