TRANSACTION MANAGEMENT SYSTEM

• US 20100312772A1
• Filed: 07/29/2010
• Published: 12/09/2010
• Est. Priority Date: 09/28/2000
• Status: Active Grant

• Current Assignee: Ip Ot Sub Ulc
• Original Assignee: Open TEXT SA (Open Text Corporation)
• Inventors: MacLean, John M.
• Granted Patent: US 8,543,537 B2
• Time in Patent Office: Days
• US Class Current: 707/758
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The systems and methods described herein relate to a system for documenting transactions. A filter is provided that captures content associated with transactions. The filter may be configured to start and stop the capture at predetermined times, and may be further configured to specify what content is to be captured during a transaction. The system may store any documents or data associated with a transaction, including dynamic content and user selections and inputs. A document repository may be provided for storing unstructured data representing data, text, forms, and so forth presented to a party during a transaction. A viewer may be provided for displaying data stored in the document repository.

Claims

1. A transaction management system comprising:

a server that hosts a transaction;

a network;

a client connected in a communicating relationship with the server over the network, and the client participating in the transaction hosted by the server;

a filter operating on the server to capture data associated with the transaction, wherein the data associated with the transaction comprises;

multiple requests by the client for web pages as part of the transaction;

HTML objects associated with the requested web page and objects referenced by the HTML objects returned to the client in response to the requests;

a repository accessible by the server, wherein the filter stores the data associated with the transaction in the repository indexed by one or more transaction attributes.

2. The transaction management system of claim 1, wherein the transaction attributes comprise one or more of a transaction type, a time, a date, a transaction identification number, a transaction party.

3. The transaction management system of claim 2, wherein the set of objects referenced by the first HTML object comprise at least some external content.

4. The transaction management system of claim 2, wherein the filter is responsive to a first trigger to begin capturing data associated with the transaction and responsive to a second trigger to stop capturing data associated with the transaction.

5. The transaction management system of claim 2, wherein the user input comprises activation of a user control in the first page.

6. The transaction management system of claim 1, wherein storing the data associated with the transaction in the repository further comprises storing the requests, the HTML objects and objects referenced by the first HTML objects in a hierarchical system of folders.

7. The transaction management system of claim 1, wherein storing the data associated with the transaction in the repository further comprises storing the requests, the HTML objects and objects referenced by the first HTML objects in sequential order.

8. The transaction management system of claim 1, wherein the filter captures data associated with the transaction over multiple sessions.

9. A method comprising:

providing a system comprising a server running a server application to host a transaction and a repository accessible by the server, a filter to capture information sent to or received by the server and one or more additional computers configured to store unstructured data in the repository;

capturing data associated with the transaction at the server, wherein the data associated with the transaction comprises;

multiple requests by the client for web pages as part of the transaction;

HTML objects associated with the requested web page and objects referenced by the HTML objects returned to the client in response to the requests;

storing the data associated with the transaction in the repository;

storing additional unstructured data associated with the transaction in the repository, wherein the data and unstructured data associated with the transaction are stored with one or more transaction attributes.

10. The method of claim 9, wherein the transaction attributes comprise one or more of a transaction type, a time, a date, a transaction identification number, a transaction party.

11. The method of claim 9, wherein the unstructured data associated with the transaction comprises a facsimile sent or received as part of the transaction.

12. The method of claim 9, wherein the unstructured data associated with the transaction comprises an electronic mail sent or received as part of the transaction.

13. The method of claim 9, wherein the at least one of the set of objects referenced by the HTML objects comprises at least some external content.

14. The method of claim 9, wherein storing the data and unstructured data associated with the transaction comprises storing the data and unstructured data associated with the transaction in a hierarchical system of folders.

15. The method of claim 9, wherein storing the data and unstructured data associated with the transaction comprises storing the data and unstructured data associated with the transaction in sequential order.

16. The method of claim 9, wherein the filter captures the data associated with the transaction over multiple sessions.

17. The method of claim 9, further comprising providing a viewer configured to present all the data and unstructured data associated with the transaction to a user in sequential order.

18. The method of claim 17, wherein the viewer is further configured to search documents in the repository in the documents'"'"' native format.

19. A computer program product comprising a non-transitory computer readable medium storing a set of computer instructions, the computer instructions executable to:

capture data associated with a transaction hosted by a server, wherein the data associated with the transaction is captured at the server and comprises;

multiple requests by the client for web pages as part of the transaction;

HTML objects associated with the requested web page and objects referenced by the HTML objects returned to the client in response to the requests;

store the data associated with the transaction in the repository indexed by one or more transaction attributes;

store unstructured data associated with the transaction from one or more additional document sources in the repository indexed by the one or more transaction attributes.

20. The computer program product of claim 19, wherein the unstructured data comprises one or more of an electronic mail, a facsimile or a scanned document.

21. The computer program product of claim 19, further comprising computer instructions executable to:

search the repository based on the one or more transaction attributes;

retrieve the data and unstructured data associated with the transaction from the repository;

present the data and unstructured data associated with the transaction to a user in sequential order.