# US 8,543,537 B2 · Transaction management system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,543,537 B2 - Document ID: US8543537B2 - Status: Granted - Kind: B2 - Application number: 12/846,463 - Filed: 2010-07-29 - Published: 2010-12-09 - Granted: 2013-09-24 - Earliest claimed: 2000-09-28 - Assignees: Open Text Corporation - Applicants: John M. MacLean - Inventors: John M. MacLean - Web page: https://patentgrep.com/patent/US8543537B2 ## CPC - G06F 16/2379: {Updates performed during online database operations; commit processing} - G06F 16/24565: {Triggers; Constraints} - G06F 16/951: Indexing; Web crawling techniques - G06F 16/953: Querying, e.g. by the use of web search engines - G06F 16/954: Navigation, e.g. using categorised browsing - G06Q 10/087: Inventory or stock management, e.g. order filling, procurement or balancing against orders - G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction} - G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes - H04L 43/00: Arrangements for monitoring or testing data switching networks - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)} - H04L 69/329: in the application layer [OSI layer 7] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 1 A transaction management system comprising: a server that hosts an electronic commerce transaction over a network, the server having a processor and a set of computer instructions executable by the processor to communicate with a client connected in a communicating relationship with the server over the network, the client participating in the electronic commerce transaction hosted by the server; a user interface for customizing one or more filters; a filter configured using the user interface and operating on the server to capture data associated with the electronic commerce transaction in response to a trigger, wherein the filter is configured via the user interface to control which of the data associated with the electronic commerce transaction is or is not to be captured, and wherein the data associated with the electronic commerce transaction comprises: multiple requests by the client for web pages as part of the electronic commerce transaction; user selections and inputs made during the electronic commerce transaction; first objects associated with the requested web pages; and second objects referenced by the first objects returned to the client in response to the multiple requests; and a repository accessible by the server, wherein the filter stores the data associated with the electronic commerce transaction in the repository indexed by one or more transaction attributes. ### Claim 2 (depends on 1) The transaction management system of claim 1, wherein the one or more transaction attributes comprise one or more of a transaction type, a time, a date, a transaction identification number, a transaction party. ### Claim 3 (depends on 2) The transaction management system of claim 2, wherein the second objects referenced by the first objects comprise at least some external content. ### Claim 4 (depends on 2) The transaction management system of claim 2, wherein the filter is responsive to a first trigger to begin capturing data associated with the electronic commerce transaction and responsive to a second trigger to stop capturing data associated with the electronic commerce transaction. ### Claim 5 (depends on 1) The transaction management system of claim 1, wherein the filter is selected based on an event. ### Claim 6 (depends on 1) The transaction management system of claim 1, wherein storing the data associated with the electronic commerce transaction in the repository further comprises storing the multiple requests, the first objects, and the second objects referenced by the first objects in a hierarchical system of folders. ### Claim 7 (depends on 1) The transaction management system of claim 1, wherein storing the data associated with the electronic commerce transaction in the repository further comprises storing the multiple requests, the first objects, and the second objects referenced by the first objects in a sequential order. ### Claim 8 (depends on 1) The transaction management system of claim 1, wherein the filter captures the data associated with the electronic commerce transaction over multiple sessions. ### Claim 9 A method comprising: providing a user interface for customizing one or more filters; capturing, by a filter configured using the user interface, data associated with an electronic commerce transaction hosted by a server, wherein the data associated with the electronic commerce transaction is captured at the server in response to a trigger, wherein the filter is configured via the user interface to control which of the data associated with the electronic commerce transaction is or is not to be captured, and wherein the data associated with the electronic commerce transaction comprises: multiple requests by the client for web pages as part of the electronic commerce transaction; user selections and inputs made during the electronic commerce transaction; first objects associated with the requested web pages; and second objects referenced by the first objects returned to the client in response to the multiple requests; storing the data associated with the electronic commerce transaction in the repository; and storing any unstructured data associated with the electronic commerce transaction in the repository, wherein the data and the unstructured data associated with the electronic commerce transaction are stored with one or more transaction attributes. ### Claim 10 (depends on 9) The method of claim 9, wherein the one or more transaction attributes comprise one or more of a transaction type, a time, a date, a transaction identification number, a transaction party. ### Claim 11 (depends on 9) The method of claim 9, wherein the unstructured data associated with the electronic commerce transaction comprises a facsimile sent or received as part of the electronic commerce transaction. ### Claim 12 (depends on 9) The method of claim 9, wherein the unstructured data associated with the electronic commerce transaction comprises an electronic mail sent or received as part of the electronic commerce transaction. ### Claim 13 (depends on 9) The method of claim 9, wherein at least one of the second objects referenced by the first objects comprises at least some external content. ### Claim 14 (depends on 9) The method of claim 9, wherein storing the data and the unstructured data associated with the electronic commerce transaction comprises storing the data and the unstructured data associated with the electronic commerce transaction in a hierarchical system of folders. ### Claim 15 (depends on 9) The method of claim 9, wherein storing the data and the unstructured data associated with the electronic commerce transaction comprises storing the data and the unstructured data associated with the electronic commerce transaction in a sequential order. ### Claim 16 (depends on 9) The method of claim 9, wherein the filter captures the data associated with the electronic commerce transaction over multiple sessions. ### Claim 17 (depends on 9) The method of claim 9, further comprising providing a viewer configured to present all the data and the unstructured data associated with the electronic commerce transaction to a user in a sequential order. ### Claim 18 (depends on 9) The method of claim 9, wherein the filter is selected based on an event. ### Claim 19 A computer program product comprising a non-transitory computer readable medium storing a set of computer instructions, the computer instructions executable to: provide a user interface for customizing one or more filters; capture, by a filter configured using the user interface, data associated with an electronic commerce transaction hosted by a server, wherein the data associated with the electronic commerce transaction is captured at the server in response to a trigger, wherein the filter is configured via the user interface to control which of the data associated with the electronic commerce transaction is or is not to be captured, and wherein the data associated with the electronic commerce transaction comprises: multiple requests by the client for web pages as part of the electronic commerce transaction; user selections and inputs made during the electronic commerce transaction; first objects associated with the requested web pages; and second objects referenced by the first objects returned to the client in response to the multiple requests; store the data associated with the electronic commerce transaction in a repository indexed by one or more transaction attributes; and store any unstructured data associated with the electronic commerce transaction from one or more document sources in the repository indexed by the one or more transaction attributes. ### Claim 20 (depends on 19) 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. ### Claim 21 (depends on 19) 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 the unstructured data associated with the electronic commerce transaction from the repository; present the data and the unstructured data associated with the electronic commerce transaction to a user in a sequential order.