Method of and system for determining if an electronic signature is necessary in order to commit a transaction to a database

• US 7,966,493 B2
• Filed: 12/08/2003
• Issued: 06/21/2011
• Est. Priority Date: 11/18/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Gupta, Manish, Puri, Srinivasulu, Durgada, Savita, Fisher, Mark, Akella, Ravindra, Stearns, William, Saleeb, Hany
• Primary Examiner(s): CERVETTI, DAVID GARCIA
• Application Number:
  US10/731,623
• Publication Number:
  US 20050108537A1
• Time in Patent Office: 2,752 Days
• Field of Search: 713/151, 713/176
• US Class Current: 713/176
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures

Abstract

A method of and system for intercepting a transaction instantiated by a database application to determine if an electronic signature is necessary to commit the transaction to the database is disclosed. In one embodiment the method comprises calling an application program interface to raise an event in response to a triggering action generated by the database application; initiating a workflow process that executes a rule to determine if an electronic signature is required to approve the transaction; and if execution of the rule results in a determination that an electronic signature is required for the transaction, instantiating a signature collection process. Some embodiments further comprise obtaining an electronic signature in response to the signature collection process and thereafter, verifying the electronic signature and updating a filed of the electronic record to indicate a valid signature was collected if the electronic signature is verified.

Claims

1. A method of intercepting a transaction instantiated by a database application to determine if an electronic signature is necessary to commit the transaction to the database, the method comprising:

in response to a triggering action generated by the database application, calling an application program interface with one or more processors associated with one or more computer systems to raise an event indicative of a signature collection process;

initiating a workflow process defined by the event with the one or more processors associated with one or more computer systems that initiates the transaction instantiated by the database application with the database without committing the initiated transaction to the database;

executing a rule specified by the workflow process with the one or more processors associated with one or more computer systems to determine if an electronic signature is required to approve the transaction; and

if execution of the rule results in a determination that an electronic signature is required for the initiated transaction to be committed to the database, instantiating the signature collection process with the one or more processors associated with one or more computer systems.

2. The method of claim 1 wherein calling the application program interface comprises calling the application program interface based on an event name and an event id.

3. The method of claim 1 wherein instantiating the signature collection process comprises instantiating either a synchronous collection process or an asynchronous collection process.

4. The method of claim 3 wherein calling the application program interface comprises calling the application program interface based on an event name, an event id and an indication of whether the signature collection process is a synchronous process or an asynchronous process.

5. The method of claim 1 wherein the workflow process generates an electronic record that captures data associated with the initiated transaction prior to the initiated transaction being committed to the database.

6. The method of claim 5 wherein the electronic record comprises unstructured data.

7. The method of claim 6 wherein the unstructured data comprises extensible markup language data stored in character large object (CLOB) format.

8. The method of claim 7 wherein the extensible markup language data comprises a first well-formed extensible markup language document that comprises extensible markup language fields generated from a mapping to fields in a database and a second well-formed extensible markup language document that comprises the electronic record as it is displayed to a user during the signature collection process.

9. The method of claim 5 further comprising:

obtaining an electronic signature in response to the signature collection process; and

thereafter, verifying the electronic signature and, if the electronic signature is verified, updating a field of the electronic record to indicate a valid signature was received.

10. The method of claim 9 further comprising committing the initiated transaction to the database if the electronic signature is verified.

11. A computer system comprising:

a processor;

a database; and

a computer-readable memory coupled to the processor, the computer-readable memory configured to store a computer program;

wherein the processor is operative with the computer program to;

(i) call an application program interface to raise an event indicative of a signature collection process in response to a triggering action generated by the database application;

(ii) initiate a workflow process defined by the event that initiates the transaction instantiated by the database application with the database without committing the initiated transaction to the database;

(iii) execute a rule specified by the workflow process to determine if an electronic signature is required to approve the transaction; and

(iv) instantiate the signature collection process if execution of the rule results in a determination that an electronic signature is required for the initiated transaction to be committed to the database.

12. The computer system of claim 11 wherein the processor is operative with the computer program to call the application program interface based on an event name and an event id.

13. The computer system of claim 11 wherein the signature collection process can be either a synchronous collection process or an asynchronous collection process.

14. The computer system of claim 11 wherein the workflow process generates an electronic record that captures data associated with the initiated transaction prior to the initiated transaction being committed to the database.

15. The computer system of claim 14 wherein the electronic record comprises unstructured data.

16. The computer system of claim 15 wherein the unstructured data comprises extensible markup language data stored in character large object (CLOB) format.

17. The computer system of claim 16 wherein the extensible markup language data comprises a first well-formed extensible markup language document that comprises extensible markup language fields generated from a mapping to fields in a database and a second well-formed extensible markup language document that comprises the electronic record as it is displayed to a user during the signature collection process.

18. The computer system of claim 15 further comprising:

obtaining an electronic signature in response to the signature collection process; and

thereafter, verifying the electronic signature and, if the electronic signature is verified, updating a field of the electronic record to indicate a valid signature was received.

19. The computer system of claim 11 wherein the processor is further operative with the computer program to commit the initiated transaction to the database if the electronic signature is verified.

20. A non-transitory computer-readable medium storing a set of code modules which when executed by a processor of a computer system cause the processor to intercept a transaction instantiated by a database application to determine if an electronic signature is necessary to commit the transaction to the database, the computer-readable medium comprising:

code for calling an application program interface to raise an event indicative of a signature collection process in response to a triggering action generated by the database application;

code for initiating a workflow process defined by the event that initiates the transaction instantiated by the database application with the database without committing the initiated transaction to the database;

code for executing a rule specified by the workflow process to determine if an electronic signature is required to approve the transaction; and

code for instantiating the signature collection process if execution of the rule results in a determination that an electronic signature is required for the initiated transaction to be committed to the database.

21. The computer-readable medium of claim 20 wherein the code for initiating the workflow process comprises code for generating an electronic record that captures data associated with the initiated transaction prior to the initiated transaction being committed to the database.

22. The computer-readable medium of claim 20 wherein the electronic record comprises unstructured data.

23. The computer-readable medium of claim 22 wherein the unstructured data comprises extensible markup language data stored in character large object (CLOB) format.

24. The computer-readable medium of claim 23 wherein the extensible markup language data comprises a first well-formed extensible markup language document that comprises extensible markup language fields generated from a mapping to fields in a database and a second well-formed extensible markup language document that comprises the electronic record as it is displayed to a user during the signature collection process.

25. A method for committing database transactions, the method comprising:

generating, with one or more processors associated with one or more computer systems, information indicative of one or more triggering conditions associated with an event indicative of a signature collection process and processing that occurs when the event is evoked;

in response to determining that the one or more triggering conditions are satisfied by a database program, calling an application program interface with the one or more processors associated with the one or more computer systems to raise the event;

invoking, with the one or more processors associated with the one or more computer systems, a portion of the processing that occurs when the event is evoked to initiate a transaction instantiated by the database application with a database without committing the transaction instantiated by the database application to the database;

invoking, with the one or more processors associated with the one or more computer systems, a workflow process that executes a set of rules to determine whether an electronic signature is required to approve an electronic record representative of the pre-committed transaction instantiated by the database application; and

generating, with the one or more processors associated with the one or more computer systems, an indication of results of the signature collection process with the electronic record prior to committing the transaction instantiated by the database application to the database.

26. The method of claim 25 further comprising:

committing the transaction instantiated by the database application to the database in response to an approval of the electronic record during the signature collection process.

27. The method of claim 25 further comprising:

rolling back the transaction instantiated by the database application with the database in response to disapproval of the electronic record during the signature collection process.