IP Library Granted Patent US 6,867,789
Granted Patent B1
US 6,867,789 · App. 09/597,298 · Granted Mar 15, 2005

System and method for generating graphical user interfaces

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 6,867,789
App. No.
09/597,298
Granted
Mar 15, 2005
Kind
B1
Abstract

An automated method for generating Graphical User Interfaces (GUI's) is illustrated in the context of a system for processing financial applications. In one embodiment, the GUI generator converts domain data representing over one thousand application types into an equal number of corresponding user screens. The interface may also be bi-directional, operating on user inputs to validate data or check for double keying.

Claims (32)

1. A method for automatically generating a graphical user interface for use in receiving an application for a financial services product, comprising:

(a) receiving domain data defining layout attributes of an application for a particular financial services product out of multiple financial services products for which applications can be made, the layout attributes including field descriptions and locations on the application for the fields;

(b) based on the layout attributes, converting the domain data to a presentable format comprising a graphical user interface applicant screen by automatically generating user interface script; and

(c) displaying the applicant screen according to the domain data received in step (a) and the resulting format from the conversion in step (b), the applicant screen being customized for the particular financial services product;

(d) wherein the applicant screen substantially reflects the layout of a printed application for the particular financial services product.

2. The method of claim 1 , wherein the step (a) of receiving comprises inputting data manually.

3. The method of claim 1 , wherein the step (a) of receiving comprises collecting data from a scanner in a semi-automated process.

4. The method of claim 1 , wherein the step (a) of receiving comprises interfacing to a pre-existing database of domain data.

5. The method of claim 1 , wherein the step (a) of receiving comprises automated conversion from a flat file to data in Extensible Markup Language (XML) format.

6. The method of claim 1 , wherein the step (b) of converting comprises a step (e) of translating from Extensible Markup Language (XML) to Hyper Text Markup Language (HTML) format.

7. The method of claim 6 , wherein the step (e) of converting is accomplished with application of Extensible Stylesheet Language (XSL).

8. The method of claim 1 , wherein the step (b) of converting is accomplished with application of Extensible Stylesheet Language (XSL) without resulting in Hyper Text Markup Language (HTML) format.

9. The method of claim 1 , wherein the step (b) of converting comprises application of Document Style Semantics and Specification Language (DSSSL).

10. The method of claim 1 , wherein the step (b) of converting comprises application of Cascading Style Sheets (CSS).

11. The method of claim 1 , wherein the step (b) of converting is executed on an as-needed basis in response to an applicant action initiating an application for the particular financial services product, thereby providing for the generation of the graphical user interface applicant screen on a per-transaction basis.

12. The method of claim 1 , wherein the step (b) of converting is executed when triggered by a change in domain data, thereby providing for the generation of the graphical user interface applicant screen each time the domain data for the particular financial services product is modified.

13. The method of claim 1 , wherein the step (b) of converting is executed at scheduled intervals.

14. The method of claim 1 , further comprising the step of (e) receiving applicant input information entered into the graphical user interface for the particular financial services product.

15. The method of claim 14 , wherein the applicant input information is processed for making an approval determination using a selected one or a selected more than one, of a plurality of selectable decision engines.

16. The method of claim 14 , wherein the applicant input information is forwarded to a rules engine for validating the data input by the applicant.

17. A system for automatically generating customized graphical user interfaces for applications for financial services products, comprising:

a database of domain data defining layout attributes of customized applications for a plurality of financial services products, the layout attributes including field descriptions and locations on the application for the fields;

a processing server for processing applicant requests for financial services products from the plurality of financial services products, the processing server receiving the applicant requests and providing decisions;

a graphical user interface generator for converting, based on the layout attributes, domain data for a particular financial services product into a graphical user interface applicant screen tailored for the particular financial services product, wherein the conversion comprises automatically generating user interface script based on domain data for the particular financial services product.

18. The system of claim 17 , wherein the graphical user interface generator produces the tailored graphical user interface screen in response to an applicant requesting the particular financial services product, thereby generating the tailored graphical user interface on a per-transaction basis.

19. The system of claim 17 , wherein the graphical user interface generator produces the tailored graphical user interface screen in response to a change made to the database of domain data, thereby generating the tailored graphical user interface each time the database is modified.

20. The system of claim 17 , wherein the domain data comprises entries made to flat file data that are automatically converted to Extensible Markup Language (XML) format each time the graphical user interface generator is generating a graphical user interface.

21. The system of claim 17 , wherein the graphical user interface generator converts domain data in Extensible Markup Language (XML) format to Hypertext Markup Language (HTML) format.

22. The system of claim 21 , wherein the conversion from XML to HTML is carried out using Extensible Stylesheet Language (XSL).

23. The system of claim 17 , wherein the processing server receives an applicant request comprising applicant input information entered into the graphical user interface for the particular financial services product.

24. The system of claim 23 , wherein the processing server processes the applicant input information for making an approval determination using a selected one or a selected more than one, of a plurality of selectable decision engines.

25. The method of claim 23 , wherein the applicant input information is forwarded to a rules engine for validating the data input by the applicant.

Assignments (3)
NUNC PRO TUNC ASSIGNMENT Recorded Aug 5, 2009
From: CHASE MANHATTAN BANK USA, N.A.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 023057/0179 →
MERGER Recorded Aug 5, 2009
From: BANK ONE, DELAWARE, NATIONAL ASSOCIATION
To: CHASE MANHATTAN BANK USA, NATIONAL ASSOCIATION
Reel/Frame 023057/0455 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 15, 2004
From: TEICHMAN, WILLIAM J.
To: BANK ONE, DELAWARE, NATIONAL ASSOCIATION
Reel/Frame 015218/0726 →