What are you looking for?

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

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

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

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

Manager Topics

View Transaction History

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

Manager allows you to view transaction history to see user's interaction with a form. You can use this tool to troubleshoot, analyze, and audit transactions.

Note

Manager allows you to check transaction trends and analyze user behavior.

When a transaction is finished, Manager writes all relevant submission information, such as final status, form name, time to submit, and browser information into a transaction history table. This table does not contain any PIIPersonally identifiable information (PII) is any data that could potentially identify a specific individual. Any information that can be used to distinguish one person from another and can be used for de-anonymizing anonymous data can be considered PII. data (aside from an email address, which is used for security auditing purposes).

To view transaction history:

  1. Select Operations > Form Transactions.
  2. Locate a transaction and click View.
  3. Select the History tab to see all transaction versions.
  4. Check the following information for each transaction:
    • Form Status.
    • Time of a transaction
    • Version of a transaction. A new version of a transaction is created each time a user opens and saves a form until the form is submitted.
    • The space associated with the selected transaction.
    • The time to submit, which is a time it took for a user to fill in a form and submit it.
    • User
    • The device used to access a form from.
    • The user's OS / browser of the user that created a transaction. This is used for auditing purposes.
    • The IP address of the user that created a transaction. This is used for auditing purposes.
    • Form Request Key, which is a unique identifier of a transaction.
  5. Click Form Session to check details about the transaction in Form Request Details.
  6. Click View XML History to download a copy of the submitted XML data. This option is commonly available to Composer Forms.
  7. Note

    Only available if the Log Submission History XML checkbox is selected.

  8. Click View XML Diff to view the difference between the submitted XML data and the XML data of the blank form with no input from the user. This option is commonly available to Composer Forms.
  9. Note

    Only available if the Log Submission History XML checkbox is selected.

  10. Click Close.

Next, learn how to track submissions.

Feedback

Did this topic provide the information you need or leave you wanting to know more? Is there some way we can make this topic better? Let us know how we can improve this documentation.

Contact Us

Community

Our Community is a dynamic, user-driven source of information that provides a home for sharing Journey platform knowledge where you can ask questions and get answers quickly.

Explore Community

Support

Temenos is committed to supporting our customers with Journey platform solutions installed in the cloud or on premise. Learn more about our Customer Care Team, and its policies, procedures, and processes.

Learn More