×

    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

Transaction Support Search

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

Manager allows you to search transactions based on wide range of criteria. This is useful when troubleshooting transactions.

To navigate to transaction support search, select Operations > Txn Support Search.

Transactions are shown page by page, with the maximum number of records per page configured via the user's preferences.

To filter or search the transactions by one or more criteria, specify the following settings and click Search:

  • Reference: a transaction ID or tracking code.
  • Form status.

    A form status can be one of the following:

    • Abandoned - transactions that have been abandoned by the user, or based on the data retention policy.
    • Assigned - a task which is waiting to be completed by a user.
    • Completed - transactions that have been successfully submitted and contain all required data.
    • Opened - transactions that have been started by a user. When a transaction is created by a user (by starting a new form), the initial form status is set to opened. This status will be changed once the user saves, cancels, or submits the transaction.
    • Saved - transactions that have been saved by the user or automatically by the system.
    • Submitted - transactions that have been submitted but may require additional information (attachments, payment, etc.). Once the required data is collected, the transaction status will change to Completed. This status is not common for Maestro forms as all information, such as attachments and payments, are collected prior to the user submitting the form. Most Maestro forms would skip the Submitted status and be marked as Completed after the form is submitted by the user. This is a legacy feature.
    • Expired - a form used by this transaction has expired and is no longer available.
  • Attachments.

    An attachment type can be one of the following:

    • Completed.
    • Optional.
    • Required.
  • Form Name - select a form name from the dropdown list.
  • User/Email - provide a user name or an email address.
  • Receipt.

    A receipt status can be one of the following:

    • Ready - a receipt is waiting to be allocated to a receipt generator.
    • In Progress - a receipt is in a receipt generator's queue.
    • Completed - a receipt has been generated.
    • Error - there is an error during receipt generation. A retry may fix it.
    • Error - No Data - there is no XML data available to generate a receipt.
  • Payment.

    A payment type can be one of the following:

    • Required.
    • Completed.
    • Error.
    • Pending.
  • Space.
  • Delivery.

    A delivery status can be one of the following:

    • Completed - a transaction has been successfully delivered, based on the configured delivery channel.
    • Undeliverable - a delivery is not possible. Check the error logs for further details of the error.
    • Not Ready - a transaction is not ready for delivery yet. This is the start state before a transaction has been completed by the user. Generally, the receipt render service will kick the transaction from this state to the Ready state when the receipt is rendered.
    • Not Required - a delivery is not required. It may be that this form is part of a collaboration job and the delivery is to be handled separately say as a consolidation of the transaction details from all the associated forms.
    • Ready - a transaction is ready to be delivered. A transaction will be marked as Ready until the delivery channel is processed, or it may remain marked as Ready if a delivery channel is not configured.
    • In Progress - a delivery has been started but is waiting to be completed.
    • Paused - a transaction delivery is paused. This transaction's status can be changed by some other means, for example by a Groovy Scheduled Task.
    • Error - a transaction delivery has failed and is waiting to be retried.
    • Sent Email - a secure email has been sent and now a transaction is waiting for the user to log in and process it.
    • Pending
  • Signature.

    A signature type can be one of the following:

    • Required.
    • Completed.
    • Completed - Deliver Manually.
    • Completed - Upload Scanned Copy.
  • Jobs.

    A job type can be one of the following:

    • Include - transactions associated with a job are included.
    • Exclude - transactions associated with a job are excluded.
  • Start Date.
  • End Date.
  • Email Verify.

    An email verification type can be one of the following:

    • Required.
    • Pending.
    • Completed.
    • Abandoned.
    • Error.
    • Error - No Data.
  • Tasks - to filter transactions related to tasks.

    A task type can be one of the following:

    • Include - transactions associated with a task are included.
    • Exclude - transactions associated with a task are excluded.

Click Clear to reset the search criteria.

You can perform one of the following actions for each selected transaction:

  • Click View to view transaction details.
  • Click View receipt to view the transaction PDF receipt.
  • Click Open Saved Form to open the saved form to allow an administrator with the Submission Save Edit permission to complete the form on behalf of the user.

You can perform several bulk operations on multiple selected transactions or a group of transactions.  |   v18.11 This feature was introduced in v18.11.

To perform a bulk operation:

  1. Select or filter transactions you need.
  2. Select all these transaction ID checkboxes or select the header checkbox to bulk select all filtered transactions.
  3. Apply one of the following actions:
  4. Click OK to accept the warning message that the transactions and all the data will be purged.
  5. Note

    Transactions relating to collaboration jobs are rejected and this is recorded in the event log entry. The user is warned this has happened.

  6. Check the event log entry to see if the purging was successful. An example of a successful message is: Submission 3090 was marked for immediate PII data purging by user john.smith@email.com.
Note

You must be an administrator with Submission Data Purge or Submission Edit privileges to perform these bulk operations.

Note

You can purge each transaction separately from the Transaction Status tab.  |   v18.11 This feature was introduced in v18.11.

Note

The System Event Publisher publishes submission PII purging events.  |   v18.11 This feature was introduced in v18.11.

Next, learn how to view form transactions.