Universal forms engine

• US 7,376,891 B2
• Filed: 09/29/2003
• Issued: 05/20/2008
• Est. Priority Date: 06/04/1998
• Status: Expired due to Term

• Current Assignee: CollegeNET Incorporated
• Original Assignee: CollegeNET Incorporated
• Inventors: Hitchock, Michael D., Wolfston, James H. Jr., Hertz, Andreè{grave over ( )} J., Stedman, John W., Price, Raymond L.
• Primary Examiner(s): Hutton; Doug
• Assistant Examiner(s): Blackwell; James H.
• Application Number:
  US10/673,674
• Publication Number:
  US 20050080756A1
• Time in Patent Office: 1,695 Days
• Field of Search: 715/505, 715/506, 715/507, 715/508, 715/513, 705/1, 707/100, 707/10, 709/203
• US Class Current: 715/221
• CPC Class Codes: G06F 40/174 Form filling; Merging
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A forms engine allows data sharing between customizable on-line forms, such as college admissions applications. Before applying, an applicant opens an account with a third party application servicer. After the applicant completes an application for one institution, the data is saved in a data base and automatically populates fields in subsequent application forms. The form for each institution is created from a form description file. Each form is branded for its institution and forms for different institutions differ in appearance and content so that the presence of the third party servicer is transparent to the applicant.

The system is extensible without programming, allowing new applicant attributes to be readily incorporated into the system and allowing the content and appearance of the application to be readily changed by changing the description file. The use of aliases for applicant attributes permits data to be readily shared between forms even though labeled and arranged differently on different forms. Information stored about each attribute allows the specification of data validation rules and data sharing and grouping rules, as well as dependency rules that permit application page content to depend on applicant'"'"'s responses on a previous page.

Claims

1. A method of further processing over a computer network forms directed by multiple public forms users to multiple institutions of higher education, the forms being processed by a third party forms servicer that is neither one of the institutions of higher education nor one of the public forms users, the method comprising:

presenting to a form user over a computer network by a third party forms servicer in response to a request from the form user, a form directed to one of the multiple institutions of higher education, the form being generated by a forms generator that generates multiple forms corresponding to multiple institutions of higher education, the forms including fields for the forms users to enter user information;

receiving by the third party forms servicer over the computer network user information and electronic payment information entered by the user;

processing by the third party forms servicer an electronic payment associated with the form, the processed payment being from the user to the one of the multiple institutions to which the form is directed;

storing by the third party forms servicer at least some of the user information entered on the form; and

maintaining by the third party forms servicer a transaction state for the form so as to prevent duplicate submission or payment,

causing the form to enter a first state after the form user submits payment information and before the payment is settled; and

transmitting the completed form to the form user to view after causing the form to enter the first state.

4. The method of claim 3 or 1 further comprising causing the form to enter a second state after the payment is settled.

5. The method of claim 3 or 1 in which causing the form to enter the first state prevents the form user from making further changes to the form.

6. The method of claim 3 or 1 in which the form enters a paid state after payment is submitted and before the payment is acknowledge by the institution or settled, and the form then enters a completed state when the form is acknowledged by the institution and the payment is settled.

7. The method of claim 3 or 1 in which if the form is not settled, the form returns to an active state.

8. The method of claim 2 or 1 further comprising:

presenting over a computer network by the third party forms servicer in response to a request from the form user, a second form directed to one of the multiple institutions of higher education; and

automatically inserting into the second form user information previously entered onto a form by the form user.

9. The method of claim 2 or 1 in which presenting to a form user over a computer network by a third party forms servicer in response to a request from the form user a form directed to one of the multiple institutions of higher education includes presenting a form including multiple pages.

10. The method of claim 9 further comprising verifying in accordance with validation criteria user information on each of the multiple pages as they are posted by the form user.

11. The method of claim 10 in which verifying in accordance with validation criteria user information on each of the multiple pages as they are posted includes verifying the user information at a client computer or at a server computer.

12. The method of claim 10 in which the validation criteria are specified by the institution to which the form is directed.

13. The method of claim 10 further comprising verifying in accordance with first validation criteria user information on each of the multiple pages as they are posted and verifying in accordance with second validation criteria user information when a completed form is submitted.

14. The method of claim 13 in which verifying user information in accordance with first validation criteria includes verifying user information at a client computer and in which verifying user information in accordance with second validation criteria includes verifying user information at a server computer.

15. The method of claim 2 or 1 in which receiving electronic payment information includes receiving electronic payment information entered onto the form.

16. The method of claim 2 or 1 in which maintaining a transaction state includes maintaining a transaction state using at least one hidden field in a page of the form.

17. The method of claim 16 further comprising determining whether a payment has been submitted by parsing a hidden field on the page of the form.

18. The method of claim 2 or 1 in which the maintaining a transaction state includes maintaining the form within one state selected from a set of states, the set of states including an active state, a submitted state, and a paid state.

19. The method of claim 2 or 1 in which presenting a form to a form user over a computer network includes presenting a form using a stateless communications conduit.

20. The method of claim 19 in which the stateless communication conduit includes the World Wide Web.

21. The method of claim 2 or 1 in which the state of the form is maintained in a database table.

22. A computer system, comprising:

a processor for carrying out computer instructions;

a computer readable m emory storing instructions for performing the steps of claim 2 or 1.

2. A method of processing over a computer network forms directed by multiple public forms users to multiple institutions of higher education, the forms being processed by a third party forms servicer that is neither one of the institutions of higher education nor one of the public forms users, the method comprising,

presenting to a form user over a computer network by a third party forms servicer in response to a request from the form user, a form directed to one of the multiple institutions of higher education, the form being generated by a forms generator that generates multiple forms corresponding to multiple institutions of higher education, the forms including fields for the forms users to enter user information;

receiving by the third party forms servicer over the computer network user information and electronic payment information entered by the user;

processing by the third party forms servicer an electronic payment associated with the form, the processed payment being from the user to the one of the multiple institutions to which the form is directed;

storing by the third party forms servicer at least some of the user information entered on the form;

maintaining by the third party forms servicer a transaction state for the form so as to prevent duplicate submission or payment; and

if the form indicates that the form user is paying by check or is requesting a fee waver, causing the form to enter a hold state until the check is received or the fee waiver is approved.

3. The method of claim 2 further comprising causing the form to enter a first state after the form user submits payment information and before the payment is settle.