Multi-provider forms processing system with retry upon failure
First Claim
1. A computer-implemented method for monitoring and reprocessing a transaction, the method comprising:
- receiving a compound document at a paper-like forms server, the compound document including an image and a transaction template including a description of at least one transaction;
determining, with a processor, the transaction to perform on the compound document based on the transaction template;
transmitting the compound document to a first service provider for performing the transaction on the compound document;
creating a log entry indicating performance of the transaction;
determining whether the transaction failed and what caused the transaction to fail;
retrying to perform the transaction if the transaction failed, the retrying comprising;
modifying criteria for selecting an alternate service provider based on what caused the transaction to fail;
identifying the alternate service provider based on the modified criteria; and
sending at least a portion of the compound document to the alternate service provider for performing the transaction on the compound document; and
updating log information for the failure of the transaction and retrying of the transaction.
1 Assignment
0 Petitions
Accused Products
Abstract
A multi-provider forms processing system with retry upon failure comprises: a plurality of portable computing devices, a plurality of service providers and a paper-like forms server coupled by a network. The paper-like forms server performs the scheduling, routing, logging, verification and billing for the paper-like processing of compound documents. The paper-like forms server comprises a central schedule, a retry module and a billing module. The multi-provider forms processing system is advantageous because it monitors for failure of transactions, automatically issues a retry or replacement transactions and adjusts the billing for the failed transaction. In particular, the central scheduler tracks and determines when transaction failures occur, and based on these failures revises the billing to users and credits to service providers. The central scheduler also monitors the logs for completion as well as restarts, attempts, failure, reworked and re-performed transaction steps and modifies the bills accordingly.
-
Citations
20 Claims
-
1. A computer-implemented method for monitoring and reprocessing a transaction, the method comprising:
-
receiving a compound document at a paper-like forms server, the compound document including an image and a transaction template including a description of at least one transaction; determining, with a processor, the transaction to perform on the compound document based on the transaction template; transmitting the compound document to a first service provider for performing the transaction on the compound document; creating a log entry indicating performance of the transaction; determining whether the transaction failed and what caused the transaction to fail; retrying to perform the transaction if the transaction failed, the retrying comprising; modifying criteria for selecting an alternate service provider based on what caused the transaction to fail; identifying the alternate service provider based on the modified criteria; and sending at least a portion of the compound document to the alternate service provider for performing the transaction on the compound document; and updating log information for the failure of the transaction and retrying of the transaction. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A non-transitory computer program product comprising a computer useable medium including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:
-
receive a compound document at a paper-like forms server, the compound document including an image and a transaction template including a description of at least one transaction; determine the transaction to perform on the compound document based on the transaction template; transmit the compound document to a first service provider for performing the transaction on the compound document; create a log entry indicating performance of the transaction; determine whether the transaction failed and what caused the transaction to fail; retry to perform the transaction if the transaction failed, the retry comprising; modifying criteria for selecting an alternate service provider based on what caused the transaction to fail; identify the alternate service provider based on the modified criteria; and send at least a portion of the compound document to the alternate service provider for performing the transaction on the compound document; and update log information for the failure of the transaction and retrying of the transaction. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20)
-
Specification