US20090031230A1 - Automated Generation of Dynamic Data Entry User Interface for Relational Database Management Systems - Google Patents

Automated Generation of Dynamic Data Entry User Interface for Relational Database Management Systems Download PDF

Info

Publication number
US20090031230A1
US20090031230A1 US12172614 US17261408A US20090031230A1 US 20090031230 A1 US20090031230 A1 US 20090031230A1 US 12172614 US12172614 US 12172614 US 17261408 A US17261408 A US 17261408A US 20090031230 A1 US20090031230 A1 US 20090031230A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
entity
data
customer
order
table
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12172614
Inventor
John N. Kesler
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ADVANCED DYNAMIC INTERFACES LLC
INNOVATION MANAGEMENT SCIENCES
Original Assignee
INNOVATION MANAGEMENT SCIENCES
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30286Information retrieval; Database structures therefor ; File system structures therefor in structured data stores
    • G06F17/30557Details of integrating or interfacing systems involving at least one database management system
    • G06F17/3056Details of integrating or interfacing systems involving at least one database management system between a Database Management System and a front-end application
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/953Organization of data
    • Y10S707/954Relational
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching
    • Y10S707/99934Query formulation, input preparation, or translation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching
    • Y10S707/99935Query augmenting and refining, e.g. inexact access
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99942Manipulating data structure, e.g. compression, compaction, compilation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99943Generating database or data structure, e.g. via user interface
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • Y10S707/99945Object-oriented database structure processing

Abstract

Computer software for, computer apparatus for, and a method of automatically generating a user interface for a relational database comprising extracting schema information from the relational database and automatically generating corresponding schema and user interface metadata, storing the metadata in a repository, and automatically developing from the metadata a user interface appropriate to the relational database.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • [0001]
    This application is a continuation application of U.S. patent application Ser. No. 11/204,799 (U.S. Pat. No. 7,401,094), filed on Aug. 16, 2005, which is a continuation of U.S. patent application Ser. No. 10/040,851 (U.S. Pat. No. 7,062,502) filed on Dec. 28, 2001, and the specifications thereof are incorporated herein by reference.
  • STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
  • [0002]
    Not applicable.
  • COPYRIGHTED MATERIAL
  • [0003]
    A portion of the disclosure of this patent document contains material that is subject to copyright protection. The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever.
  • BACKGROUND OF THE INVENTION
  • [0004]
    1. Field of the Invention (Technical Field)
  • [0005]
    The present invention relates to computer database systems and more particularly to a data entry user interface used to populate a relational database with information.
  • [0006]
    2. Background Art
  • [0007]
    A glossary is presented in the GLOSSARY OF TERMS section below to facilitate a better understanding of the terms relevant to the present invention. Such terms are denoted by the use of italics.
  • [0008]
    Relational database management systems are well known in the prior art. A key characteristic of such systems is that data is organized and stored in tables in such a manner that various tables may be related to one another for the purpose of representing real world problems in the form of an organized data structure.
  • [0009]
    Relational databases are widely accepted in the modern business environment as a valuable tool to store information relating to an organization's business activities. But while relational database management systems provide an attractive way to organize and store data, they do not provide a convenient method to accept input from an end user for the purpose of populating the database with information.
  • [0010]
    A variety of commercial computer systems are available to provide user interfaces to relational databases. Such systems are typically developed to provide solutions to common business problems such as accounting systems for small businesses and inventory management systems for manufacturers.
  • [0011]
    However, a myriad of business problems cannot be solved with existing commercial computer systems. Many business problems are specific to a particular organization requiring a custom database structure to properly model each problem. It follows then that these custom database structures require custom user interfaces in order to populate the database with information.
  • [0012]
    Creating custom user interfaces for relational databases is a time consuming and costly process. At a high level, the process generally includes the following stages:
    • 1. Analyze the business problem to define a set of requirements.
    • 2. Design a data structure and a set of business rules to provide for the collection and storage of information relevant to the set of requirements defined in the previous stage.
    • 3. Design a user interface within which users may navigate through the relational database to store and retrieve information subject to the set of business rules defined in the previous stage.
    • 4. Create the user interface by writing computer code.
    • 5. Test the user interface. Correct programming and design errors.
    • 6. Implement and deploy the database and user interface.
    • 7. Repeat stages 1 through 6 as new requirements evolve over time.
  • [0020]
    For small scale databases with approximately 25 or fewer tables, this process often requires a couple hundred hours of programming effort in addition to numerous resources necessary to gather requirements, test and deploy the system. For larger databases, the cost increases nearly in direct proportion with the size of the database. Needless to say, the cost of developing custom user interfaces is extremely expensive often prohibiting the development of such systems for many organizations.
  • [0021]
    Most data entry user interfaces are form-based in which a graphical representation of a form is presented on a video display. The form, which relates to the data being entered, contains a series of data entry controls that are used to collect data from the end user. These data entry controls typically attempt to provide the user with an intuitive data entry experience. For example, as illustrated in FIG. 1, when entering a Customer Order into the database, an edit box with a corresponding button might represent the Order Date. The user can enter a date into the edit box by: (1) using the keyboard or (2) clicking the button to obtain a calendar from which a date can then be selected.
  • [0022]
    A key problem arises with the form-based user interface depicted above in that if a new data element (i.e., field) is added to a table in the database, a new data entry control must be added to the table's corresponding form in the user interface. This modification requires further programming effort, additional testing, and a recompilation and redeployment of the user interface. So not only is the user interface extremely expensive to develop in the first place, it is also very costly to maintain over the lifetime of the database.
  • [0023]
    In order to dramatically reduce the cost and turnaround time of developing and maintaining data entry user interfaces for relational databases, it is desirable to generate the user interface, and more particularly the data entry forms, dynamically at run-time without the necessity of writing computer code. The user interface should also provide a mechanism by which users can conveniently navigate through the database for the purposes of entering and maintaining data. Finally, the user interface should be extensible so that a system administrator can modify the interface to provide users with a better data entry experience and to insure the integrity of data stored in the underlying database.
  • SUMMARY OF THE INVENTION
  • [0024]
    The present invention is of computer software for, computer apparatus for, and a method of automatically generating a user interface for a relational database comprising: extracting schema information from the relational database and automatically generating corresponding schema and user interface metadata; storing the metadata in a repository; and automatically developing from the metadata a user interface appropriate to the relational database. In the preferred embodiment, the schema and user interface metadata comprise entities, entity fields, entity relationships, and entity search paths. The entity relationships comprising one-to-many, many-to-one, and many-to-many relationships, and the automatically developed user interface comprises context menus specific to type of entity relationship. The schema and user interface metadata preferably additionally comprises platform attributes for abstracting syntactic differences between database implementations. The invention preferably additionally provides for addition of non-automatically-generated functionality to the developed user interface, such as scripts, external components, business rules, and/or triggers. The metadata in the repository is refreshable after schema changes are made to the relational database.
  • [0025]
    It is the primary object of the present invention to provide a method and system by which data entry forms for relational databases may be generated dynamically at run-time without the necessity of writing computer code to accomplish this task.
  • [0026]
    It is a further object of the present invention to provide a method and system by which end users may conveniently navigate through a relational database for the purposes of entering and maintaining data.
  • [0027]
    It is still a further object of the present invention to provide a method and system for the validation, insertion, update, and deletion of data.
  • [0028]
    Other objects of the present invention, including methods to provide application extensibility, will become apparent from the detailed description that follows.
  • GLOSSARY OF TERMS
  • [0029]
    For purposes of the specification and claims, the following terms in Table 1 are defined to have the following meanings:
  • [0000]
    TABLE 1
    TERM DEFINITION
    Boolean A value that must be either TRUE (non 0) or FALSE (0). Some
    databases systems store Boolean values as a single bit.
    Business Rule The logical rules that are used to run a business. Business rules can
    be enforced through the user interface or in a database using
    triggers, stored procedures, and constraints.
    Data Entry Control Objects that are contained within data entry forms and are designed
    to display data and accept input from users.
    Data Integrity A state in which all the data values stored in the database are
    correct. If incorrect data values have been stored in a database, the
    database is said to have lost data integrity.
    Datatype An attribute that specifies what type (i.e. Boolean, text, number,
    date, etc) of information can be stored in a field.
    Design Time Anytime a computer programmer is building an application/user
    interface.
    Extensible Markup Language Extensible Markup Language (XML) is a meta-markup language that
    (XML) provides a format for describing structured data. This facilitates more
    precise declarations of content and more meaningful search results
    across multiple platforms. In addition, XML is enabling a new
    generation of Web-based data viewing and manipulation
    applications.
    Field In a database table, the area in each row that stores the data value
    for some attribute of the object modeled by the table.
    Foreign Key The field or combination of fields whose values match the primary
    key (PK) or unique key in the same or another table.
    Intersection Table A table used to form a relationship between two or more indirectly
    related tables.
    Metadata Information about the properties of data, such as the type of data in
    a field (numeric, text, and so on) or the length of a field. It can also
    be information about the structure of data or information that
    specifies the design of objects such as tables and relationships.
    NULL An entry that has no explicitly assigned value. NULL is not
    equivalent to zero or blank. A value of NULL is not considered to be
    greater than, less than, or equivalent to any other value, including
    another value of NULL.
    Primary Key A field or set of fields that uniquely identify all the rows in a table.
    Primary keys do not allow null values. No two rows can have the
    same primary key value; therefore, a primary key value always
    uniquely identifies a single row.
    Record A group of related fields of information treated as a unit in a table.
    Relational Database A collection of information organized in related tables where each
    table consists of records and fields.
    Relational Database A software system that supports relational databases. Well known
    Management System examples are Microsoft Access, Microsoft SQL Server and Oracle.
    Relationship A link between tables that references the primary key in one table to
    a foreign key in another table.
    Run-Time Any time the user is actually running and interacting with the
    application/user interface.
    Schema A collection of database objects including tables, views, indexes,
    and foreign keys.
    Stored Procedure A precompiled collection of SQL statements stored under a name
    and processed as a unit.
    Structured Query Language A language used to insert, retrieve, modify, and delete data in a
    (SQL) relational database.
    System Administrator A generic term used throughout this document which refers to any
    person or persons who might perform business requirement
    analysis, database design and implementation duties, or make
    configuration changes to the metadata used by the present
    invention.
    Table A two-dimensional object, consisting of records and fields, used to
    store data in a relational database.
    Table Join As a verb, to combine the contents of two or more tables and
    produce a result set that incorporates rows and fields from each
    table. Tables are typically joined using data that they have in
    common. As a noun, the process or result of joining tables.
    Unique Key Constraint Constraints that enforce table integrity on a non-primary key.
    Unique constraints ensure that no duplicate values are entered in
    the fields, which compose the key.
    View A database object that can be referenced the same way as a table in
    SQL statements. Views are defined using a SELECT statement and
    are analogous to an object that contains the result set of this
    statement.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0030]
    The accompanying drawings, which are incorporated into and form a part of the specification, illustrate one or more embodiments of the present invention and, together with the description, serve to explain the principles of the invention. The drawings are only for the purpose of illustrating one or more preferred embodiments of the invention and are not to be construed as limiting the invention. In the drawings:
  • [0031]
    FIG. 1 depicts a data entry control.
  • [0032]
    FIG. 2 depicts the high-level architecture implemented by the invention.
  • [0033]
    FIG. 3 summarizes the first 4 Forms of Normalization.
  • [0034]
    FIG. 4 depicts the Entity Relationship Diagram for the example database.
  • [0035]
    FIG. 5 depicts the parent-child paradigm implemented by the user interface.
  • [0036]
    FIG. 6 depicts selecting a child entity.
  • [0037]
    FIG. 7 depicts the View Menu in the user interface.
  • [0038]
    FIG. 8 depicts the Parent context menu.
  • [0039]
    FIG. 9 depicts the Reference context menu.
  • [0040]
    FIG. 10 depicts access to Reference Tables through the View Menu.
  • [0041]
    FIG. 11 depicts the One-To-Many context menu.
  • [0042]
    FIG. 12 depicts the Many-To-One context menu.
  • [0043]
    FIG. 13 depicts the Many-To-Many context menu.
  • [0044]
    FIG. 14 depicts selection of New Line Item One-To-Many menu option.
  • [0045]
    FIG. 15 depicts entering data on the Line Item data entry form.
  • [0046]
    FIG. 16 depicts the newly added Line Item record.
  • [0047]
    FIG. 17 depicts selection of the New Customer Many-To-One menu option.
  • [0048]
    FIG. 18 depicts entering data on the Customer data entry form.
  • [0049]
    FIG. 19 depicts the newly added Customer record.
  • [0050]
    FIG. 20 depicts selection of the New Spoken Language Many-To-Many menu option.
  • [0051]
    FIG. 21 depicts entering data on the Spoken Language data entry form.
  • [0052]
    FIG. 22 depicts the newly added Spoken Language record.
  • [0053]
    FIG. 23 depicts selecting the Promote Customer menu option.
  • [0054]
    FIG. 24 depicts the newly promoted Customer entity.
  • [0055]
    FIG. 25 depicts the results of a Quick-Text search on “Suyama”.
  • [0056]
    FIG. 26 depicts the results of Quick-Text search with two search columns defined for Customer Order.
  • [0057]
    FIG. 27 depicts the results of a Quick-Text search against the Line Item child entity.
  • [0058]
    FIG. 28 depicts an Advanced Search screen for the Customer Order entity.
  • [0059]
    FIG. 29 depicts saving an Advanced Search into an XML file.
  • [0060]
    FIG. 30 depicts deletion of a Line Item record.
  • [0061]
    FIG. 31 depicts the Customer Order data entry form.
  • [0062]
    FIG. 32 depicts a flowchart of decision points used in assigned data entry controls to entity fields.
  • [0063]
    FIG. 33 depicts a ComboBoxControl data entry control.
  • [0064]
    FIG. 34 depicts a SmartComboControl data entry control.
  • [0065]
    FIG. 35 illustrates a customized caption for the Employee child entity.
  • [0066]
    FIG. 36 depicts a Quick-Text search for a Many-To-Many relationship.
  • [0067]
    FIG. 37 depicts a list of searchable entities on the Advanced Search screen.
  • [0068]
    FIG. 38 depicts the Filter definition screen.
  • [0069]
    FIG. 39 depicts a new Line Item record for which SQL will be generated.
  • [0070]
    FIG. 40 depicts the Data Entry Grid for the Line Item entity.
  • [0071]
    FIG. 41 depicts the Unit Price and Extended Price calculated data entry controls.
  • [0072]
    FIG. 42 depicts the CheckBox data entry control.
  • [0073]
    FIG. 43 depicts the process of adding a new Shipper while using a ComboBoxControl.
  • [0074]
    FIG. 44 depicts the Shipper data entry form that was loaded by a ComboBoxControl.
  • [0075]
    FIG. 45 depicts the newly added Shipper in the ComboBoxControl.
  • [0076]
    FIG. 46 depicts the process of using the FileDialogControl data entry control.
  • [0077]
    FIG. 47 depicts the process of using the FileDialogControl data entry control.
  • [0078]
    FIG. 48 depicts the process of using the FileDialogControl data entry control.
  • [0079]
    FIG. 49 depicts the process of using the ImageBLOB data entry control.
  • [0080]
    FIG. 50 depicts the process of using the ImageBLOB data entry control including viewing an image.
  • [0081]
    FIG. 51 depicts the MaskEditBox data entry control.
  • [0082]
    FIG. 52 depicts the NotesControl data entry control.
  • [0083]
    FIG. 53 depicts the NumericFormatBox data entry control.
  • [0084]
    FIG. 54 depicts the TextBoxControl with the Email Address attribute set to TRUE.
  • [0085]
    FIG. 55 depicts the Business Rule input screen from the Utility Tool.
  • [0086]
    FIG. 56 depicts the Trigger input screen from the Utility Tool.
  • [0087]
    FIG. 57 depicts the Utility Tool interface.
  • [0088]
    FIG. 58 illustrates the creation of a new configuration repository.
  • [0089]
    FIG. 59 illustrates definition of a new Datasource.
  • [0090]
    FIG. 60 illustrates the selection of Reference Tables.
  • [0091]
    FIG. 61 depicts the fully populated Entities tree.
  • [0092]
    FIG. 62 illustrates modification of the control type for the Customer field in the Customer Order entity.
  • [0093]
    FIG. 63 illustrates modification of the control type for the Ship Address field in the Customer Order entity.
  • [0094]
    FIG. 64 depicts the definition of entity attributes for the Customer Order entity.
  • [0095]
    FIG. 65 depicts the definition of a search column for the Customer Order entity.
  • [0096]
    FIG. 66 depicts the definition of a sort column for the Customer Order entity.
  • [0097]
    FIG. 67 illustrates setting the order of relationships for the Customer Order entity.
  • [0098]
    FIG. 68 illustrates changing the Caption attribute of the Employee relationship to Sales Person.
  • [0099]
    FIG. 69 illustrates granting permissions to the Sales Reps group for the Customer Order entity.
  • [0100]
    FIG. 70 illustrates setting the Display On Tab entity attribute to TRUE.
  • [0101]
    FIG. 71 illustrates the definition of a new unbound CalculatedControl.
  • [0102]
    FIG. 72 illustrates the definition of a bound CalculatedControl
  • [0103]
    FIG. 73 illustrates the definition of system attributes such as Application Caption and Startup Entity.
  • [0104]
    FIG. 74 illustrates the definition of a new Tool called “Import Wizard”.
  • [0105]
    FIG. 75 illustrates the modification of the user interface configuration file.
  • [0106]
    FIG. 76 illustrates the System Login screen of the user interface.
  • [0107]
    FIG. 77 depicts the Import Wizard tool menu option.
  • [0108]
    FIG. 78 depicts the Advanced search screen.
  • [0109]
    FIG. 79 depicts a custom filter screen.
  • [0110]
    FIG. 80 illustrates setting the Ship Address foreign key on the Customer Order data entry form.
  • [0111]
    FIG. 81 illustrates adding a new Line Item record to the new Customer Order record.
  • [0112]
    FIG. 82 illustrates promoting the Sales Person (Employee) child entity.
  • [0113]
    FIG. 83 illustrates adding a new Customer Order when Employee is the parent entity.
  • [0114]
    FIG. 84 depicts the addition of a new field to the CUSTOMER_ORDER table in the database.
  • [0115]
    FIG. 85 illustrates the Refresh of the Customer Order entity in the Utility Tool.
  • [0116]
    FIG. 86 depicts the newly added Requested Date field on the Customer Order data entry screen.
  • DETAILED DESCRIPTION OF THE INVENTION
  • [0117]
    As alluded to above, the high cost of developing and maintaining data entry user interfaces in the prior art is largely attributed to the tight coupling of data entry forms with the structure of the underlying relational database. This problem is further aggravated by the common practice of hard coding navigation, business rules and Structured Query Language (SQL) into the source code of the user interface, thus requiring a recompilation and redeployment of the user interface software when modifications to the database structure and/or changes to business logic are made.
  • [0118]
    To overcome this problem, the present invention proposes the high level architecture depicted in FIG. 2. Under this architecture, a utility program (the “Utility Tool”) interprets database schema information from the relational database. Information gleaned from the schema is used to populate a configuration repository with metadata. This metadata is then utilized by the user interface (the “UI”) to: (1) generate data entry forms, (2) provide a method of navigation through the database, including menus and sophisticated searching functionality and (3) provide a mechanism for the validation, insertion, update and deletion of data.
  • [0119]
    A key principal behind the present invention is that the structure, or schema, of a relational database provides a significant amount of useful information with respect to the data entry user interface. While it is theoretically possible to generate a user interface directly from the database schema without the use of a configuration repository, the layer of abstraction offered by the repository has numerous advantages. These advantages will be explored in depth in the remainder of this document.
  • [0120]
    In one embodiment, the present invention utilizes personal computer-based client/server architecture for the purpose of providing data entry access to a relational database. Insofar as a single personal computer (PC) can act as both client and server, it is perfectly acceptable to deploy the data entry interface and the relational database on a standalone PC. In addition, all user interaction is possible using either a keyboard or a mouse.
  • [0121]
    As web interface technology matures, other embodiments of the present invention, using very similar if not identical architecture, might well be implemented over the Internet. Under such embodiments, the “server” might be any set of computers on the Internet that look like a single database to the client. The “client” might be any computer on the Internet running one of several commercially available browsers.
  • [0122]
    The relational database should meet the following requirements:
    • 1. Each table should have a single integer field which serves as its primary key. This requirement, a common practice in the database development community, does not preclude the use of unique key constraints on fields that compose the logical primary key, such as the social security number for a table of employees. Among other advantages, this requirement simplifies table joins by insuring that the primary key of the first table in the join is composed of a single field of the same datatype as the foreign key in the second or related table.
    • 2. Relationships between tables should be established using foreign keys.
    • 3. A view should be created for each table in the database. The view represents the physical table throughout the UI for the purposes of searching and displaying data. The view should include the primary key of the underlying table. The main objective of this requirement is to present users with formatted data using intuitive column names as opposed to unformatted data using cryptic database field names.
  • [0126]
    While not a requirement, it is highly recommended that the relational database be in at least 3rd Normal Form. Normalization is widely accepted as a systematic methodology by which redundancy can be removed from relational database structures. For the reader's convenience, the first 4 Forms of Normalization are summarized in FIG. 3.
  • Relational Database Example
  • [0127]
    In order to help the reader better understand the present invention, an example will used throughout the remainder of the detailed description. An Entity Relationship Diagram (ERD) for the example is presented in FIG. 4. The arrows point from the foreign key table to the primary key table. For example, the CUSTOMER_ORDER table relates to the CUSTOMER table on the CUSTOMER_ID field. CUSTOMER_ORDER is the foreign key table. CUSTOMER is primary key table.
  • [0128]
    The example is a simple order entry database for a fictional company, ACME Grocery Supply, in which:
    • Each Customer is assumed to have one Billing Address.
    • Each Customer Order is taken by an Employee (i.e. Sales Person).
    • Each Customer Order consists of one or more Line Items.
    • Each Customer Order is assumed to have a single Shipping Address regardless of the number of Line Items.
    • Each Line Item is for a single Product. The Unit Price of a Product may be discounted on the Line Item by entering a Discount percentage.
    • Products are supplied by Suppliers and grouped into Categories.
    • The fictional company is assumed to do business on an international basis. Consequently, each Employee may speak one or more Spoken Languages.
    • Employees may have a Manager who is also an Employee. However, Employees cannot manage themselves.
  • [0137]
    The example database has been designed to help illustrate the fundamental principles of the present invention. With one exception, the database is in 4th Normal Form. The lone exception has to do with the implementation of the ADDRESS table. The ADDRESS table violates normalization rules in that it contains redundancy. However, in order to simplify and limit the size and complexity of the example, Addresses have not been normalized.
  • [0138]
    Other liberties have been taken to limit the size and complexity of the example. For example, a more realistic implementation of the PRODUCT table would track price changes over time. However, the example is not intended to accurately model the real world problem of designing order entry systems. Instead, its purpose is to illustrate common database principles with respect to the present invention.
  • The Configuration Repository
  • [0139]
    Instead of tightly coupling the user interface with the relational database, a configuration repository is used to present a layer of abstraction between the database and the user interface. The configuration repository consists of highly structured metadata. The metadata is organized in the following manner:
  • Entities
  • [0140]
    Physical database tables are represented by “entities”. A single table may be represented by more than one entity through a technique called “aliasing”. For example, separate entities might be defined to distinguish between domestic and international Customers even though a single table, CUSTOMER, is used to store all Customer data.
  • [0141]
    A special type of entity, called a “reference entity”, exists for entities that are mostly incidental to the overall business purpose behind the relational database. Reference entities help to categorize or describe data in other entities. For example, Categories help to logically organize and describe groups of related Products. But it is unlikely that most end users will ever need to interact directly the underlying CATEGORY table. Therefore, reference entities are treated differently in the UI. These differences will be made apparent in the remaining sections of this document.
  • [0142]
    Throughout the UI, with the exception of data entry forms, data relating to entities is supplied through database views. Database views provide users with easy-to-read column names and formatted data. For example, the view assigned to the Employee entity might concatenate the LAST_NAME and FIRST_NAME fields from the EMPLOYEE table into a single column, EmployeeName, as in the following example depicted in Table 2 and Table 3:
  • [0000]
    TABLE 2
    FIRST_NAME LAST_NAME
    Jane Doe
  • Becomes:
  • [0143]
  • [0000]
    TABLE 3
    EmployeeName
    Doe, Jane
  • [0144]
    Searching is performed against view columns rather than table fields. Similarly, search results are presented in the form of data lists, which consist of a collection of view columns.
  • Entity Fields
  • [0145]
    “Entity fields” represent fields within database tables. Each entity field is assigned a single data entry control. The metadata relating to each entity field defines the behavior of its corresponding data entry control. Data entry forms consist of an ordered collection of data entry controls defined by the entity field metadata.
  • [0146]
    Logical entity fields may be defined to derive values that are not actually stored in table fields. For example, it might be desirable to display a Product's Unit Price on the Line Item data entry form even though a corresponding field does not exist in the LINE_ITEM table. A special data entry control, called a Calculated Control, may be defined to retrieve and display the Unit Price for the currently selected Product. This example will be illustrated under the USER INTERFACE GENERATION section.
  • Entity Relationships
  • [0147]
    Relationships between database tables, implemented through foreign keys in the database, are represented by “entity relationships”. In the configuration repository, two entity relationships are generated for each foreign key defined in the database schema. For example, the PRODUCT_ID foreign key in the LINE_ITEM table would generate one relationship from the perspective of the foreign key table, LINE_ITEM, and one from the perspective of the related table (or primary key table), PRODUCT as shown in Table 4:
  • [0000]
    TABLE 4
    Relationship Relationship Type
    LINE_ITEM.PRODUCT_ID = Many-To-One
    PRODUCT.PRODUCT_ID
    PRODUCT.PRODUCT_ID = One-To-Many
    LINE_ITEM.PRODUCT_ID
  • [0148]
    There are three types of entity relationships: One-To-Many, Many-To-One, and Many-To-Many. The first relationship in the table above is of relationship type Many-To-One, as are all relationships from the perspective of the foreign key table. The second relationship in the table is of type One-To-Many, as are all relationships from the perspective of the related table.
  • [0149]
    Many-To-Many relationships are reserved for a special case in which it is desirable to form a direct logical relationship between two indirectly related entities, such as Employee and Spoken Language. This type of relationship will be explored in more detail later.
  • [0150]
    Entity relationships provide metadata to support two key pieces of functionality in the UI: (1) navigation and (2) dynamically generated SQL.
  • Entity Search Path
  • [0151]
    From the perspective of a particular entity, the “search path” defines the collection of directly and indirectly related entities that may be searched with respect to the entity. The entity search path is a subset of all entity relationships in the configuration repository. For example, to obtain a list of Customers who bought one or more Products from a specific Sales Person, the list of entity relationships in Table 5 must be defined on the search path of the Customer entity:
  • [0000]
    TABLE 5
    Relationship
    Relationship Type
    CUSTOMER.CUSTOMER_ID = One-To-
    CUSTOMER_ORDER.CUSTOMER_ID Many
    CUSTOMER_ORDER.CUSTOMER_ORDER_ID = One-To-
    LINE_ITEM.CUSTOMER_ORDER_ID Many
    CUSTOMER_ORDER.SALES_PERSON_ID = Many-To-
    EMPLOYEE.EMPLOYEE_ID One
    PRODUCT.PRODUCT_ID = One-To-
    LINE_ITEM.PRODUCT_ID Many
  • [0152]
    The entity search path also resolves circular loops that might otherwise exist between two entities. For example, two paths exist from the Customer entity to the Address entity. One path, which corresponds to the billing address, flows directly from the Customer entity to the Address entity via the BILL_ADDRESS_ID foreign key. A second path, corresponding to the shipping address, flows indirectly from the Customer entity to the Address entity through the Customer Order entity via the SHIP_ADDRESS_ID foreign key. Consequently, a circular loop exists between the Customer and Address entities:
  • [0000]
    Figure US20090031230A1-20090129-C00001
  • [0153]
    In order to allow searching of both billing and shipping addresses with respect to the Customer entity, this loop must be resolved. This can be accomplished by aliasing the Address entity into a new entity called Shipping Address. This results in the search path in Table 6 for the Customer entity:
  • [0000]
    TABLE 6
    Relationship Relationship Type
    CUSTOMER.CUSTOMER_ID = One-To-Many
    CUSTOMER_ORDER.CUSTOMER_ID
    CUSTOMER.BILL_ADDRESS_ID = One-To-Many
    ADDRESS.ADDRESS_ID
    CUSTOMER_ORDER.SHIP_ADDRESS_ID = One-To-Many
    ADDRESS_1.ADDRESS_ID
  • [0154]
    The aliased Address entity, Shipping Address, which corresponds to the logical table ADDRESS_1 in the third relationship above, resolves the circular loop by creating the illusion of two distinct instances of the physical ADDRESS table in the underlying database.
  • [0155]
    Another way to resolve this circular loop is to simply include Address information in the database views for both the Customer and Customer Order entities. Searching for shipping address information can then be performed against the Customer Order entity directly.
  • Entity and Entity Relationship Permissions
  • [0156]
    Data entry and navigation functionality in the UI are provided through “pop-up” menus. These menus are generated dynamically from metadata stored in the configuration repository. The metadata associated with menus is “predefined” in the sense that it is not derived from the database schema but instead built into the UI architecture. As will be demonstrated throughout the remainder of this document, the type of menu shown to a user at any given point is determined by the “menu context”. The menu context simply describes the point from within the UI where the end user requests a menu.
  • [0157]
    As will be shown, menu contexts are tightly coupled to entities and entity relationships. Thus, permissions that provide access to menu options (stored as metadata) are granted at the entity and entity relationship level.
  • Platforms and Platform Attributes
  • [0158]
    Syntactic differences between various database systems such as Oracle and Microsoft SQL Server must be accounted for. The configuration repository contains a set of predefined metadata that provides a layer of abstraction between the UI and specific database systems (referred to as “platforms” within the metadata structure). One example of a syntactic difference between platforms would be the date delimiter used in SQL expressions. Consider the following SQL statement, which works fine against SQL Server but would fail against Microsoft Access:
  • SELECT*FROM CUSTOMER_ORDER WHERE ORDER_DATE BETWEEN ‘1-1-1998’ AND ‘12-31-1998’
  • [0159]
    SQL Server uses the single-quote symbol to delimit dates whereas Microsoft Access uses the # symbol.
  • [0160]
    To account for such differences between database platforms, a set of attributes are defined which specify the various symbols and formats used by each platform. In this way, SQL can be generated generically by the UI as the following modified version of the above SQL statement shows:
  • [0000]
    SELECT * FROM CUSTOMER_ORDER
    WHERE ORDER_DATE BETWEEN [DATE_DELIMITER]1-1-
     1998[DATE_DELIMITER] AND
     [DATE_DELIMITER]12-31-1998[DATE_DELIMITER]
  • [0161]
    The “[DATE_DELIMITER]” placeholder is replaced by the appropriate symbol before the SQL statement is executed.
  • [0162]
    Another advantage of abstracting syntactic differences between database systems is that the Utility Tool and UI may be used to access new database systems by simply adding metadata to the platform and platform attribute structure.
  • User Interface Architecture
  • [0163]
    The UI architecture is tightly coupled with the structure of the metadata relating to entities, entity fields, entity relationships, and entity search paths. In particular, the architecture takes advantage of the inherent parent-child paradigm offered by the entity-entity relationship structure. FIG. 5 illustrates this paradigm quite clearly by presenting the main screen of the UI. On the top portion of the screen, we see that the focus of the interface is with respect to the Customer Order entity. On the bottom left side of the screen, we see a list of related entities (exclusive of reference entities, a detail that will be discussed momentarily). Under the current context of the interface, Customer Order is the “parent” entity. The list of related entities are called “children”. This list is derived from the entity relationships that are defined for the Customer Order entity. The currently selected child is Line Item. In FIG. 6, the selected child has been switched to Customer.
  • [0164]
    The parent entity may be changed by selecting a different entity through the View menu depicted in FIG. 7.
  • [0165]
    Note that data display is list-driven. As mentioned earlier, all data lists are based on database views. In FIG. 5, a list of Customer Orders is shown on the top half of the screen. This list is the result of a “quick-text search” which will be discussed shortly. A list of Line Items for the currently selected Customer Order is displayed on the bottom half of the screen. The architecture attempts to maximize the amount of information displayed with the effective use of data lists in conjunction with the parent-child entity paradigm. Switching the selected child entity results in a filtered list of information relating to the newly selected child. Regardless, of the type of relationship between parent and child entities (i.e. One-To-Many, Many-To-One, or Many-To-Many), child data lists are filtered according to the currently selected record for the parent entity. This is accomplished through dynamic SQL generation.
  • [0166]
    It is not necessary to display reference entities as children of a parent entity since it is assumed that fields of interest from these reference entities are included in the database view for the corresponding parent entity. For example, notice that the Customer Order view in FIG. 5 includes the ShipperName in the data list but does not include Shipper as a child entity. Shipper has been defined as a reference entity.
  • [0167]
    Data entry and navigation functionality are accessed through dynamically constructed menus. Menus are generated from data lists by right-mouse clicking on the list or using the CTRL-M key combination on the keyboard. The list of options available on a menu depends upon the context from which the end user accesses the menu within the UI. There are five menu contexts:
    • 1. Parent: FIG. 8 depicts a Parent context menu for the Customer Order parent entity. Several options deal with data entry (e.g. New, Edit, Duplicate, Delete, and View) while others deal with searching functionality (Find and Find (Advanced)). Still others deal with extracting information in the form of an export, print preview of the data list, or a predefined report using a report writer such as Crystal Reports or BusinessObjects®.
    • 2. Reference: The Reference context menu applies to the data list depicted in FIG. 9. This data list is located in the Reference Tables area, which is accessed through the View menu (see FIG. 10). With the exception of the Export and Print Preview options, all options on this menu have to do with data entry.
    • 3. One-To-Many: The One-To-Many context menu applies to child entities only. The context name, One-To-Many, corresponds to the type of relationship that exists between parent and child entities.
    • 4. Many-To-One: The Many-To-One context menu applies to child entities only. The context name, Many-To-One, corresponds to the type of relationship that exists between parent and child entities.
    • 5. Many-To-Many: The Many-To-Many context menu applies to child entities only. The context name, Many-To-Many, corresponds to the type of relationship that exists between parent and child entities.
  • [0173]
    Menu options for the last three menu contexts are depicted in FIG. 11-13. While the individual menu options are nearly identical for each of these three contexts, the functionality behind the options differs significantly. For example, FIG. 14-16 illustrate the process of adding a new Line Item to a Customer Order. With Customer Order as the parent entity, the dynamically generated data entry form for the Line Item entity is able to automatically populate the Customer Order field, which maps to the CUSTOMER_ORDER_ID foreign key in the LINE_ITEM table. This is possible because the primary key value, from the selected Customer Order record in the parent data list, is known.
  • [0174]
    On the other hand, when the child entity is Customer, as illustrated in FIG. 17-19, the context of adding a new Customer record is quite different. In this case, the relationship between parent and child entities is Many-To-One. Adding a new Customer has the impact of inserting a new record into the CUSTOMER table and modifying the CUSTOMER_ID foreign key value in the CUSTOMER_ORDER table to the value of the newly generated primary key value of the new Customer record.
  • [0175]
    When the relationship between parent and child entities is Many-To-Many, the context of the New menu option takes on yet another meaning. In FIG. 20-22, the parent entity is Employee and the child is Spoken Language. Adding a New Spoken Language has the effect of inserting a new record into the SPOKEN_LANGUAGE table and inserting a new record into the EMPLOYEE_SPOKEN_LANGUAGE table. These two operations must execute in the proper order so that, after adding the new Spoken Language record, the newly generated primary key value is used to populate the foreign key field, SPOKEN_LANGUAGE_ID, when inserting a new record into the EMPLOYEE_SPOKEN_LANGUAGE intersection table. It should be noted that the Many-To-Many relationship type applies to a special case of intersection tables, which consist of, aside from the primary key, two, and only two, foreign key fields. This special case is quite common in practice. The Many-To-Many relationship type offers convenient functionality to end users. This functionality will be discussed in more detail later.
  • [0176]
    Menus for child entities contain a particularly powerful navigation menu option referred to as “promotion”. Promoting a child entity generates a new screen in which the child entity becomes the parent. Within this screen, the context of all searching is with respect to the newly promoted parent entity. FIG. 23 and FIG. 24 illustrate the promotion of the Customer entity. This functionality allows end users to drill through their database easily changing entity focus as the need arises.
  • [0177]
    Security is implemented at the menu option level. Upon the initial population of the configuration repository, permissions are granted to the Administrators user group for the most commonly used menu options. The system provides one built-in user, Admin, who belongs to the lone built-in group, Administrators. The system administrator manages security through the Utility Tool interface. All security information is stored as metadata in the configuration repository.
  • [0178]
    Two security models exist. One model provides for the integration of security in the UI with the underlying database by passing user login information from the UI to the database for verification. The other model uses a common database login for all users of the UI software. Under either case, permissions must be granted to the user's group before they can use menu options.
  • [0179]
    Configuration of permissions will be demonstrated in the UTILITY TOOL OPERATION section.
  • [0180]
    Two types of searching are provided to filter data with respect to the current parent entity: (1) quick-text searching and (2) advanced searching.
  • [0181]
    The quick-text search is designed to provide a simple method by which the parent entity may be searched to retrieve a set of records that meet a particular criterion. The criterion is entered into an edit box as depicted in FIG. 25. After entering the criterion and pressing the Enter (or Return) key on the keyboard, the parent entity is searched for instances where values in one or more searchable columns match the criterion. By default, all columns in the parent entity are searchable. A record matches if the value in at least one of the columns begins with the same character string as the criterion.
  • [0182]
    The collection of searchable columns is configurable such that one or more columns may be specified to limit the scope of the search to only these selected columns. Such is the case in FIG. 26 where only the CustomerName and EmployeeName columns are searchable as denoted by the use of the eyeglass icon next to each column header. The type of search performed against each column may be customized as well using one of the following search types in Table 7:
  • [0000]
    TABLE 7
    Search Type Description
    BEGINS Equivalent to the following SQL syntax:
    “EmployeeName LIKE ‘Suy%’”
    Where “%” is a wildcard symbol signifying 0 or more characters.
    EQUALS Equivalent to the following SQL syntax:
    “EmployeeName = ‘Suyama, Michael’”.
    INCLUDES Equivalent to the following SQL syntax:
    “EmployeeName LIKE ‘%Suy%’”
    Where “%” is a wildcard symbol signifying 0 or more characters.
    NAME_SEARCH Specially designed to allow flexible searching against names. Text is parsed into
    separate components. For example, the search text “Michael Suy” is broken into two
    distinct components, “Michael” and “Suy”. The EmployeeName column is then
    searched using the INCLUDES method for each component. Only those records for
    which INCLUDES evaluates to true for each component are returned. Thus, the SQL
    syntax for the current example would be:
    “(EmployeeName LIKE ‘%Michael%’) AND (EmployeeName LIKE ‘%Suy%’)”.
  • [0183]
    In addition, child entities may also be searched with respect to the parent entity. For example, FIG. 27 illustrates a configuration in which the CustomerName and SalesPerson columns from the Customer Order entity are searched using the NAME_SEARCH search type and the ProductName column from the Line Item child entity is also searched using the INCLUDES search type. If a Product Name is entered as the criterion, all Customer Orders on which a Line Item for the specified Product exists will be returned.
  • [0184]
    While the quick-text search is extremely flexible, in some cases it may be preferable to have access to more directed searching functionality. In the previous example, suppose a CustomerName includes the ‘Chai’ search criterion. Customer Orders where the CustomerName includes the character string ‘Chai’ will also be returned. This affect may be undesirable. To overcome this problem, advanced searching provides end users with targeted, precise searching functionality.
  • [0185]
    Advanced searching, depicted in FIG. 28, provides users with an opportunity to search against all entities defined on the search path of a parent entity, with respect, of course, to the parent entity. On the left side of the screen, a list is traversed to select columns on which filters may be defined. The right side of the screen displays a list filters that have been defined. Ultimately, these filters will be translated into SQL. Note that indentation is used to logically group filters thus implementing order of precedence into the aggregate filter expression. By default, filters are conjoined using the logical AND operator, but this default behavior may be overridden to use the OR operator as shown in the example. Once the filter has been completed, it is “applied” to generate a set of matching records for the parent entity.
  • [0186]
    A final note on advanced searching: Filters may be saved for later reuse using Extensible Markup Language (XML) as illustrated in FIG. 29.
  • [0187]
    With regard to menus and data entry functionality, not all data entry-related menu options require the use of data entry forms. The Delete menu option, for instance, simply constructs and executes a DELETE SQL statement for selected records as shown in FIG. 30. The Link and Unlink menu options are a bit more complex, but ultimately generate and execute INSERT, DELETE, and UPDATE SQL statements depending on the menu context of the entity in question.
  • [0188]
    Regardless of the menu context, the New, Duplicate, Edit, and View menu options all require the dynamic generation of data entry forms. As mentioned earlier, data entry forms are constructed from the metadata relating to the collection of entity fields for the relevant entity.
  • [0189]
    In FIG. 31, the Edit menu option was selected for a particular Customer Order. Data entry controls are graphically constructed in a list-like fashion using the metadata defined for each entity field. The ordering of the fields with respect to one another is determined by the Field Order entity field attribute. The type of data entry control assigned to each field depends upon several factors including the datatype of the field and whether or not the field is a primary or foreign key. For example, the SHIPPER_ID foreign key is represented by a dropdown list (referred to as a ComboBoxControl within the context of the present invention).
  • [0190]
    The decision-making process for the assignment of data entry controls will be discussed in depth in the METADATA GENERATION section below.
  • [0191]
    Note that red checkmarks are used to denote required fields. Required is a Boolean attribute of entity fields. Other features such as entity and entity field “scripting”, entity “business rules”, and entity “triggers” are available to promote data integrity and extend the basic functionality provided by dynamically generated data entry forms. These features will be discussed under the USER INTERFACE GENERATION section.
  • [0192]
    After editing a record, the user can cancel the changes by clicking the Cancel button or choose to save the changes to the underlying table by clicking the OK button. In the event the user elects to save the changes, the system first verifies that all required fields have been populated. It then applies any business rules that have been defined to validate user input. If any required data is missing or any business rules fail, the user is prompted to remedy the problem. Otherwise, dynamic SQL is generated to update the underlying database table.
  • [0193]
    NOTE: Of all the functionality provided by the present invention, the cost savings made possible through the dynamic generation of data entry forms cannot be overstated. Using conventional user interface development methods, each data entry form must be painstakingly programmed to provide similar functionality.
  • [0194]
    What happens if the underlying physical table is modified to add or remove a field? The metadata relating to an entity's collection of fields is simply modified within the Utility Tool to reflect the change. The data entry form will automatically adjust to changes in metadata without the necessity of writing any computer code.
  • Metadata Generation
  • [0195]
    The Utility Tool is responsible for analyzing the database schema and generating the metadata stored in the configuration repository. While custom computer code may be written to analyze database schemas for various popular relational database systems, such as Microsoft SQL Server and Oracle, several commercial middleware products are available to abstract differences between database systems into a common programming interface. In this way, foreign keys, for instance, are detected using identical, or very similar, code from within the Utility Tool regardless of database system. The present invention uses Microsoft's Data Access Components (MDAC) to provide this layer of abstraction.
  • [0196]
    The database schema provides sufficient information to populate the metadata relating to entities, entity fields, entity relationships, and entity search paths. Other default settings, such as entity and entity relationship permissions for the Administrators group, are configured to ease and speed the development process. However, these default metadata configuration settings do not make direct use of the database schema.
  • Entities
  • [0197]
    One entity is created for every table in the database. While the schema provides the primary key of each table, each table's corresponding view must be determined through a simple naming convention for the view whereby a prefix or suffix is appended to the table name to derive the name of the view. Using a suffix of “_V” would therefore yield a view name of CUSTOMER_ORDER_V for the CUSTOMER_ORDER table.
  • [0198]
    Reference entities cannot be detected from the schema. This attribute must be defined by a system administrator based on their overall understanding behind the business purpose of the relational database. Consequently, the Utility Tool prompts the system administrator with a list of tables from which reference tables may be defined. This will be illustrated in the UTILITY TOOL OPERATION section.
  • Entity Fields
  • [0199]
    The primary purpose of analyzing database schema information relating to table fields is to determine and assign an appropriate data entry control to each field. By default, one entity field is created for each field in the underlying table. A summary of the available data entry controls is presented in the USER INTERFACE GENERATION section.
  • [0200]
    The strategy used to determine the data entry control for each field is illustrated via the flowchart in FIG. 32. It should be noted that all default attributes discussed below can be modified within the Utility Tool at any time. The Utility Tool uses the following strategy during the initial population of the configuration repository and on demand by the system administrator as modifications are made to the database structure over time:
  • [0201]
    If the field is a primary key, a NumericFormatBox is assigned. Since primary key values are system generated, the NumericFormatBox will be placed in read-only mode, meaning end users cannot make changes to the value.
  • [0202]
    If the field is a foreign key, then one of two data entry controls will be assigned depending on whether the related table is a reference entity. If the related entity is a reference entity, a ComboBoxControl is assigned. The graphical representation of a ComboBoxControl is a simple dropdown list, an example of which is depicted in FIG. 33. Shipper is a reference entity. The ComboBoxControl presents a list of Shippers to the end user but actually stores the SHIPPER_ID primary key value in the CUSTOMER_ORDER table.
  • [0203]
    If the related entity is not a reference entity, a SmartComboControl is assigned. The purpose of the SmartComboControl is identical to that of the ComboBoxControl: that is, to populate a foreign key field in the underlying table. However, its functionality is a bit more complex. Unlike the ComboBoxControl, the SmartComboControl makes two significant assumptions: (1) The number of potential records in the related table could become very large. It is, therefore, inadvisable to load a large number records into a dropdown list. (2) Several fields may be necessary to uniquely differentiate each record in the related table.
  • [0204]
    For example, the CUSTOMER_ORDER_ID foreign key in the LINE_ITEM table requires the display of several fields from the related CUSTOMER_ORDER table to provide the end user with sufficient information to distinguish one Customer Order from another. In this case, it might be wise to display the CustomerName, OrderDate, and SalesPerson and, perhaps, the Customer Order ID, assuming it is used as the order number in addition to serving as the primary key (see FIG. 34). By contrast, the SHIPPER_ID foreign key in the CUSTOMER_ORDER table can be quite reasonably represented by a dropdown list, displaying only a single column that derives from the SHIPPER_NAME field in the SHIPPER table.
  • [0205]
    Keep in mind, these default settings can be easily overridden in the event that the Utility Tool's assumptions produce an undesirable result, such as assigning a SmartComboControl when a ComboBoxControl would suffice.
  • [0206]
    As with all other data entry control types, attributes are used to control the run-time behavior of each control type. With respect to the ComboBoxControl and SmartComboControl control types, two important attributes are worthy of mention here: Expression and Expression Type. These two attributes are used to determine how data is displayed to the end user and, in the case of the ComboBoxControl, the source of data for the dropdown list.
  • [0207]
    The Expression Type attribute must be one of three values: EXPRESSION, SQL, or STORED_PROCEDURE. The specific meaning of each Expression Type differs slightly for each control type as shown in Table 8 and Table 9:
  • [0000]
    TABLE 8
    Expression Type Description
    EXPRESSION A list of two fields from the related entity's corresponding view that are used
    to populate the dropdown list. For the SUPPLIER_ID foreign key in the
    CUSTOMER_ORDER table, a valid Expression attribute might be:
    SHIPPER_ID, ShipperName
    At run-time, this would be translated to the following complete SQL
    statement:
    SELECT SHIPPER_ID, ShipperName FROM SHIPPER_V
    The SQL statement above would then be executed to generate a list of
    Shippers for the dropdown list.
    SQL (Default) This is the default Expression Type selected by the Utility Tool for the
    ComboBoxControl control type. The SQL statement is executed at run-time
    to generate the dropdown list. By default, the Utility Tool uses the underlying
    view for the related entity to construct the SQL statement as in the following
    example:
    SELECT SHIPPER_ID, ShipperName FROM SHIPPER_V ORDER BY
    ShipperName
    The columns defined in the SELECT clause are derived by selecting the first
    two columns returned by the underlying view. It is assumed the system
    administrator follows a simple convention in the creation of views for all
    reference entities: The first column should be the primary key field of the
    related entity and the second should be a descriptive column that will
    represent the list of values in the dropdown list.
    Parameters may be passed to the SQL statement from the data entry form
    by using curly brackets, { }, as delimiters as in the following example for the
    MANAGER_ID foreign key in the EMPLOYEE table (which is designed to
    prevent an Employee from managing herself):
    SELECT EMPLOYEE_ID, EmployeeName
    FROM EMPLOYEE_V
    WHERE EMPLOYEE_ID <> {EMPLOYEE_ID}
    ORDER BY EmployeeName
    STORED_PROCEDURE Some databases, such as Microsoft SQL Server and Oracle, support the use
    of stored procedures. The stored procedure should return a list of records,
    as was the case with the SQL Expression Type. The list should include the
    primary key in the first column and descriptive text in the second column.
    One or more parameters may be passed to the stored procedure as in the
    following example:
    stpGetManagerList {EMPLOYEE_ID}
  • [0000]
    TABLE 9
    Expression Type Description
    EXPRESSION (Default) This is the default Expression Type selected by the Utility Tool for the
    SmartComboControl control type. The default Expression attribute is set to
    the name of the primary key field of the related entity. The Expression
    attribute is evaluated against the view associated with the related entity as in
    the following example for the CUSTOMER_ORDER_ID foreign key in the
    LINE_ITEM table:
    SELECT CUSTOMER_ORDER_ID, CustomerName, SalesPerson,
    OrderDate, CUSTOMER_ORDER_ID As OrderNumber
    FROM CUSTOMER_ORDER_V
    WHERE CUSTOMER_ORDER_ID = {CUSTOMER_ORDER_ID}
    Two points are worth noting in this example: First, the list of columns from
    the database view have been expanded from the default setting, which
    included only the primary key, CUSTOMER_ORDER_ID, to the following list:
    CUSTOMER_ORDER_ID, CustomerName, SalesPerson, OrderDate,
    CUSTOMER_ORDER_ID As OrderNumber
    Second, a WHERE clause has been inserted which limits the return list to a
    single record using a parameter as denoted by the curly brackets. The
    functionality of the SmartComboControl provides for the display of a multiple
    fields from a single record.
    SQL An SQL statement may also be used provided it returns only a single record
    with at least one column, the primary key.
    STORED_PROCEDURE A stored procedure may also be used provided it returns only a single record
    with at least one column, the primary key.
  • [0208]
    If the field is not a primary or foreign key, then the datatype is used to determine the data entry control type. The remaining decision points in the flowchart (FIG. 32) taken in conjunction with the Data Entry Control subsection of the USER INTERFACE GENERATION section are self-explanatory.
  • [0209]
    The Required entity field attribute is determined by checking the “nullable” property of table fields in the database schema. A field that is nullable can accept the NULL value. A field that does not accept NULL values is assumed to be required. The data entry controls for required entity fields are denoted with a red checkmark on data entry forms.
  • [0210]
    The order of entity fields on data entry forms is determined by the “ordinal position” property of table fields in the database schema. Ordinal position simply refers to the physical order of fields within the table. Creating table definitions whereby fields are added in the order in which they should appear on the data entry form will result in properly ordered data entry controls.
  • [0211]
    The Visible attribute determines whether entity fields are visible on the data entry form. By default, all entity fields are visible.
  • Entity Relationships
  • [0212]
    It was noted in the CONFIGURATION REPOSITORY section that two entity relationships are created for every foreign key found in the schema, one from the perspective of the foreign key table and one from the perspective of the related table. An example was presented for the PRODUCT_ID foreign key in the LINE_ITEM table. The entity relationship generated from the perspective of the Line Item entity is used to define the parent-child relationship between Line Item and Product in the UI, a Many-To-One relationship. Conversely, the entity relationship generated from the perspective of the Product entity is used to define the parent-child relationship, a One-To-Many relationship, between Product, as the parent entity, and Line Item, as the child entity.
  • [0213]
    Once the Utility Tool has interrogated the schema to determine all foreign keys for every table in the database, all parent-child relationships for all entities have been defined in terms of the metadata.
  • Entity Search Paths
  • [0214]
    The Utility Tool sets the default search path for each entity during the initial population of the configuration repository. The system administrator can modify this search path at any time. The default search path for an entity is simply the set of all direct relationships with other entities regardless of relationship type. For the Customer Order entity, this would include the following relationships. Please note that reference entities, such as Address and Shipper, are not included in this list of relationships as shown in Table 10:
  • [0000]
    TABLE 10
    Relationship
    CUSTOMER.CUSTOMER_ID=CUSTOMER_ORDER.-
    CUSTOMER_ID
    EMPLOYEE.EMPLOYEE_ID=
    CUSTOMER_ORDER.SALES_PERSON_ID
    CUSTOMER_ORDER.CUSTOMER_ORDER_ID=
    LINE_ITEM.CUSTOMER_ORDER_ID
  • USER INTERFACE GENERATION
  • [0215]
    Key components of the UI, as outlined in the USER INTERFACE ARCHITECTURE section, will now be discussed with respect to the method by which they are dynamically generated from metadata at run-time. Several attributes of entities and entity relationships will be presented during this discussion. Attributes are used to customize and modify the behavior of the UI without the necessity of writing computer code. Other attributes exist for entities and entity relationships. Many of these will be discussed in the APPLICATION EXTENSIBILITY, UTILITY TOOL OPERATION and the USER INTERFACE OPERATION sections.
  • View Menu
  • [0216]
    The Show On View Menu entity attribute determines whether an entity appears on the View Menu. The order of entities with respect to one another is determined by the Relative Order entity attribute. The Reference Tables menu option appears if at least one reference entity exists. An entity may be hidden entirely from end users by setting its Visible attribute to FALSE.
  • Parent Entities
  • [0217]
    An entity may become a parent by: (1) selecting the entity from the View Menu or (2) promoting a child entity. The list of child entities with respect to the parent entity is derived from the set of entity relationships defined in the metadata for the parent. Excluded from this list are entity relationships where: (1) the Visible entity relationship attribute is set to FALSE or (2) the related entity is a reference entity.
  • [0218]
    The name of a child entity, defined by the Caption entity relationship attribute, is initially set to the name of the related entity. Entity names are defined by the Caption entity attribute. The Caption entity relationship attribute may be customized, as is the case for the child entity, Sales Person, in FIG. 35. The related entity is Employee. However, since the role Employee plays relative to a Customer Order is to act as a Sales Person, the Caption attribute has been changed accordingly.
  • [0219]
    As illustrated in the USER INTERFACE ARCHITECTURE section, two methods are provided to search for instances (i.e. records) of the parent entity. The implementation of each method follows:
  • [0220]
    1. Quick-Text Search: The example of a quick-text search presented in the USER INTERFACE ARCHITECTURE section provided for a flexible search against both parent and child entities. The collection of searchable columns is defined by the metadata associated with entities and entity relationships.
  • [0221]
    For the parent entity, the existence of one or more “entity search columns” in the metadata limits the scope of the search to include only those predefined columns. If no entity search columns are defined for the parent, all columns are searchable using the BEGINS search type.
  • [0222]
    On the other hand, child entities are only searchable if one or more “entity relationship search columns” is defined in the metadata. In addition, in order to be searchable, a child entity must be on the search path of the parent entity. In the example presented in FIG. 27, the ProductName column for the Line Item entity is the only search column defined for any of the child entities. Thus, Line Item is the only searchable child entity.
  • [0223]
    The strategy employed by the quick-text search is to first generate SQL against the parent entity and then join it to SQL generated against searchable child entities using the UNION SQL keyword. Search columns defined for both parent and child entities are used to build WHERE clauses for each individual SQL statement. Consider the following SQL generated for the example in FIG. 27:
  • [0000]
    SELECT CUSTOMER_ORDER_V.*
    FROM CUSTOMER_ORDER_V
    WHERE ((CUSTOMER_ORDER_V.CustomerName Like ‘%chai%’)
      OR (CUSTOMER_ORDER_V.SalesPerson Like ‘%chai%’))
    UNION
    SELECT CUSTOMER_ORDER_V.*
    FROM CUSTOMER_ORDER_V,CUSTOMER_ORDER,LINE_ITEM,
    LINE_ITEM_V
    WHERE (CUSTOMER_ORDER_V.CUSTOMER_ORDER_ID=
      CUSTOMER_ORDER.CUSTOMER_ORDER_ID
     AND CUSTOMER_ORDER.CUSTOMER_ORDER_ID=
     LINE_ITEM.CUSTOMER_ORDER_ID
     AND LINE_ITEM_V.LINE_ITEM_ID=LINE_ITEM.-
     LINE_ITEM_ID) AND (LINE_ITEM_V.ProductName
      Like ‘%chai%’)
    ORDER BY CUSTOMER_ORDER_V.CustomerName ASC,
     CUSTOMER_ORDER_V.OrderDate DESC
  • [0224]
    The first portion of the SQL statement, before the UNION keyword, is straightforward. The entity search columns are used to build the WHERE clause.
  • [0225]
    The second portion of the SQL statement, which follows the UNION keyword, is a bit more complex. Notice that the SELECT clause must match that of the first portion of the SQL statement:
  • [0226]
    SELECT CUSTOMER_ORDER_V.*
  • [0227]
    However, since we need to search against the columns of the view associated with the child entity, we must join the parent entity view, CUSTOMER_ORDER_V, with the child entity view, LINE_ITEM_V. These joins make up the first portion of the WHERE clause. To generate these joins, we must first join the views with their associated tables:
  • [0000]
    CUSTOMER_ORDER_V.CUSTOMER_ORDER_ID=
    CUSTOMER_ORDER.CUSTOMER_ORDER_ID
    LINE_ITEM_V.LINE_ITEM_ID=LINE_ITEM.LINE_ITEM_ID
  • [0228]
    The tables themselves are then linked using entity relationship metadata, which defines the physical relationship between the Customer Order and Line Item entities:
  • [0229]
    CUSTOMER_ORDER.CUSTOMER_ORDER_ID=LINE_ITEM.CUSTOMER_ORDER_ID
  • [0230]
    The remainder of the WHERE clause is generated using the entity relationship search column metadata associated with the Line Item entity:
  • [0231]
    LINE_ITEM_V.ProductName Like ‘%chai%’
  • [0232]
    Finally, the ORDER BY clause is generated by interpreting the metadata stored for “entity sort columns”. Entity sort columns are a collection of columns from the associated entity view where a default sort order has been defined (i.e. ascending or descending):
  • [0000]
    ORDER BY CUSTOMER_ORDER_V.CustomerName ASC,
     CUSTOMER_ORDER_V.OrderDate DESC
  • [0233]
    The preceding strategy works fine for parent and child entities that are directly linked, as is the case for One-To-Many and Many-To-One relationships. The strategy for Many-To-Many relationships must consider the fact that a level of indirection exists between parent and child entities, as is the case for the example in FIG. 36, which illustrates a search for Employees who speak German. The SQL statement for this search follows:
  • [0000]
    SELECT EMPLOYEE_V.*
    FROM EMPLOYEE_V
    WHERE (EMPLOYEE_V.EmployeeName Like ‘%German%’)
    UNION
    SELECT EMPLOYEE_V.*
    FROM EMPLOYEE_V, EMPLOYEE,-
    EMPLOYEE_SPOKEN_LANGUAGE,SPOKEN_LANGUAGE
      SPOKEN_LANGUAGE_1, SPOKEN_LANGUAGE_V
    WHERE (EMPLOYEE_V.EMPLOYEE_ID=
    EMPLOYEE.EMPLOYEE_ID
     AND EMPLOYEE.EMPLOYEE_ID=
     EMPLOYEE_SPOKEN_LANGUAGE.EMPLOYEE_ID
     AND SPOKEN_LANGUAGE_1.SPOKEN_LANGUAGE_ID=
       EMPLOYEE_SPOKEN_LANGUAGE.-
       SPOKEN_LANGUAGE_ID
     AND SPOKEN_LANGUAGE_V.SPOKEN_LANGUAGE_ID=
       SPOKEN_LANGUAGE_1.SPOKEN_LANGUAGE_ID)
     AND (SPOKEN_LANGUAGE_V.SpokenLanguage
     Like ‘%German%’)
    ORDER BY EMPLOYEE_V.EmployeeName ASC
  • [0234]
    The first portion of the SQL statement, before the UNION keyword, follows the same format presented in the previous example. The second portion of the SQL statement makes use of additional metadata defined for Many-To-Many entity relationships in order to insert the EMPLOYEE_SPOKEN_LANGUAGE intersection table into the tables joins. The relationship between the Employee and Employee Spoken Language entities, stored as metadata, is defined in such a way that the UI software knows to “map” the Employee Spoken Language entity to the Spoken Language entity. Mapping entities in this manner notifies the UI to insert one additional relationship into the table joins, in this case, the relationship between the Employee Spoken Language and Spoken Language entities.
  • [0235]
    2. Advanced Searching: Advanced searching is accessed through the “Find @E (Advanced)” menu option (where @E is a placeholder for the name of the entity as in “Find Customer Order (Advanced)”) for the parent entity menu context. The list of searchable entities on the left side of the screen is generated by interpreting the search path defined for the parent entity in the following way:
  • [0236]
    Each table join is parsed to determine the “table aliases” on each side of the join. The table alias is the same name as the physical table for entities that have not been aliased. Otherwise, it is the name of the physical table with an appended number to indicate the instance of the alias. This insures all table aliases are unique. For example, aliasing the Customer entity to distinguish between international and domestic Customers would generate the table alias CUSTOMER_1 for the new International Customer entity. The table alias is then used to index into the entity metadata to determine the entity names to use in the generation of the list of searchable entities on the left side of the screen. In this way, indirectly related entities will be included in the list of searchable entities as in the example in FIG. 37, which has been derived from the following search path in Table 11 for the Customer Order entity:
  • [0000]
    TABLE 11
    Search Path Table Joins
    CUSTOMER.CUSTOMER_ID=CUSTOMER_ORDER.-
    CUSTOMER_ID
    CUSTOMER_ORDER.CUSTOMER_ORDER_ID=
    LINE_ITEM.CUSTOMER_ORDER_ID
    CUSTOMER_ORDER.SALES_PERSON_ID=
    EMPLOYEE.EMPLOYEE_ID
    PRODUCT.PRODUCT_ID=LINE_ITEM.PRODUCT_ID
  • [0237]
    Once the list of searchable entities has been generated, the user may begin creating filters for columns within searchable entities. In the example, a list of filters is presented on the right side of the screen.
  • [0238]
    Several points are worth noting with regard to this list of filters. First, there are five individual filters defined each of which is conjoined to its predecessor by use of a logical AND or OR operator. Each filter references a column from an entity using the following format: Entity.Column. Thus, Customer Order.OrderDate refers to the OrderDate column from the Customer Order entity.
  • [0239]
    Indentation indicates order of precedence to insure parentheses are inserted into the translated SQL according to the wishes of the end user. Notice the affect of indentation on the translated SQL for the set of filters defined in the example:
  • [0000]
    (
    ((CUSTOMER_V.BillCountry = ‘Germany’) OR
    (CUSTOMER_V.BillCity = ‘London’))
    AND (PRODUCT_V.ProductCategory IN (‘Produce’,‘Seafood’))
    AND (EMPLOYEE_V.Manager LIKE ‘Fuller%’)
    AND (CUSTOMER_ORDER_V.OrderDate
    BETWEEN ‘1-1-1998’ AND ‘12-31-1998’))
    )
  • [0240]
    The translated SQL should ultimately produce a list of Customer Orders where the bill was sent to either the city of London or the country of Germany for all orders entered during 1998 where the sales person was managed by someone with a last name of Fuller and where one or more products on the order belong to the Produce or Seafood product categories.
  • [0241]
    Before looking at the strategy used to generate the complete SQL statement, please refer to FIG. 38, which illustrates the method by which end users define filters. A Filter screen is presented for the column on which the user has decided to filter. Here, the ProductCatgory from the Customer Order entity has been selected. The caption of this screen indicates the type of filter appropriate for the selected column. In this case, the type of filter for the ProductCatgory column is Text. Number and Date filters are also available. The list of Operators available depends on the filter type. Most operators, such as the “Contains” Text operator, accept a single operand that is entered into the Value 1 field. Other operators, such as “Between”, require two operands, which are entered into the Value 1 and Value 2 fields. Still other operators, such as Is In List, require the selection of one or more discreet values from the underlying view. The ProductCategory makes use of the Is In List operator.
  • [0242]
    The strategy used to build the entire SQL statement follows:
  • [0243]
    1. Add the view and table associated with the parent entity to the FROM clause. Add the join between the table and view to the WHERE clause.
  • [0244]
    2. For each entity that is not the focus of the search (i.e. is not the parent entity), but has been referenced in one or more filters, add the entity's associated table and view to both the FROM and WHERE clauses as in the previous step.
  • [0245]
    If an entity has been aliased, then the table and table alias are used in the FROM clause and the table alias is used in the WHERE clause. For example, to join the International Customer entity (described earlier) with the Customer Order entity, the FROM and WHERE clauses would be as follows:
  • [0000]
    FROM: CUSTOMER CUSTOMER_1, CUSTOMER_ORDER
    WHERE: CUSTOMER_1.CUSTOMER_ID=CUSTOMER_ORDER.-
    CUSTOMER_ID
  • [0246]
    3. For each entity that is not the focus of the search but has been referenced in one or more filters, join the entity's associated table with the table associated with the parent entity. For the Product entity, this would produce the following table joins with respect to the Customer Order parent entity:
  • [0000]
    CUSTOMER_ORDER.CUSTOMER_ORDER_ID=
    LINE_ITEM.CUSTOMER_ORDER_ID
    PRODUCT.PRODUCT_ID=LINE_ITEM.PRODUCT_ID
  • [0247]
    This list may produce redundancy where the same table joins are generated for more than one entity with respect to the Customer Order parent entity.
  • [0248]
    4. Remove redundancy from the previous step and append the resulting list of joins to the WHERE clause.
  • [0249]
    5. Append the translated SQL for the list of filters to the WHERE clause.
  • [0250]
    6. Define the SELECT clause by selecting the primary key column from the view associated with the parent entity:
  • [0251]
    SELECT CUSTOMER_ORDER_V.CUSTOMER_ORDER_ID
  • [0252]
    7. Nest the entire SQL statement (generated by appending the SELECT, FROM, and WHERE clauses) inside of an outer SQL statement which follows the following format relative to the example:
  • [0000]
    SELECT CUSTOMER_ORDER_V.*
    FROM CUSTOMER_ORDER_V
    WHERE CUSTOMER_ORDER_V.CUSTOMER_ORDER_ID IN
    (SQL statement from first 7 steps)
    ORDER BY CUSTOMER_ORDER_V.CustomerName ASC,
     CUSTOMER_ORDER_V.OrderDate DESC
  • [0253]
    This general format insures that a list of Customer Orders is returned as the result set regardless of the entities selected in the list of filters. The ORDER BY clause is derived from the entity sort column metadata for the parent entity.
  • [0254]
    8. The final SQL generated by the advanced search is as follows:
  • [0000]
    SELECT CUSTOMER_ORDER_V.*
    FROM CUSTOMER_ORDER_V
    WHERE CUSTOMER_ORDER_V.CUSTOMER_ORDER_ID IN
    (
    SELECT CUSTOMER_ORDER_V.CUSTOMER_ORDER_ID
    FROM CUSTOMER_ORDER_V, CUSTOMER_ORDER, CUSTOMER, CUSTOMER_V, LINE_ITEM,
      PRODUCT, PRODUCT_V, EMPLOYEE, EMPLOYEE_V
    WHERE CUSTOMER_ORDER_V.CUSTOMER_ORDER_ID=
      CUSTOMER_ORDER.CUSTOMER_ORDER_ID AND
      CUSTOMER.CUSTOMER_ID=CUSTOMER_ORDER.CUSTOMER_ID
     AND CUSTOMER_V.CUSTOMER_ID=CUSTOMER.CUSTOMER_ID
     AND CUSTOMER_ORDER.CUSTOMER_ORDER_ID=LINE_ITEM.CUSTOMER_ORDER_ID
     AND PRODUCT.PRODUCT_ID=LINE_ITEM.PRODUCT_ID
     AND PRODUCT_V.PRODUCT_ID=PRODUCT.PRODUCT_ID
     AND EMPLOYEE.EMPLOYEE_ID=CUSTOMER_ORDER.SALES_PERSON_ID
     AND EMPLOYEE_V.EMPLOYEE_ID=EMPLOYEE.EMPLOYEE_ID
     AND (((CUSTOMER_V.BillCountry = ‘Germany’) OR (CUSTOMER_V.BillCity = ‘London’))
     AND (PRODUCT_V.ProductCategory IN (‘Produce’,‘Seafood’))
     AND (EMPLOYEE_V.Manager LIKE ‘Fuller%’)
     AND (CUSTOMER_ORDER_V.OrderDate BETWEEN ‘1-1-1998’ AND ‘12-31-1998’))
    )
    ORDER BY CUSTOMER_ORDER_V.CustomerName ASC,
      CUSTOMER_ORDER_V.OrderDate DESC
  • Child Entities
  • [0255]
    Once a set of parent entity records has been retrieved using one of the search methods described above, data lists may be generated for child entities. Each time the end user selects a child entity a data list is created by applying a filter to the view associated with the child. The filter is based on the currently selected record for the parent entity. The filter strategy depends on the relationship between the parent and child entities:
  • [0256]
    One-To-Many
  • [0257]
    The general form for dynamic filtering of data lists for One-To-Many relationships follows:
      • SELECT C_V.*
      • FROM C_V, C
      • WHERE C_V.PK=C.PK AND C.FK={P.PK}
      • Where: C_V =View associated with the child entity
        • C=Table associated with the child entity
        • P=Table associated with the parent entity
        • PK=Primary key
        • FK=Foreign key
        • {P.PK}=Primary key value for the currently selected parent record
  • [0267]
    For the Customer Order—Line Item parent-child relationship, the following SQL is generated:
  • [0000]
    SELECT LINE_ITEM_V.*
    FROM LINE_ITEM_V, LINE_ITEM
    WHERE LINE_ITEM_V.LINE_ITEM_ID =
    LINE_ITEM.LINE_ITEM_ID
     AND LINE_ITEM.CUSTOMER_ORDER_ID = 10507
    ORDER BY LINE_ITEM_V.CustomerName ASC,
    LINE_ITEM_V.OrderNumber ASC
  • Many-To-One
  • [0268]
    The general form for dynamic filtering of data lists for Many-To-One relationships follows:
  • [0269]
    SELECT C_V.*
  • [0270]
    FROM C_V, P
  • [0271]
    WHERE C_V.PK=P.FK AND P.PK={P.PK}
  • [0000]
    For the Customer Order—Customer parent-child relationship, the following SQL is generated:
  • [0000]
    SELECT CUSTOMER_V.*
    FROM CUSTOMER_V, CUSTOMER_ORDER
    WHERE CUSTOMER_V.CUSTOMER_ID=
    CUSTOMER_ORDER.CUSTOMER_ID
     AND CUSTOMER_ORDER.CUSTOMER_ORDER_ID = 10507
    ORDER BY CUSTOMER_V.CustomerName ASC
  • Many-To-Many
  • [0272]
    The general form for dynamic filtering of data lists for Many-To-Many relationships follows:
  • [0273]
    SELECT C.PK, M_V.*
  • [0274]
    FROM M_V, C
  • [0275]
    WHERE M_V.PK=C.FK1 AND C.FK2={P.PK}
  • [0276]
    Where: M_V=The view associated with the “maps-to-entity”. In the context of the Many-To-Many relationship between the Employee and Spoken Language entities, the child entity corresponds to the Employee Spoken Language entity and the maps-to-entity is Spoken Language.
  • [0000]
    For the Employee—Spoken Language parent-child relationship, the following SQL is generated:
  • [0000]
    SELECT EMPLOYEE_SPOKEN_LANGUAGE.-
      EMPLOYEE_SPOKEN_LANGUAGE_ID,
      SPOKEN_LANGUAGE_V.*
    FROM EMPLOYEE_SPOKEN_LANGUAGE ,
    SPOKEN_LANGUAGE_V
    WHERE EMPLOYEE_SPOKEN_LANGUAGE.-
    SPOKEN_LANGUAGE_ID =
      SPOKEN_LANGUAGE_V.SPOKEN_LANGUAGE_ID
     AND EMPLOYEE_SPOKEN_LANGUAGE.EMPLOYEE_ID = 7
    ORDER BY SPOKEN_LANGUAGE_V.SpokenLanguage ASC
  • [0277]
    For One-To-Many child entities, a special menu option exists to allow filtering of the child data list. This menu option is called “Filter @E Records”, where @E is a placeholder for the name of the child entity. Since the purpose of the present invention is to provide a generic interface to any relational database, one never knows how many records might exist for a particular instance of a data list participating in a One-To-Many relationship. The “Filter @E Records” menu option uses the same screen illustrated during the discussion on advanced searching only for a slightly different purpose; that is, to filter a data list.
  • [0278]
    The “Promote @E” menu option, available for all child menu contexts, provides access to the promotion functionality discussed in the USER INTERFACE ARCHITECTURE.
  • Menus and Menu Contexts
  • [0279]
    The use of dynamically generated menus to invoke navigation and data entry functionality was discussed in the USER INTERFACE ARCHITECTURE section. This provides a method by which the UI software can dynamically adapt menu options according to where an entity exists within the UI architecture at any given point in time.
  • [0280]
    As mentioned under the USER INTERFACE ARCHITECTURE section, permissions are granted at the menu option level. Permissions might be revoked for security reasons. For example, it may be desirable to define a user group that has limited access to data entry features, but is allowed to search and view data. Another reason for revoking permissions is to provide a more intuitive data entry experience for end users. Since the UI architecture is designed to work with any relational database, given the overall business purpose behind the database, end users may not find certain menu options particularly intuitive or useful. To avoid confusion, these menu items can simply be disabled.
  • [0281]
    Following are a series of tables, grouped by menu context, which summarize the menu options available for each menu context. The “@E” symbol serves as a placeholder for the name of the entity. For child menu contexts, the “@P” symbol serves a placeholder for the name of the parent entity. Several of the menu options listed below in Table 12 through Table 16 will be illustrated under the USER INTERFACE OPERATION section:
  • Parent Context
  • [0282]
  • [0000]
    TABLE 12
    Menu Option Description
    New @E Record Adds a new record using a data entry form.
    Duplicate @E Record Creates a new record by copying forward data from the selected record into
    a data entry form.
    Edit @E Record Loads the selected record into a data entry form for editing.
    Delete @E Record(s) Deletes the selected records from the database, subject of course to
    referential integrity rules.
    View @E Record Loads the selected record into a data entry form for viewing. The data entry
    form is placed in read-only mode.
    Export @E Record(s) Exports the entire data list to one of several file formats using an export
    wizard.
    Print Preview Loads the data list into a print preview screen from where it can then be
    printed.
    Print Report Generates a custom report, such as a nicely formatted invoice, by passing
    the primary key of the selected record to a report writer using COM. For
    more information, see the APPLICATION EXTENSIBILITY section.
    Find @E (Advanced) Loads the advanced searching screen.
    Find @P Uses a COM interface to load an external component that will provide a
    custom search screen. For more information, see the APPLICATION
    EXTENSIBILITY section.
    Display Data Entry Grid Loads the data list into a data entry grid for editing. For more information on
    data entry grids, see the Data Entry Forms subsection under the USER
    INTERFACE GENERATION section.
  • Reference Context
  • [0283]
  • [0000]
    TABLE 13
    Menu Option Description
    New @E Record Adds a new record using a data entry form.
    Duplicate @E Record Creates a new record by copying forward data from the selected record into
    a data entry form.
    Edit @E Record Loads the selected record into a data entry form for editing.
    Delete @E Record(s) Deletes the selected records from the database, subject of course to
    referential integrity rules.
    View @E Record Loads the selected record into a data entry form for viewing. The data entry
    form is placed in read-only mode.
    Export @E Record(s) Exports the entire data list to one of several file formats using an export
    wizard.
    Print Preview Loads the data list into a print preview screen from where it can then be
    printed.
    Display Data Entry Grid Loads the data list into a data entry grid for editing. For more information on
    data entry grids, see the Data Entry Forms subsection under the USER
    INTERFACE GENERATION section.
  • One-to-Many Context
  • [0284]
  • [0000]
    TABLE 14
    Menu Option Description
    New @E Record Adds a new record using a data entry form. The foreign key field, which
    relates the entity to its parent, is automatically populated with the primary
    key value from the currently selected parent record.
    Duplicate @E Record Creates a new record by copying forward data from the selected record into
    a data entry form.
    Edit @E Record Loads the selected record into a data entry form for editing.
    Delete @E Record(s) Deletes the selected records from the database, subject of course to
    referential integrity rules.
    Link Selected @E Loads a simple search screen to allow the end user to select a different
    Record(s) with a Different parent record in which to link the currently selected child. The foreign key
    @P Record field in the child will be updated.
    Unlink the Selected @E Sets the foreign key field of the child entity to NULL, subject of course to
    Record(s) from the @P referential integrity rules.
    Record
    View @E Record Loads the selected record into a data entry form for viewing. The data entry
    form is placed in read-only mode.
    Export Record(s) Exports the entire data list to one of several file formats using an export
    wizard.
    Print Preview Loads the data list into a print preview screen from where it can then be
    printed.
    Filter @E Records Loads the same screen used for advanced searching. However, the filters
    defined are simply applied to the data list to limit the number of visible
    records.
    Promote @E Promotes the selected child entity, including the data list, into a new screen
    where the child becomes the parent entity.
    Display Data Entry Grid Loads the data list into a data entry grid for editing. For more information on
    data entry grids, see the Data Entry Forms subsection under the USER
    INTERFACE GENERATION section.
  • Many-to-One Context
  • [0285]
  • [0000]
    TABLE 15
    Menu Option Description
    New @E Record Adds a new record using a data entry form. If successfully saved, the new
    primary key value will be used to update the foreign key field of the currently
    selected parent record.
    Duplicate @E Record Creates a new record by copying forward data from the selected record into
    a data entry form. If successfully saved, the new primary key value will be
    used to update the foreign key field of the currently selected parent record.
    Edit @E Record Loads the selected record into a data entry form for editing.
    Delete @E Record(s) Deletes the selected records from the database, subject of course to
    referential integrity. The delete will fail unless the database is configured to
    cascade deletes since deleting the child in this context necessitates deletion
    of the parent record.
    Link the @P Record with Loads a simple search screen to allow the end user to select a different child
    a Different @E Record record in which to link the currently selected parent record. In this context,
    the foreign key field of the parent entity will be updated.
    Unlink the @P Record Sets the foreign key field of the parent entity to NULL, subject of course to
    from the Selected @E referential integrity rules.
    Record
    View @E Record Loads the selected record into a data entry form for viewing. The data entry
    form is placed in read-only mode.
    Export Record(s) Exports the entire data list to one of several file formats using an export
    wizard.
    Print Preview Loads the data list into a print preview screen from where it can then be
    printed.
    Promote @E Promotes the selected child entity, including the data list, into a new screen
    where the child becomes the parent entity.
    Display Data Entry Grid Loads data list into a data entry grid for editing. For more information on
    data entry grids, see the Data Entry Forms subsection under the USER
    INTERFACE GENERATION section.
  • Many-to-Many
  • [0286]
  • [0000]
    TABLE 16
    Menu Option Description
    New @E Record Loads a data entry form for the “maps-to-entity”. The maps-to-entity is the
    entity to which the parent is indirectly related (e.g. Employee to Spoken
    Language). The placeholder, “@E”, corresponds to the maps-to-entity. If
    successfully saved, an additional record will be inserted into the intersection
    table which links the parent and maps-to-entities (e.g.
    EMPLOYEE_SPOKEN_LANGUAGE).
    Duplicate @E Record Creates a new record by copying forward data for the maps-to-entity from
    the selected record into a data entry form. If successfully saved, an
    additional record will be inserted into the intersection table which links the
    parent and maps-to-entities.
    Edit @E Record Loads the selected record for the maps-to-entity into a data entry form for
    editing.
    Delete @E Record(s) Deletes the selected records for the maps-to-entity from the database,
    subject of course to referential integrity rules. Before deleting the maps-to-
    entity records, the related records from the intersection table are deleted.
    Link the Selected @P Loads the simple search screen for the maps-to-entity. For each record
    Record with a @E selected from the maps-to-entity, a corresponding record is inserted into the
    Record(s) intersection table thus linking the parent and maps-to-entities.
    Unlink the @P Record Deletes the selected records from the intersection table which links the
    from the Selected @E parent and maps-to-entities.
    Record(s)
    View @E Record Loads the selected record (for the maps-to-entity) into a data entry form for
    viewing. The data entry form is placed in read-only mode.
    Export Record(s) Exports entire data list to one of several file formats using an export wizard.
    Print Preview Loads the data list into a print preview screen from where it can then be
    printed.
    Promote @E Promotes the selected child entity, including the data list, into a new screen
    where the child becomes the parent entity.
    Display Data Entry Grid Loads data list into a data entry grid for editing. For more information on
    data entry grids, see the Data Entry Forms subsection under the USER
    INTERFACE GENERATION section.
  • Data Entry Forms
  • [0287]
    Data entry forms consist of an ordered collection of data entry controls derived from metadata relating to entity fields. The general strategy is to validate as much data as possible while the end user enters data into each of the data entry controls. For example, the DateTimeControl control type, which presents a graphical image of a calendar to the end user, will not permit an invalid date to be entered. Similarly, the ComboBoxControl, implemented graphically as a drop-down list, will only accept valid foreign key values from the list.
  • [0288]
    When the user decides to save a record to the database, the Required entity field attribute is used to insure all required data has been entered. Business rules, discussed below, may be defined to provide further data validation.
  • [0289]
    Entity and entity field scripting, using language such as VBScript and JavaScript, are also available to implement data validation or other desired functionality. Form-level events, such as FormLoad, BeforeSave, and AfterSave, are triggered at run-time. Scripting may be attached to these events to provide custom functionality. Some events provide a mechanism for canceling further processing. For instance, before saving a new Line Item to the database, suppose the system administrator wants to insure there is sufficient inventory on hand to fill the order. The following VBScript might be entered in the BeforeSave event. Notice that if sufficient inventory is not on hand, setting the Cancel argument to TRUE prevents further processing:
  • [0000]
    Public Sub LINE_ITEM_BeforeSave(Cancel)
     Dim SQL
     Dim rs
     Dim Message
     ‘If entering a new Line Item, check the affect on inventory by building an SQL statement
     ‘using the Quantity and Product fields from the data entry form.
     If Application.NewRecord Then
      SQL = “SELECT * FROM PRODUCT WHERE (UNITS_IN_STOCK - ”
      SQL = SQL & Application.Fields(“QUANTITY”).Value & ”) <= 0 “
      SQL = SQL & “AND PRODUCT_ID = “& Application.Fields(“PRODUCT_ID”).Value
      ‘Create a recordset object using ADO to store the query results.
      Set rs = CreateObject(“ADODB.Recordset”)
      ‘Get a connection to the database.
      Set rs.Activeconnection = Application.DBConnection
      rs.Open SQL
      ‘If a record is returned in the result set, it means the inventory is too low.
      If Not (rs.BOF And rs.EOF) Then
       Message = “There is insufficient inventory on hand. ”
       Message = Message & “This line item cannot be added to the order.”
       ‘Present a message to the user.
       MsgBox Message, vbOkOnly + vbInformation, “Insufficient Inventory”
       ‘Cancel further processing of events.
       Cancel = TRUE
      End If
      rs.Close
      Set rs = Nothing
     End If
    End Sub
  • [0290]
    Script may also be attached to entity field events such as OnChange. The OnChange event is triggered when the value in a data entry control changes.
  • [0291]
    In addition to data validation, the present embodiment provides access to a limited programmable interface, or object model as it is frequently referred to, to perform various tasks such as enabling and disabling, or showing and hiding, data entry controls at run-time. Future embodiments should provide a more robust object model. However, a reasonable balance must be maintained between the use of metadata attributes to modify run-time behavior and the integration of scripting to achieve the same affect. Even though scripting is stored as metadata in the configuration repository, and does not require recompilation and redeployment of the UI software when changes are made, it is nonetheless computer code. Remember, the underlying premise of the present invention is that computer code is extremely expensive to develop and maintain.
  • [0292]
    Once the data entry form has been validated, SQL is generated to update the underlying database table using entity and entity field metadata in conjunction with the values stored in each data entry control. Saving the new Line Item record depicted in FIG. 39 would generate the following SQL statement:
  • [0000]
    INSERT INTO LINE_ITEM (LINE_ITEM_ID,
     CUSTOMER_ORDER_ID, PRODUCT_ID, QUANTITY,
     DISCOUNT, EXTENDED_PRICE) VALUES( 2186,
     10355, 3, 10, 0.1, 90.00)
  • [0293]
    Occasionally, it may be preferable to have end users enter data into a grid-like data entry form where multiple records can be edited on a single screen. A special menu option, “Display Data Entry Grid”, provides access to this type of functionality. FIG. 40 illustrates such a data entry grid for the Line Item entity. The functionality is nearly identical to that of the normal data entry form with the primary exception being that a record is saved when the focus shifts from one record to another as opposed to clicking a button.
  • Data Entry Controls
  • [0294]
    Several data entry controls are available to collect input from end users. Each of these controls is designed to provide an intuitive data entry experience using many of the same graphical constructs to which users have grown accustomed. Where possible, the data entry controls validate input to protect the integrity of the underlying database. An overview of each control type will now be presented to provide the reader with a better understanding of how data is collected from end users. Please note that future embodiments of the present invention should expand upon the following selection of control types to provide a wider variety of preprogrammed controls, thus eliminating the need for custom data entry forms. (Integrating custom data entry forms into the UI is discussed in the APPLICATION EXTENSIBILTY section):
  • CalculatedControl
  • [0295]
    The CalculatedControl is a read-only data entry control designed to derive a value from the underlying database and display the value on the data entry form. A CalculatedControl is “bound” if it maps to a field in the physical table associated with the entity and “unbound” if the derived value is not stored in the underlying table. As with the ComboBoxControl and SmartComboControl controls, three Expression Types are available to derive the calculated value: EXPRESSION, SQL, and STORED_PROCEDURE. Regardless of Expression Type, the execution of the corresponding Expression attribute at run-time should return a single value.
  • [0296]
    Two CalculatedControls are present on the Line Item data entry form in FIG. 41. The Unit Price simply displays the Unit Price for the currently selected Product. Notice that a UNIT_PRICE field does not exist in the LINE_ITEM table. The unbound UNIT_PRICE field has been added to the Line Item entity metadata. The SQL Expression Type has been defined and the following Expression is evaluated at run-time to derive the value displayed in the control:
  • [0297]
    SELECT UNIT_PRICE FROM PRODUCT WHERE PRODUCT_ID={PRODUCT_ID}
  • [0298]
    The parameter passed within the curly brackets simply tells the UI software to insert the value of the PRODUCT_ID foreign key field (i.e. the currently selected Product on the Line Item record) into the SQL statement. The value returned from this SQL statement is then inserted into the Unit Price data entry control.
  • [0299]
    The second CalculatedControl control on the Line Item form is used to calculate the Extended Price. The Extended Price is bound to the EXTENDED_PRICE field in the LINE_ITEM table. Here, the STORED_PROCEDURE Expression Type is used and the following Expression is evaluated at run-time:
  • [0300]
    stpExtendedPrice {PRODUCT_ID}, {QUANTITY}, {DISCOUNT}
  • [0301]
    The values from Product, Quantity, and Discount fields on the Line Item are passed from the data entry form to the stored procedure, “stpExtendedPrice”. An output parameter is then used by the stored procedure to return a value back to the UI software.
  • CheckBox
  • [0302]
    The CheckBox, depicted in FIG. 42, is designed to represent Boolean fields. A graphical image of check box is presented to the end user. Clicking the box toggles the value from TRUE, when the box is checked, to FALSE, when the box is not checked.
  • ComboBoxControl
  • [0303]
    The ComboBoxControl was discussed in the METADATA GENERATION section. A couple additional features add to the control's versatility. These features are implemented through the entity field attributes shown in Table 17:
  • [0000]
    TABLE 17
    Attribute Description
    Allow Edit Set the Allow Edit attribute to TRUE to allow entry of new values into the dropdown list
    by adding a new record to the related entity. FIGS. 43-45 illustrate the process of
    adding a new Shipper while entering a Customer Order record.
    Limit To List By default, this attribute is set to TRUE and the user must select an item from the
    dropdown list, as should be the case when using the ComboBoxControl to populate a
    foreign key field. However, by setting this attribute to FALSE, the user can either
    select a value from the list or type a new value directly into the edit box portion of the
    control.
    NOTE: Limit To List should never be set to FALSE for foreign key fields.
    Consider the following scenario: Suppose it is desirable to present a list of countries in
    the Country field of the Address entity. Country is not a foreign key field. Converting
    the Country field from a TextBoxControl to a ComboBoxControl and using the following
    SQL Expression will generate a list of countries:
    SELECT DISTINCT COUNTRY
    FROM ADDRESS
    ORDER BY COUNTRY
  • DateTimeControl
  • [0304]
    The DateTimeControl uses a single attribute to determine whether to accept date or time input from the end user. When the Date Time Control Type attribute is set to DATE_CONTROL, the control will present a calendar to the end user from which a date may be selected (see FIG. 1). Alternatively, the user can simply enter a date into the edit box. However, if the attribute is set to one of four available time formats, such as TIME_CONTROL (01:15 PM), then the user simply enters a time into the edit box. The value entered is validated against the selected format.
  • FileDialogControl
  • [0305]
    Frequently, users need to store the path to a document or image file in a database field. The FileDialogControl is designed to allow users to navigate through their directory structures to select a particular file. The entire path is returned to the control. Setting the File Association attribute to TRUE will create a hyper-link between the path displayed in the control and the computer software associated with the file. For example, if the path to a Microsoft Word document is displayed in the control, clicking the hyper-linked path will load the document into an instance of Word. Operation of the FileDialogControl is illustrated in FIG. 46-48.
  • ImageBLOB
  • [0306]
    The ImageBLOB is very similar to the FileDialogControl. Users can select image files from their directory structures. However, instead of storing the path to the image in the database, a binary copy of the image itself is stored. Obviously, this control type is only appropriate for database fields capable of storing binary large objects (BLOB). Once the image has been stored, a hyper-link may be clicked to load the image as illustrated with the Photo field in the Employee entity (see FIG. 49-50).
  • MaskEditBox
  • [0307]
    The MaskEditBox is designed to provide an input mask for text fields that store formatted data such as social security numbers. The Mask Type attribute defines the type of mask to be used. A few predefined masks are available such as PHONE_MASK and SSN_MASK. The GENERAL_MASK Mask Type is used in combination with the Format entity field attribute to define custom input masks using a set of special characters. For example, setting the Format attribute to “A###” generates an input mask that ensures the first character must be alphanumeric and the last three characters must be digits.
  • [0308]
    The SSN field in the Employee entity uses the SSN_MASK Mask Type as illustrated in FIG. 51.
  • NotesControl
  • [0309]
    The NotesControl eases the entry of large amounts of text by providing multiple lines in the edit box and exposing a button which, when clicked, loads the text into a larger scrollable edit box in a “zoom” screen (see FIG. 52).
  • NumericFormatBox
  • [0310]
    The NumericFormatBox, illustrated in FIG. 53, is a simple edit box that enforces entry of numeric data. The Format entity field attribute may be used to format the data display, such as presenting monetary data using currency symbols.
  • SmartComboControl
  • [0311]
    The SmartComboControl was discussed in some detail under the METADATA GENERATION section. From the end user's perspective, this control type provides two key pieces of functionality summarized in Table 18:
  • [0000]
    TABLE 18
    Feature Description
    Hyper-linking Once the foreign key field has been populated,
    the edit box is hyper-linked to the record from the related
    entity. Clicking the hyper-link loads a data entry
    form for the related entity.
    Modifying the Clicking the button on the right side of the control loads
    foreign key a simple text search screen for the related entity.
    value Selecting a record from the list modifies the foreign key
    value in the underlying data entry form. An example will
    be presented in the USER INTERFACE OPERATION
    section
  • TextBoxControl
  • [0312]
    The TextBoxControl allows open-ended text data entry, such as with a street address. A few entity field attributes provide additional functionality as summarized in Table 19:
  • [0000]
    TABLE 19
    Feature Description
    Email When set to TRUE, this attribute provides a hyper-link
    to the user's default email
    Address program as illustrated in FIG. 54.
    Web Address When set to TRUE, this attribute provides a hyper-link
    to the user's web browser.
    Lines Provides ability to expand the number of lines available
    in the edit box.
  • Auditing
  • [0313]
    Setting the Audit On entity attribute to TRUE invokes auditing against the current entity. Inserts, updates, and deletes to the underlying table are logged to a system-defined table to document when the action occurred and the user responsible for the change.
  • Entity Filters
  • [0314]
    Filters may be defined on the views associated with entities. These filters are part of the metadata relating to entities. Filters are defined at the group level so that different filters may be applied to various groups of users. For example, suppose sales people were divided into two user groups: International Sales and Domestic Sales. The list of Customers with which each group is permitted to work might be filtered on the BillCountry column in the CUSTOMER_V view as the following SQL snippets demonstrate in Table 20:
  • [0000]
    TABLE 20
    Group Filter
    International Sales Group CUSTOMER_V.BillCountry < > ‘United
    States’
    Domestic Sales Group CUSTOMER_V.BillCountry = ‘United States’
  • Entity Business Rules
  • [0315]
    Entity business rules are used to provide edit checks prior to inserts, updates, and deletes to an underlying table. More than one rule may be defined for each entity. The rules are defined using either an SQL statement or a stored procedure. The business rule input screen from the Utility Tool is illustrated in FIG. 55. With the “SQL” Rule Type, a rule is violated if one or more records are returned from the SQL statement when the rule is applied. For the “Stored Procedure” Rule Type, a rule is violated if the output parameter of the stored procedure returns a value of 0.
  • [0316]
    When a business rule is violated, a message is presented to the end user informing them of the violation. Setting the Action Type to “Fatal” means that further processing cannot occur until the violation has been remedied. Setting the Action Type to “Warning” means that the user will have an opportunity to continue processing if they so desire.
  • [0317]
    The Rule Type “Terminator” is used in conjunction with Action Types “Go To Rule” and “Stop” to organize several rules into a control structure similar the “If . . . Then . . . Else . . . ” programming construct.
  • Entity Triggers
  • [0318]
    Entity triggers are SQL statements or Stored Procedures that are executed in conjunction with insert, update, and delete operations against the underlying database. For inserts and updates, the trigger is executed immediately after the operation. For deletes, the trigger is executed prior to the deletion operation. A single trigger may apply to an insert, update, or delete operation, or any combination thereof. Several triggers may be defined for a single entity. The Trigger Number determines the order of execution of each trigger.
  • [0319]
    The trigger input screen from the Utility Tool is illustrated in FIG. 56. This trigger is designed to update inventory after a new Line Item has been saved to the database.
  • Application Extensibility
  • [0320]
    The present invention recognizes the occasional need to integrate custom functionality into the UI. Within the context of the present invention, custom functionality can be broadly characterized as any functionality that falls outside of that provided by the run-time UI executable in combination with the metadata. As demonstrated throughout this document, considerable functionality and flexibility are provided through the careful integration of the UI with metadata stored in the configuration repository. Still, there are occasions where it is desirable to integrate external components with the UI.
  • [0321]
    Over the last several years, various industry-wide specifications have been defined to provide for interaction between different software components. One of the most widely accepted specifications is the Component Object Model (COM). The general idea behind COM is to design various programming interfaces such that Component A can communicate with Component B, and vice versa, without either component understanding the details of the other's internal implementation.
  • [0322]
    One embodiment of the present invention defines a specification for a COM interface that provides for communication between the UI and external software components. Future embodiments might look toward other promising specifications and protocols, such as the Simple Object Access Protocol (SOAP), to provide inter-component communication.
  • [0323]
    The present invention offers several opportunities to integrate external components into the UI. Table 21 summarizes four of the most significant areas where external components can be integrated using a predefined COM interface:
  • [0000]
    TABLE 21
    Area Description
    Custom Data Entry Form Setting the Custom Data Entry entity attribute to TRUE will call an external
    component to load a custom data entry form. In this case, the dynamically
    generated data entry form provided by the UI is replaced with the custom form.
    Custom Search Screen Setting the Custom Filter entity attribute to TRUE will call an external
    component to load a custom search screen. The custom search screen must
    return an SQL statement back to the UI. The SQL statement should be
    structured such that it ultimately returns records from the view associated with
    the parent entity.
    This feature is accessible through the “Find @E” menu option for the parent
    menu context. An example will be illustrated in the UTILITY TOOL
    OPERATION and USER INTERFACE OPERATION sections.
    Reports The parent entity menu context provides for the integration of custom reports
    into the UI. COM interfaces for popular report writers, such as
    BusinessObjects ®, Crystal Reports, and Microsoft Access, are used to
    generate high quality reports within the UI.
    With reference to the example used throughout this document, a custom
    invoice might be designed such that, by passing the CUSTOMER_ORDER_ID
    primary key value to the report, a nicely formatted invoice would be generated.
    The report could then be linked to the Customer Order entity using the Report
    Name, Report Path and Report Type entity attributes.
    Tools Menu The main menu of the UI contains a Tools menu to which external components
    may be attached. Examples of tools that one might wish to integrate into the
    UI are limitless. A common example might be an import tool to allow the
    import of data into the database. An example will be illustrated in the UTILITY
    TOOL OPERATION and USER INTERFACE OPERATION sections.
  • Utility Tool Operation
  • [0324]
    A brief series of illustrated examples of operation of the Utility Tool will now be presented. In FIG. 57, the Utility Tool interface is shown. In FIG. 58, a new configuration repository is created.
  • [0325]
    The screen images presented in FIG. 59 illustrate the process of defining a Datasource. A Datasource simply defines a connection to a relational database; in this case, a Microsoft SQL Server database called CustomerOrders.
  • [0326]
    The Datasource is Refreshed, in FIG. 60, to initiate the process of populating the configuration repository with metadata. The user is prompted to define the reference tables (entities) from the list of tables found in the database schema.
  • [0327]
    In FIG. 61, the Refresh process has completed and the Customer Order entity metadata is shown.
  • [0328]
    In FIG. 62, the default data entry control assigned to the Customer field in the Customer Order entity is changed from a SmartComboControl to a ComboBoxControl. In FIG. 63, the default control assigned to the Address field, which maps to the ADDRESS_ID foreign key field, is changed from a ComboBoxControl to a SmartComboControl.
  • [0329]
    FIG. 64 illustrates the assignment of an icon to the Customer Order entity. When Customer Order is the parent entity on the main screen of the UI, the icon will provide users with a graphical image of the entity. On the Attributes tab, a custom filter is implemented using the COM interface exposed by the UI. Also, a form caption expression is defined to place a meaningful caption on data entry forms.
  • [0330]
    In FIG. 65 and FIG. 66, search columns and sort columns are defined for the Customer Order entity.
  • [0331]
    In FIG. 67, the order of Customer Order relationships is modified to place Line Item at the top of the child list.
  • [0332]
    In FIG. 68, the caption of the Employee relationship is changed to Sales Person.
  • [0333]
    Permissions for the Customer Order entity are assigned to the Sales Reps user group in FIG. 69.
  • [0334]
    The Line Item relationship will appear as a tab on the Customer Order data entry form by setting the Display On Tab attribute to TRUE as illustrated in FIG. 70.
  • [0335]
    In FIG. 71, an unbound CalculatedControl is added to the Line Item entity in order to display the Unit Price on the data entry form. The Extended Price field is modified in FIG. 72 to implement a bound CalculatedControl.
  • [0336]
    A business rule has been defined to check inventory levels before adding a Line Item to a Customer Order (see FIG. 55). A trigger has also been defined to update inventory on hand immediately after a Line Item is added to a Customer Order (see FIG. 56).
  • [0337]
    In FIG. 73, an Application Caption and Startup Entity are defined in the System Attributes screen. The Startup Entity is the first parent entity to appear when end users log into the UI.
  • [0338]
    A tool, “Import Wizard”, is defined in FIG. 74 in order to integrate an external COM component into the UI.
  • [0339]
    Finally, in FIG. 75, an entry is added to a configuration file to notify the UI of the presence of a new configuration repository. The UI software may now use the new configuration repository to generate a user interface.
  • User Interface Operation
  • [0340]
    Many features of the UI have been presented in prior sections of this document. However, continuing with the example in the UTILITY TOOL OPERATION section, the operation of the UI will now be briefly illustrated using the newly created configuration repository from the previous section.
  • [0341]
    In FIG. 76, a user logs into the UI. Notice that more than one configuration repository exists. Since the UI behavior is controlled by metadata, any number of configuration repositories can be used by a single installation of the UI software.
  • [0342]
    In FIG. 77, the Tools menu now displays an “Import Wizard” menu option. Selecting the menu option launches an external COM component (not shown here).
  • [0343]
    An advanced search screen for the Customer Order entity is illustrated in FIG. 78. The default search path configured by the Utility Tool during the Refresh process is used to construct the list of searchable entities.
  • [0344]
    A simple custom filter (search) is illustrated in FIG. 79. The custom filter screen is provided by an external COM component. Changes made to the internal workings of the COM component have no impact on the UI software.
  • [0345]
    In FIG. 80, a new Customer Order is entered. Notice the Line Item tab on the Customer Order data entry form. Also, notice the use of a SmartComboControl to populate the Address field (remember, addresses are stored in a single table and shared by four entities to ensure the same physical address is entered once and only once).
  • [0346]
    A Line Item is added to the new Customer Order in FIG. 81. Notice the presence of the unbound Unit Price CalculatedControl.
  • [0347]
    Promotion of the Sales Person entity is illustrated in FIG. 82. With Employee as the parent, Customer Orders may be entered using the child menu as shown in FIG. 83. Notice that the Sales Person field is automatically populated when the Customer Order data entry screen is first instantiated.
  • [0348]
    In FIG. 84, the CustomerOrders database is modified to add the REQUESTED_DATE field to the CUSTOMER_ORDER table. The configuration repository is Refreshed, in FIG. 85, to generate metadata for the database modification.
  • [0349]
    The new Customer Order data entry form is illustrated in FIG. 86. Notice the Requested Date field now appears and is represented by a DateTimeControl.
  • [0350]
    Although the invention has been described in detail with particular reference to these preferred embodiments, other embodiments can achieve the same results. Variations and modifications of the present invention will be obvious to those skilled in the art and it is intended to cover in the appended claims all such modifications and equivalents. The entire disclosures of all references, applications, patents, and publications cited above are hereby incorporated by reference.

Claims (21)

  1. 1. Computer software for automatically generating a graphical user interface for a relational database, said software embodied in a computer readable medium having a set of computer instructions encoded thereon and comprising:
    utility software extracting schema information from the relational database and automatically generating corresponding schema and graphical user interface metadata comprising entity fields stored in a repository; and
    user interface software at runtime automatically, and without compilation of code before runtime, developing from the metadata a graphical user interface for the relational database.
  2. 2. The computer software of claim 1 wherein said utility software assigns to each entity field a type attribute based on attributes of a corresponding table field in the relational database.
  3. 3. The computer software of claim 2 wherein said utility software assigns to an entity field a numeric format type if the corresponding table field is a primary key.
  4. 4. The computer software of claim 3 wherein said utility software assigns to an entity field a numeric format type if the corresponding table field is a primary key and marks that entity field as read-only so that it is not alterable by an end user.
  5. 5. The computer software of claim 2 wherein said utility software assigns to an entity field a dropdown list type if the corresponding table field is a foreign key.
  6. 6. The computer software of claim 5 wherein said utility software assigns to an entity field a dropdown list type permitting display of values from more than one field if the corresponding table field is a foreign key.
  7. 7. The computer software of claim 2 wherein said utility software assigns to an entity field one of a predetermined set of types if the corresponding table field is neither a primary nor a foreign key.
  8. 8. Computer apparatus for automatically generating a graphical user interface for a relational database, said apparatus comprising:
    means embodied in a computer readable medium having a set of computer instructions encoded thereon for extracting schema information from the relational database and automatically generating corresponding schema and graphical user interface metadata comprising entity fields;
    repository means for containing said metadata; and
    means embodied in a computer readable medium having a set of computer instructions encoded thereon for at runtime automatically, and without compilation of code before runtime, developing from the metadata a graphical user interface for the relational database.
  9. 9. The computer apparatus of claim 8 wherein each entity field in said repository has a type attribute based on attributes of a corresponding table field in the relational database.
  10. 10. The computer apparatus of claim 9 wherein an entity field in said repository has a numeric format type if the corresponding table field is a primary key.
  11. 11. The computer apparatus of claim 10 wherein an entity field in said repository has a numeric format type if the corresponding table field is a primary key and is marked as read-only so that it is not alterable by an end user.
  12. 12. The computer apparatus of claim 9 wherein an entity field in said repository has a dropdown list type if the corresponding table field is a foreign key.
  13. 13. The computer apparatus of claim 12 wherein an entity field in said repository has a dropdown list type permitting display of values from more than one field if the corresponding table field is a foreign key.
  14. 14. The computer apparatus of claim 9 wherein an entity field in said repository has one of a predetermined set of types if the corresponding table field is neither a primary nor a foreign key.
  15. 15. A method of automatically generating a graphical user interface for a relational database, the method comprising the steps of:
    extracting schema information from the relational database and automatically generating corresponding schema and graphical user interface metadata comprising entity fields;
    storing the metadata in a repository; and
    at runtime automatically, and without compilation of code before runtime, developing from the metadata a graphical user interface for the relational database.
  16. 16. The method of claim 15 wherein each entity field in said repository has a type attribute based on attributes of a corresponding table field in the relational database.
  17. 17. The method of claim 16 wherein an entity field in said repository has a numeric format type if the corresponding table field is a primary key.
  18. 18. The method of claim 17 wherein an entity field in said repository has a numeric format type if the corresponding table field is a primary key and is marked as read-only so that it is not alterable by an end user.
  19. 19. The method of claim 16 wherein an entity field in said repository has a dropdown list type if the corresponding table field is a foreign key.
  20. 20. The method of claim 19 wherein an entity field in said repository has a dropdown list type permitting display of values from more than one field if the corresponding table field is a foreign key.
  21. 21. The method of claim 16 wherein an entity field in said repository has one of a predetermined set of types if the corresponding table field is neither a primary nor a foreign key.
US12172614 2001-12-28 2008-07-14 Automated Generation of Dynamic Data Entry User Interface for Relational Database Management Systems Abandoned US20090031230A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US10040851 US7062502B1 (en) 2001-12-28 2001-12-28 Automated generation of dynamic data entry user interface for relational database management systems
US11204799 US7401094B1 (en) 2001-12-28 2005-08-16 Automated generation of dynamic data entry user interface for relational database management systems
US12172614 US20090031230A1 (en) 2001-12-28 2008-07-14 Automated Generation of Dynamic Data Entry User Interface for Relational Database Management Systems

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12172614 US20090031230A1 (en) 2001-12-28 2008-07-14 Automated Generation of Dynamic Data Entry User Interface for Relational Database Management Systems

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11204799 Continuation US7401094B1 (en) 2001-12-28 2005-08-16 Automated generation of dynamic data entry user interface for relational database management systems

Publications (1)

Publication Number Publication Date
US20090031230A1 true true US20090031230A1 (en) 2009-01-29

Family

ID=36576625

Family Applications (3)

Application Number Title Priority Date Filing Date
US10040851 Active 2023-07-11 US7062502B1 (en) 2001-12-28 2001-12-28 Automated generation of dynamic data entry user interface for relational database management systems
US11204799 Active 2022-12-15 US7401094B1 (en) 2001-12-28 2005-08-16 Automated generation of dynamic data entry user interface for relational database management systems
US12172614 Abandoned US20090031230A1 (en) 2001-12-28 2008-07-14 Automated Generation of Dynamic Data Entry User Interface for Relational Database Management Systems

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10040851 Active 2023-07-11 US7062502B1 (en) 2001-12-28 2001-12-28 Automated generation of dynamic data entry user interface for relational database management systems
US11204799 Active 2022-12-15 US7401094B1 (en) 2001-12-28 2005-08-16 Automated generation of dynamic data entry user interface for relational database management systems

Country Status (1)

Country Link
US (3) US7062502B1 (en)

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030159136A1 (en) * 2001-09-28 2003-08-21 Huang Xiao Fei Method and system for server synchronization with a computing device
US20070067710A1 (en) * 2005-09-22 2007-03-22 Clark David K Navigating table data with mouse actions
US20070143398A1 (en) * 2005-12-16 2007-06-21 Jean Graham Central work-product management system for coordinated collaboration with remote users
US20080162553A1 (en) * 2006-12-27 2008-07-03 Rakshit Daga Method and system for generating string-based addresses
US20080162532A1 (en) * 2006-12-27 2008-07-03 Rakshit Daga Method and system for generating relational spreadsheets
US20090248710A1 (en) * 2008-03-27 2009-10-01 Microsoft Corporation Database Part Table Junctioning
US20090327212A1 (en) * 2006-01-09 2009-12-31 Trevor Bell Efficient SQL access to point data and relational data
US20110107243A1 (en) * 2009-11-05 2011-05-05 International Business Machines Corporation Searching Existing User Interfaces to Enable Design, Development and Provisioning of User Interfaces
US20120137359A1 (en) * 2010-11-29 2012-05-31 Groupe Cgi Inc. Method For Storing (Hiding) A Key In A Table And Corresponding Method For Retrieving The Key From The Table
US20120151382A1 (en) * 2010-12-14 2012-06-14 Microsoft Corporation Generating and managing electronic documentation
US20130179807A1 (en) * 2012-01-10 2013-07-11 General Motors Llc Method and system for database browsing
US20140012883A1 (en) * 2007-10-26 2014-01-09 Microsoft Corporation Metadata driven reporting and editing of databases
US20140047377A1 (en) * 2012-08-09 2014-02-13 Sap Ag Retrieving data from an external data source
US8719124B2 (en) 2007-04-30 2014-05-06 Textura Corporation Construction payment management systems and methods with specified billing features
US20140149470A1 (en) * 2012-11-27 2014-05-29 Sandeep Rawal Systems and methods for storing and populating forms
US20140310262A1 (en) * 2013-03-15 2014-10-16 Cerinet Usa Inc. Multiple schema repository and modular database procedures
US9141650B1 (en) * 2011-12-06 2015-09-22 The Boeing Company Methods and systems for filtering tree node data to determine part and assembly relationships
US20150286720A1 (en) * 2012-12-11 2015-10-08 Tmm Data, Llc Methods and systems for collecting, managing, and sharing data
US20160117416A1 (en) * 2014-10-27 2016-04-28 Joseph Wong Automatic detection of queries missing order-by via unit test
WO2016179536A1 (en) * 2015-05-07 2016-11-10 51 Maps, Inc. Secure container platform for resource access and placement on unmanaged and unsecured devices

Families Citing this family (473)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7130879B1 (en) 1999-08-10 2006-10-31 Alexandre Dayon System for publishing, organizing, accessing and distributing information in a computer network
US7689711B2 (en) 2001-03-26 2010-03-30 Salesforce.Com, Inc. System and method for routing messages between applications
US9948644B2 (en) 2001-03-26 2018-04-17 Salesforce.Com, Inc. Routing messages between applications
US7788399B2 (en) 2001-03-26 2010-08-31 Salesforce.Com, Inc. System and method for mapping of services
US7062502B1 (en) * 2001-12-28 2006-06-13 Kesler John N Automated generation of dynamic data entry user interface for relational database management systems
US20030204547A1 (en) * 2002-04-29 2003-10-30 Kevin Davis Technique for scheduling computer processes
US9171049B2 (en) 2002-06-13 2015-10-27 Salesforce.Com, Inc. Offline simulation of online session between client and server
EP1403764A1 (en) * 2002-09-26 2004-03-31 SAP Aktiengesellschaft Method and computer system for dynamic data type enrichment
CA2501206A1 (en) * 2002-10-04 2004-04-15 Tenix Investments Pty Ltd Adaptively interfacing with a data repository
US20050044531A1 (en) * 2003-06-09 2005-02-24 Erc-Ip, Llc Methods and systems for deploying computer source code
US20040255239A1 (en) * 2003-06-13 2004-12-16 Ankur Bhatt Generating electronic reports of data displayed in a computer user interface list view
US8589311B2 (en) * 2003-06-13 2013-11-19 Sap Aktiengesellschaft Designing business content for reporting
US7949953B2 (en) * 2003-06-13 2011-05-24 Sap Aktiengesellschaft Designing and generating charts to graphically represent data in a data source
US7434170B2 (en) * 2003-07-09 2008-10-07 Microsoft Corporation Drag and drop metadata editing
US7890540B2 (en) * 2003-07-22 2011-02-15 Sap Ag Browsing meta data for an enterprise service framework
US20050021538A1 (en) * 2003-07-25 2005-01-27 Activeviews, Inc. Method and system for displaying a relational abstraction of a data store
US7814093B2 (en) * 2003-07-25 2010-10-12 Microsoft Corporation Method and system for building a report for execution against a data store
US8543566B2 (en) 2003-09-23 2013-09-24 Salesforce.Com, Inc. System and methods of improving a multi-tenant database query using contextual knowledge about non-homogeneously distributed tenant data
US8453196B2 (en) 2003-10-14 2013-05-28 Salesforce.Com, Inc. Policy management in an interoperability network
US20050172261A1 (en) * 2004-01-30 2005-08-04 Yuknewicz Paul J. Architecture for creating a user interface using a data schema
US7546286B2 (en) * 2004-02-19 2009-06-09 Microsoft Corporation Offline multi-table data editing and storage
US7546291B2 (en) * 2004-02-19 2009-06-09 Microsoft Corporation Data source task pane
US7779039B2 (en) 2004-04-02 2010-08-17 Salesforce.Com, Inc. Custom entities and fields in a multi-tenant database system
WO2005119435A3 (en) * 2004-06-02 2006-07-20 Joseph C Lesh Systems and methods for dynamic menus
US7251653B2 (en) * 2004-06-30 2007-07-31 Microsoft Corporation Method and system for mapping between logical data and physical data
EP1776668A4 (en) * 2004-08-12 2009-05-06 Jigsaw Data Corp Contact information marketplace
US20060069679A1 (en) * 2004-09-10 2006-03-30 Percey Michael F System for creating associative records
US9645712B2 (en) 2004-10-01 2017-05-09 Grand Central Communications, Inc. Multiple stakeholders for a single business process
US7721328B2 (en) 2004-10-01 2010-05-18 Salesforce.Com Inc. Application identity design
US8060817B2 (en) 2004-11-09 2011-11-15 Oracle International Corporation Data viewer
US8402361B2 (en) * 2004-11-09 2013-03-19 Oracle International Corporation Methods and systems for implementing a dynamic hierarchical data viewer
US7562091B2 (en) * 2004-12-16 2009-07-14 Apple Inc. Cascade feature for creating records in a database
US20060195427A1 (en) * 2005-02-25 2006-08-31 International Business Machines Corporation System and method for improving query response time in a relational database (RDB) system by managing the number of unique table aliases defined within an RDB-specific search expression
US7853961B2 (en) * 2005-02-28 2010-12-14 Microsoft Corporation Platform for data services across disparate application frameworks
US20060195460A1 (en) * 2005-02-28 2006-08-31 Microsoft Corporation Data model for object-relational data
US7685561B2 (en) * 2005-02-28 2010-03-23 Microsoft Corporation Storage API for a common data platform
US7774366B2 (en) 2005-03-08 2010-08-10 Salesforce.Com, Inc. Systems and methods for implementing multi-application tabs and tab sets
US7716168B2 (en) 2005-06-29 2010-05-11 Microsoft Corporation Modifying table definitions within a database application
US8135755B2 (en) * 2005-06-29 2012-03-13 Microsoft Corporation Templates in a schema editor
US7676493B2 (en) * 2005-09-07 2010-03-09 Microsoft Corporation Incremental approach to an object-relational solution
US7827478B2 (en) * 2005-09-08 2010-11-02 William Farr Dynamic generation of form pages for accessing a database
WO2007030796A3 (en) 2005-09-09 2008-01-31 Salesforce Com Inc Systems and methods for exporting, publishing, browsing and installing on-demand applications in a multi-tenant database environment
US8799094B2 (en) 2005-11-28 2014-08-05 Cbs Interactive Inc. Product catalog management system and method
US20070255631A1 (en) * 2005-11-28 2007-11-01 Douglas Schmidt Product catalog management system and method
US9135304B2 (en) 2005-12-02 2015-09-15 Salesforce.Com, Inc. Methods and systems for optimizing text searches over structured data in a multi-tenant environment
US8069153B2 (en) 2005-12-02 2011-11-29 Salesforce.Com, Inc. Systems and methods for securing customer data in a multi-tenant environment
US8095565B2 (en) * 2005-12-05 2012-01-10 Microsoft Corporation Metadata driven user interface
US7743026B2 (en) * 2006-01-31 2010-06-22 Microsoft Corporation Redirection to local copies of server-based files
US7725461B2 (en) * 2006-03-14 2010-05-25 International Business Machines Corporation Management of statistical views in a database system
US7526501B2 (en) * 2006-05-09 2009-04-28 Microsoft Corporation State transition logic for a persistent object graph
US20070266041A1 (en) * 2006-05-11 2007-11-15 Microsoft Corporation Concept of relationshipsets in entity data model (edm)
US7823124B2 (en) * 2006-08-29 2010-10-26 Sap Ag Transformation layer
US8131644B2 (en) * 2006-08-29 2012-03-06 Sap Ag Formular update
US8065661B2 (en) * 2006-08-29 2011-11-22 Sap Ag Test engine
US20080082517A1 (en) * 2006-08-29 2008-04-03 Sap Ag Change assistant
US7912800B2 (en) * 2006-08-29 2011-03-22 Sap Ag Deduction engine to determine what configuration management scoping questions to ask a user based on responses to one or more previous questions
US7908589B2 (en) * 2006-08-29 2011-03-15 Sap Ag Deployment
US8244694B2 (en) * 2006-09-12 2012-08-14 International Business Machines Corporation Dynamic schema assembly to accommodate application-specific metadata
US8370848B2 (en) 2006-10-02 2013-02-05 Salesforce.Com, Inc. Method and system for providing a client access to an external service via an application services platform
US8572057B2 (en) 2006-10-02 2013-10-29 Salesforce.Com, Inc. Method and system for applying a group of instructions to metadata
US8370849B2 (en) 2006-10-02 2013-02-05 Salesforce.Com, Inc. API method and system for providing access to an external service via an application services platform
US8775315B2 (en) 2006-10-02 2014-07-08 Salesforce.Com, Inc. Method and system for integrating a PBX-equipped client and an on-demand database service
US7827138B2 (en) 2006-10-02 2010-11-02 Salesforce.Com, Inc. Method and system for synchronizing a server and an on-demand database service
US8255374B2 (en) 2006-10-02 2012-08-28 Salesforce.Com, Inc. Method and system for selecting amongst a plurality of processes to send a message
US8332435B2 (en) 2006-10-03 2012-12-11 Salesforce.Com, Inc. Method and system for customizing a user interface to an on-demand database service
US8095531B2 (en) 2006-10-03 2012-01-10 Salesforce.Com, Inc. Methods and systems for controlling access to custom objects in a database
US8601467B2 (en) 2006-10-03 2013-12-03 Salesforce.Com, Inc. Methods and systems for upgrading and installing application packages to an application platform
US9230068B2 (en) 2006-10-03 2016-01-05 Salesforce.Com, Inc. Method and system for managing license objects to applications in an application platform
US7730478B2 (en) 2006-10-04 2010-06-01 Salesforce.Com, Inc. Method and system for allowing access to developed applications via a multi-tenant on-demand database service
US8131580B2 (en) 2006-10-04 2012-03-06 Salesforce.Com, Inc. Method and system for load balancing a sales forecast system by selecting a synchronous or asynchronous process based on a type of an event affecting the sales forecast
GB0623059D0 (en) * 2006-11-18 2006-12-27 Etgar Ran Database system and method
US7970796B1 (en) * 2006-12-01 2011-06-28 Intuit Inc. Method and system for importing data to a repository
WO2008092079A3 (en) 2007-01-25 2008-11-06 Clipmarks Llc System, method and apparatus for selecting content from web sources and posting content to web logs
US8381113B2 (en) * 2007-04-06 2013-02-19 Microsoft Corporation Metadata-driven automatic UI code generation
US8706696B2 (en) 2007-05-04 2014-04-22 Salesforce.Com, Inc. Method and system for on-demand communities
US20080319958A1 (en) * 2007-06-22 2008-12-25 Sutirtha Bhattacharya Dynamic Metadata based Query Formulation for Multiple Heterogeneous Database Systems
US20090019022A1 (en) * 2007-07-15 2009-01-15 Dawning Technologies, Inc. Rules-based data mining
US20090031239A1 (en) * 2007-07-17 2009-01-29 Gridiron Software Inc. Asset browser for computing environment
US8781988B1 (en) 2007-07-19 2014-07-15 Salesforce.Com, Inc. System, method and computer program product for messaging in an on-demand database service
US8549417B2 (en) * 2007-07-19 2013-10-01 Salesforce.Com, Inc. System, method and computer program product for editing an on-demand database service graphical user interface
US8140576B1 (en) 2007-07-19 2012-03-20 Salesforce.Com, Inc. On-demand database service system, method and computer program product for conditionally allowing an application of an entity access to data of another entity
US8359647B1 (en) 2007-07-19 2013-01-22 Salesforce.Com, Inc. System, method and computer program product for rendering data of an on-demand database service safe
US7991790B2 (en) 2007-07-20 2011-08-02 Salesforce.Com, Inc. System and method for storing documents accessed by multiple users in an on-demand service
US8700645B2 (en) 2007-08-17 2014-04-15 Salesforce.Com, Inc. On-demand database service system, method, and computer program product for validating a developed application
EP2040182A1 (en) 2007-09-20 2009-03-25 Mario Ballerini Dynamic system for creating and managing a database
US8584212B1 (en) 2007-11-15 2013-11-12 Salesforce.Com, Inc. On-demand service security system and method for managing a risk of access as a condition of permitting access to the on-demand service
US8875259B2 (en) 2007-11-15 2014-10-28 Salesforce.Com, Inc. On-demand service security system and method for managing a risk of access as a condition of permitting access to the on-demand service
CN101201816B (en) 2007-12-20 2010-10-13 北大方正集团有限公司;北京方正阿帕比技术有限公司;北京大学 Adapter and method for outputting data in data stream to XML document
US9501453B2 (en) 2007-12-23 2016-11-22 Salesforce.Com Inc. Method and system for a flexible-data column user interface
JP5229871B2 (en) * 2008-01-10 2013-07-03 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation Technology to support the input of data by the user
US8468117B1 (en) 2008-01-22 2013-06-18 Salesforce.Com, Inc. System, method and computer program product for creating a visual component for tenants of an on-demand database service
US8156205B1 (en) 2008-01-22 2012-04-10 Salesforce.Com, Inc. System, method and computer program product for creating mobile custom views for tenants of an on-demand database service
US8677470B1 (en) 2008-01-22 2014-03-18 Salesforce.Com, Inc. System, method, and computer program product for security verification of communications to tenants of an on-demand database service
US8645376B2 (en) 2008-05-02 2014-02-04 Salesforce.Com, Inc. Method and system for managing recent data in a mobile device linked to an on-demand service
US8478782B1 (en) 2008-05-08 2013-07-02 Salesforce.Com, Inc. System, method and computer program product for sharing tenant information utilizing a multi-tenant on-demand database service
US9791993B2 (en) 2008-05-08 2017-10-17 Salesforce.Com, Inc System, method and computer program product for creating a re-usable component utilizing a multi-tenant on-demand database service
US7890538B2 (en) * 2008-05-09 2011-02-15 International Business Machines Corporation System and method for converting and storing data values
US9251239B1 (en) 2008-05-15 2016-02-02 Salesforce.Com, Inc. System, method and computer program product for applying a public tag to information
US7958094B2 (en) * 2008-06-25 2011-06-07 International Business Machines Corporation Management of deletion requests for related documents in a content management system
US8209355B2 (en) * 2008-07-28 2012-06-26 Microsoft Corporation Automatic user interface generation for entity interaction
US9798784B1 (en) 2008-08-22 2017-10-24 Salesforce.Com, Inc. System, method and computer program product for defining custom junction objects in an on-demand database service
US9535967B2 (en) * 2008-09-10 2017-01-03 Salesforce.Com, Inc. Method and system for providing efficient and complex database functionality to a mobile device
US8538942B2 (en) 2008-09-12 2013-09-17 Salesforce.Com, Inc. Method and system for sharing documents between on-demand services
US9047479B1 (en) 2008-09-12 2015-06-02 Salesforce.Com, Inc. System, method and computer program product for providing a team object in association with an object
US8423524B1 (en) 2008-09-12 2013-04-16 Salesforce.Com, Inc. System, method and computer program product for storing reports for use by tenants of a multi-tenant on-demand database service
US8726179B2 (en) 2008-09-12 2014-05-13 Salesforce.Com, Inc. Method and system for providing in-line scheduling in an on-demand service
US8417723B1 (en) 2008-09-12 2013-04-09 Salesforce.Com, Inc. System, method and computer program product for enabling access to a resource of a multi-tenant on-demand database service utilizing a token
US8135659B2 (en) * 2008-10-01 2012-03-13 Sap Ag System configuration comparison to identify process variation
US8661056B1 (en) 2008-11-03 2014-02-25 Salesforce.Com, Inc. System, method and computer program product for publicly providing web content of a tenant using a multi-tenant on-demand database service
US8396893B2 (en) 2008-12-11 2013-03-12 Sap Ag Unified configuration of multiple applications
US8255429B2 (en) * 2008-12-17 2012-08-28 Sap Ag Configuration change without disruption of incomplete processes
US9286364B2 (en) 2009-01-23 2016-03-15 Salesforce.Com Inc. Methods and systems for sharing information in a supply chain
US8065323B2 (en) * 2009-02-23 2011-11-22 Oracle International Corporation Offline validation of data in a database system for foreign key constraints
US8150832B2 (en) * 2009-03-06 2012-04-03 Oracle International Corporation Methods and systems for automatically determining a default hierarchy from data
US8751826B2 (en) 2009-04-01 2014-06-10 Salesforce.Com, Inc. Enhanced system security
US8812533B1 (en) 2009-05-21 2014-08-19 Salesforce.Com, Inc. System, method and computer program product for automatically presenting selectable options in a lookup field
US20150019484A1 (en) * 2011-06-03 2015-01-15 Robert Mack Method and apparatus for implementing a set of integrated data systems
US20110078144A1 (en) * 2009-09-28 2011-03-31 Oracle International Corporation Hierarchical sequential clustering
US20110074789A1 (en) * 2009-09-28 2011-03-31 Oracle International Corporation Interactive dendrogram controls
US8621015B2 (en) 2009-10-30 2013-12-31 Salesforce.Com, Inc. Integrating and managing social networking information in an on-demand database system
US20110106808A1 (en) * 2009-10-30 2011-05-05 Salesforce.Com, Inc. Multi-dimensional content organization and delivery
US8560575B2 (en) * 2009-11-12 2013-10-15 Salesforce.Com, Inc. Methods and apparatus for selecting updates to associated records to publish on an information feed in an on-demand database service environment
US8478722B2 (en) 2009-11-12 2013-07-02 Salesforce.Com, Inc. Enterprise level business information networking for changes in a database
US20110208759A1 (en) * 2010-02-23 2011-08-25 Paul Zellweger Method, Apparatus, and Interface For Creating A Chain of Binary Attribute Relations
US8732663B2 (en) 2010-02-24 2014-05-20 Salesforce.Com, Inc. System, method and computer program product for providing automated testing by utilizing a preconfigured point of entry in a test or by converting a test to a predefined format
US8898287B2 (en) 2010-02-24 2014-11-25 Salesforce.Com, Inc. System, method and computer program product for monitoring data activity utilizing a shared data store
US9600512B2 (en) 2010-02-25 2017-03-21 Salesforce.Com, Inc. Systems and methods for implementing customized drop-down menus
US9251164B2 (en) 2010-02-26 2016-02-02 Salesforce.Com, Inc. System, method and computer program product for using a database to access content stored outside of the database
US9715555B2 (en) 2010-02-26 2017-07-25 Salesforce.Com, Inc. System, method and computer program product for user registration with a multi-tenant on-demand database system
US9405426B2 (en) * 2010-03-01 2016-08-02 Salesforce.Com, Inc. Method and system for providing an adaptive input user interface for data entry applications
US8713043B2 (en) 2010-03-01 2014-04-29 Salesforce.Com, Inc. System, method and computer program product for sharing a single instance of a database stored using a tenant of a multi-tenant on-demand database system
US9471648B2 (en) 2010-03-01 2016-10-18 Salesforce.Com, Inc. System, method and computer program product for displaying one or more data sets to a user
US8583587B2 (en) 2010-03-08 2013-11-12 Salesforce.Com, Inc. System, method and computer program product for performing one or more actions utilizing a uniform resource locator
US9477369B2 (en) 2010-03-08 2016-10-25 Salesforce.Com, Inc. System, method and computer program product for displaying a record as part of a selected grouping of data
US8898582B2 (en) * 2010-03-10 2014-11-25 Salesforce.Com, Inc. Configurable highlights panel for display of database records
US8739030B2 (en) 2010-03-10 2014-05-27 Salesforce.Com, Inc. Providing a quote template in a multi-tenant database system environment
US8769416B2 (en) * 2010-03-12 2014-07-01 Salesforce.Com, Inc. Service cloud console
US9117003B2 (en) 2010-03-12 2015-08-25 Salesforce.Com, Inc. System, method and computer program product for navigating content on a single page
US9268955B2 (en) 2010-03-12 2016-02-23 Salesforce.Com, Inc. System, method and computer program product for conditionally sharing an object with one or more entities
US8688802B2 (en) 2010-03-15 2014-04-01 Salesforce.Com, Inc. System, method and computer program product for serving an application from a custom subdomain
US8793291B2 (en) 2010-03-15 2014-07-29 Salesforce.Com, Inc. System, method and computer program product for deploying an update between environments of a multi-tenant on-demand database system
US9031996B2 (en) 2010-03-15 2015-05-12 Salesforce.Com System, method and computer program product for creating a plurality of CNAMES for a website
US8996610B1 (en) 2010-03-15 2015-03-31 Salesforce.Com, Inc. Proxy system, method and computer program product for utilizing an identifier of a request to route the request to a networked device
US9111006B2 (en) 2010-03-16 2015-08-18 Salesforce.Com, Inc. System, method and computer program product for communicating data between a database and a cache
US9098365B2 (en) 2010-03-16 2015-08-04 Salesforce.Com, Inc. System, method and computer program product for conditionally enabling an installation aspect
US9246707B2 (en) 2010-03-16 2016-01-26 Salesforce.Com, Inc. Cost-based SMTP email routing
US20110231457A1 (en) * 2010-03-16 2011-09-22 Salesforce.Com, Inc. Monitoring and managing job resources for database tasks
US9009709B2 (en) 2010-03-16 2015-04-14 Salesforce.Com, Inc. Asynchronous rollup numbers forecasting methods and systems
CN105956176A (en) 2010-03-18 2016-09-21 诺宝公司 Database management system
US8370809B2 (en) 2010-03-18 2013-02-05 Salesforce.Com, Inc. System, method and computer program product for automated test case generation and scheduling
US8930933B2 (en) 2010-03-19 2015-01-06 Salesforce.Com, Inc. System, method and computer program product for associating a plurality of stored elements with a creation of a patch
US9275033B2 (en) 2010-03-25 2016-03-01 Salesforce.Com, Inc. System, method and computer program product for creating an object within a system, utilizing a template
US9037546B2 (en) 2010-03-25 2015-05-19 Salesforce.Com, Inc. System, method and computer program product for automatic code generation for database object deletion
US8977675B2 (en) 2010-03-26 2015-03-10 Salesforce.Com, Inc. Methods and systems for providing time and date specific software user interfaces
US9361350B2 (en) 2010-03-26 2016-06-07 Salesforce.Com, Inc. Data transfer between first and second databases
US8539234B2 (en) 2010-03-30 2013-09-17 Salesforce.Com, Inc. Secure client-side communication between multiple domains
US9619652B2 (en) 2010-03-31 2017-04-11 Salesforce.Com, Inc. System, method and computer program product for determining a risk score for an entity
US9239722B1 (en) 2010-03-31 2016-01-19 Salesforce.Com, Inc. System, method and computer program product for interacting with a process diagram
US9767136B2 (en) 2010-03-31 2017-09-19 Salesforce.Com, Inc. System, method and computer program product for maintaining data stored in a data structure
US8818938B2 (en) 2010-04-01 2014-08-26 Salesforce.Com, Inc. System, method and computer program product for synchronizing entities within a system
US20110246524A1 (en) 2010-04-01 2011-10-06 Salesforce.Com, Inc. System, method and computer program product for portal user data access in a multi-tenant on-demand database system
US8925041B2 (en) 2010-04-01 2014-12-30 Salesforce.Com, Inc. System, method and computer program product for performing one or more actions based on a determined access permissions for a plurality of users
US9195681B2 (en) 2010-04-01 2015-11-24 Salesforce.Com, Inc. System, method and computer program product for transmitting a group of data elements
US8799327B2 (en) 2010-04-01 2014-08-05 Salesforce.Com, Inc. System, method and computer program product for deriving commonalities among data entries
US8818985B2 (en) 2010-04-06 2014-08-26 Salesforce.Com, Inc. Rule-based prioritization of social data
US8793691B2 (en) 2010-04-15 2014-07-29 Salesforce.Com, Inc. Managing and forwarding tasks to handler for processing using a message queue
US8584124B2 (en) 2010-04-20 2013-11-12 Salesforce.Com, Inc. Methods and systems for batch processing in an on-demand service environment
US9229793B2 (en) 2010-04-22 2016-01-05 Salesforce.Com, Inc. System, method and computer program product for routing messages to a server
US8875152B2 (en) 2010-04-22 2014-10-28 Salesforce.Com, Inc. System, method and computer program product for dynamically increasing resources utilized for processing tasks
US8543932B2 (en) 2010-04-23 2013-09-24 Datacert, Inc. Generation and testing of graphical user interface for matter management workflow with collaboration
US8751939B2 (en) 2010-04-26 2014-06-10 Salesforce.Com, Inc. Side tab navigation and page views personalization systems and methods
US9355270B2 (en) 2010-04-28 2016-05-31 Salesforce.Com, Inc. Security configuration systems and methods for portal users in a multi-tenant database environment
US8972431B2 (en) 2010-05-06 2015-03-03 Salesforce.Com, Inc. Synonym supported searches
US8521780B2 (en) 2010-05-07 2013-08-27 Salesforce.Com, Inc. Methods and systems for sharing email in a multi-tenant database system
US8718241B2 (en) 2010-05-07 2014-05-06 Salesforce.Com, Inc. Methods and apparatus for interfacing with a phone system in an on-demand service environment
US8566792B2 (en) 2010-05-07 2013-10-22 Salesforce, Inc. Validating visual components
US9009669B2 (en) 2010-05-07 2015-04-14 Salesforce.Com, Inc. Visual user interface validator
US9781049B2 (en) 2010-05-07 2017-10-03 Salesforce.Com, Inc. Resolving information in a database environment
US8959483B2 (en) 2010-05-13 2015-02-17 Salesforce.Com, Inc. Test framework of visual components in a multitenant database environment
US8850219B2 (en) 2010-05-13 2014-09-30 Salesforce.Com, Inc. Secure communications
US20110289401A1 (en) 2010-05-20 2011-11-24 Salesforce.Com, Inc. Multiple graphical annotations of documents using overlays
US9021435B2 (en) 2010-05-20 2015-04-28 Salesforce.Com, Inc. Methods and systems for providing a user interface in a multi-tenant database environment
US9275160B2 (en) 2010-05-20 2016-03-01 Salesforce.Com, Inc. Performing an upgrade in a multi-tenant database system environment
US8738603B2 (en) 2010-05-20 2014-05-27 Salesforce.Com, Inc. Metrics-based accessing of social threads
US9262138B2 (en) 2010-05-27 2016-02-16 Salesforce.Com, Inc. Adding directives for JavaScript files directly into source code in a multi-tenant database environment
US8862632B2 (en) 2010-05-28 2014-10-14 Salesforce.Com, Inc. Customizing standard formula fields in a multi-tenant database system environment
US8572080B2 (en) 2010-06-04 2013-10-29 Salesforce.Com, Inc. Methods and systems for analyzing a network feed in a multi-tenant database system environment
US8452726B2 (en) 2010-06-04 2013-05-28 Salesforce.Com, Inc. Sharing information between tenants of a multi-tenant database
US8595382B2 (en) 2010-06-07 2013-11-26 Salesforce.Com, Inc. System, method and computer program product for performing a synchronization of data
US9246699B2 (en) 2010-06-07 2016-01-26 Salesforce.Com, Inc. Method and system for testing multiple components of a multi-tenant, multi-domain, multi-tiered website
US8539068B2 (en) 2010-06-07 2013-09-17 Salesforce.Com, Inc. Methods and systems for providing customized domain messages
US9223852B2 (en) 2010-06-11 2015-12-29 Salesforce.Com, Inc. Methods and systems for analyzing search terms in a multi-tenant database system environment
US8595207B2 (en) 2010-06-14 2013-11-26 Salesforce.Com Methods and systems for dynamically suggesting answers to questions submitted to a portal of an online service
US9495282B2 (en) 2010-06-21 2016-11-15 Salesforce.Com, Inc. Method and systems for a dashboard testing framework in an online demand service environment
US9177070B2 (en) 2010-06-21 2015-11-03 Salesforce.Com, Inc. System, method and computer program product for performing actions associated with a portal
US8230062B2 (en) 2010-06-21 2012-07-24 Salesforce.Com, Inc. Referred internet traffic analysis system and method
US8620305B2 (en) 2010-06-23 2013-12-31 Salesforce.Com, Inc. Methods and systems for a mobile device testing framework
US9817637B2 (en) 2010-07-01 2017-11-14 Salesforce.Com, Inc. Methods and systems for providing enhancements to a business networking feed
US9280596B2 (en) 2010-07-01 2016-03-08 Salesforce.Com, Inc. Method and system for scoring articles in an on-demand services environment
US8832061B2 (en) 2010-07-02 2014-09-09 Salesforce.Com, Inc. Optimizing data synchronization between mobile clients and database systems
US9529698B2 (en) 2010-07-13 2016-12-27 Salesforce.Com, Inc. Method and system for multi-mode testing through operation interface and scenario abstraction in a multi-tenant database environment
US8738970B2 (en) 2010-07-23 2014-05-27 Salesforce.Com, Inc. Generating performance alerts
US9507940B2 (en) 2010-08-10 2016-11-29 Salesforce.Com, Inc. Adapting a security tool for performing security analysis on a software application
US8812977B2 (en) 2010-08-12 2014-08-19 Salesforce.Com, Inc. Accessing multi-page data using a page index in a scrollbar
US20120041989A1 (en) * 2010-08-16 2012-02-16 Tata Consultancy Services Limited Generating assessment data
US8904541B2 (en) 2010-08-26 2014-12-02 Salesforce.Com, Inc. Performing security assessments in an online services system
US9262393B2 (en) 2010-08-31 2016-02-16 Salesforce.Com, Inc. Method and system for providing simplified form filling in an on-demand service
US9619534B2 (en) 2010-09-10 2017-04-11 Salesforce.Com, Inc. Probabilistic tree-structured learning system for extracting contact data from quotes
US9646246B2 (en) 2011-02-24 2017-05-09 Salesforce.Com, Inc. System and method for using a statistical classifier to score contact entities
US8769704B2 (en) 2010-09-10 2014-07-01 Salesforce.Com, Inc. Method and system for managing and monitoring of a multi-tenant system
US9106761B2 (en) 2010-09-23 2015-08-11 Salesforce.Com, Inc. Methods and apparatus for inviting users to follow records in an on-demand database service environment
US8732150B2 (en) 2010-09-23 2014-05-20 Salesforce.Com, Inc. Methods and apparatus for suppressing network feed activities using an information feed in an on-demand database service environment
US8560554B2 (en) 2010-09-23 2013-10-15 Salesforce.Com, Inc. Methods and apparatus for selecting updates to associated records to publish on an information feed using importance weights in an on-demand database service environment
US8661076B2 (en) 2010-09-23 2014-02-25 Salesforce.Com, Inc. Business networking information feed alerts
US20120086544A1 (en) 2010-10-08 2012-04-12 Salesforce.Com, Inc. Following Data Records in an Information Feed
US8914405B2 (en) 2010-10-08 2014-12-16 Salesforce.Com, Inc. Methods and systems for latency-free database queries
US9031957B2 (en) 2010-10-08 2015-05-12 Salesforce.Com, Inc. Structured data in a business networking feed
US8949939B2 (en) 2010-10-13 2015-02-03 Salesforce.Com, Inc. Methods and systems for provisioning access to customer organization data in a multi-tenant system
US8903770B2 (en) 2010-10-15 2014-12-02 Salesforce.Com, Inc. Methods and apparatus for discontinuing the following of records in an on-demand database service environment
US9304614B2 (en) 2010-10-20 2016-04-05 Salesforce.Com, Inc. Framework for custom actions on an information feed
US9411855B2 (en) 2010-10-25 2016-08-09 Salesforce.Com, Inc. Triggering actions in an information feed system
US8732606B2 (en) 2010-10-25 2014-05-20 Salesforce.Com, Inc. Computer implemented methods and apparatus for dynamic windowing in user interfaces
US9858535B2 (en) * 2010-10-25 2018-01-02 Innovatia Inc. System and method for dynamic generation of procedures
US8886766B2 (en) 2010-10-25 2014-11-11 Salesforce.Com, Inc. Systems and methods for tracking responses on an online social network
US8782238B2 (en) 2010-11-05 2014-07-15 Verizon Patent And Licensing Inc. Server clustering in a computing-on-demand system
US9128733B2 (en) 2010-11-12 2015-09-08 Microsoft Technology Licensing, Llc Display and resolution of incompatible layout constraints
US8682918B2 (en) 2010-11-22 2014-03-25 Salesforce.Com, Inc. Method and system for making content-based recommendations
US9690808B2 (en) * 2010-12-01 2017-06-27 Salesforce.Com, Inc. Methods and systems for loose coupling between triggers and entities
US9977814B2 (en) 2011-11-04 2018-05-22 Salesforce.Com, Inc. Custom metadata in loosely coupled triggers
US8756221B2 (en) 2010-12-03 2014-06-17 Salesforce.Com, Inc. Social files
US9465885B2 (en) 2010-12-03 2016-10-11 Salesforce.Com, Inc. Method and system for providing information to a mobile handheld device from a database system
US9069448B2 (en) 2010-12-03 2015-06-30 Salesforce.Com, Inc. Filtering objects in a multi-tenant environment
US20120150801A1 (en) * 2010-12-08 2012-06-14 Microsoft Corporation Platform agnostic file attribute synchronization
US8793706B2 (en) 2010-12-16 2014-07-29 Microsoft Corporation Metadata-based eventing supporting operations on data
US20120173568A1 (en) * 2011-01-04 2012-07-05 International Business Machines Corporation Getting individual row counts from related tables matching selection criteria
US8566648B2 (en) 2011-02-02 2013-10-22 Salesforce, Inc. Automated testing on devices
US8903943B2 (en) 2011-02-15 2014-12-02 Salesforce.Com, Inc. Integrating cloud applications and remote jobs
US8517840B2 (en) 2011-02-18 2013-08-27 Salesforce.Com, Inc. Methods and systems for providing a challenge user interface for an enterprise social network
US8972336B2 (en) 2012-05-03 2015-03-03 Salesforce.Com, Inc. System and method for mapping source columns to target columns
US9443224B2 (en) 2011-03-01 2016-09-13 Salesforce.Com, Inc. Systems, apparatus and methods for selecting updates to associated records to publish on an information feed
US9524285B2 (en) * 2011-03-05 2016-12-20 Kapaleeswar Madireddi Stream flow chemical process information system and method
US9430583B1 (en) 2011-06-10 2016-08-30 Salesforce.Com, Inc. Extracting a portion of a document, such as a web page
US20120330924A1 (en) 2011-06-21 2012-12-27 Salesforce.Com, Inc. Method and system for querying an on demand database service
US9195648B2 (en) 2011-10-12 2015-11-24 Salesforce.Com, Inc. Multi-lingual knowledge base
US9864762B2 (en) 2011-06-23 2018-01-09 Salesforce.Com, Inc. Systems and methods for mapping a value to a new domain
US9069593B2 (en) 2011-06-23 2015-06-30 Salesforce.Com, Inc. Systems and methods for deletion of untracked datastore paths
US9208187B2 (en) 2011-06-24 2015-12-08 Salesforce.Com, Inc. Using a database system for selective inclusion and exclusion of types of updates to provide a configuration feed of a social networking system
US9953273B2 (en) 2011-06-28 2018-04-24 Salesforce.Com, Inc. Systems and methods for creating a rich social media profile
US9064339B2 (en) 2011-06-28 2015-06-23 Salesforce.Com, Inc. Computer implemented systems and methods for providing a mobile social enterprise interface
US8943011B2 (en) 2011-06-28 2015-01-27 Salesforce.Com, Inc. Methods and systems for using map-reduce for large-scale analysis of graph-based data
US9069788B2 (en) 2011-07-01 2015-06-30 Salesforce.Com, Inc. Truncating data associated with objects in a multi-tenant database
US9123028B2 (en) 2011-07-01 2015-09-01 Salesforce.Com, Inc. Computer implemented methods and apparatus for controlling the inclusion of edited information in an information feed
US8892585B2 (en) 2011-07-05 2014-11-18 Microsoft Corporation Metadata driven flexible user interface for business applications
US9015494B2 (en) 2011-07-11 2015-04-21 Salesforce.Com, Inc. Methods and apparatus for digital steganography
US9489660B2 (en) 2011-07-12 2016-11-08 Salesforce.Com, Inc. Methods and systems for public collaborative interface for private network groups
US9037681B2 (en) 2011-07-12 2015-05-19 Salesforce.Com, Inc. Methods and systems for prioritizing multiple network feeds
US9395881B2 (en) 2011-07-12 2016-07-19 Salesforce.Com, Inc. Methods and systems for navigating display sequence maps
US9195971B2 (en) 2011-07-12 2015-11-24 Salesforce.Com, Inc. Method and system for planning a meeting in a cloud computing environment
US9229934B2 (en) 2011-07-12 2016-01-05 Salesforce.Com, Inc. Method and system for document integration
US8954449B2 (en) 2011-07-12 2015-02-10 Salesforce.Com, Inc. Method and system for determining a user's brand influence
US9071658B2 (en) 2011-07-12 2015-06-30 Salesforce.Com, Inc. Method and system for presenting a meeting in a cloud computing environment
US20130018955A1 (en) 2011-07-14 2013-01-17 Salesforce.Com, Inc. Computer implemented methods and apparatus for implementing a social network information feed as a platform
US9443225B2 (en) 2011-07-18 2016-09-13 Salesforce.Com, Inc. Computer implemented methods and apparatus for presentation of feed items in an information feed to be displayed on a display device
US8521782B2 (en) 2011-07-20 2013-08-27 Salesforce.Com, Inc. Methods and systems for processing large graphs using density-based processes using map-reduce
US20130024910A1 (en) 2011-07-22 2013-01-24 Salesforce.Com, Inc. Computer implemented methods and apparatus for integrating a social network information feed with a network communications application
US8620875B2 (en) 2011-07-25 2013-12-31 Salesforce.Com, Inc. Fraud analysis in a contact database
US8972421B2 (en) 2011-07-26 2015-03-03 Salesforce.Com, Inc. Systems and methods for propagating a global filter to individual datasets
US9613326B2 (en) 2011-07-26 2017-04-04 Salesforce.Com, Inc. Method and system for filtering common fields across multiple data sets
US9325750B2 (en) 2011-07-26 2016-04-26 Salesforce.Com, Inc. Method and system for viewing a contact network feed in a business directory environment
US8984051B2 (en) 2011-07-26 2015-03-17 Salesforce.Com, Inc. Computer implemented methods and apparatus for communicating feed information to one or more recipients
US9256859B2 (en) 2011-07-26 2016-02-09 Salesforce.Com, Inc. Systems and methods for fragmenting newsfeed objects
US9189532B2 (en) 2011-07-26 2015-11-17 Salesforce.Com, Inc. System, method and computer program product for locally defining related reports using a global definition
US8745625B2 (en) 2011-07-26 2014-06-03 Salesforce.Com, Inc. System, method and computer program product for conditionally executing related reports in parallel based on an estimated execution time
US9591090B2 (en) 2011-08-22 2017-03-07 Salesforce.Com, Inc. Computer implemented methods and apparatus for sharing data of an information feed of an online social network
US9395882B2 (en) 2011-08-24 2016-07-19 Salesforce.Com, Inc. Systems and methods for promoting related lists
US8549047B2 (en) 2011-08-25 2013-10-01 Salesforce.Com, Inc. Computer implemented methods and apparatus for feed-based case management
US8725721B2 (en) 2011-08-25 2014-05-13 Salesforce.Com, Inc. Personalizing scoping and ordering of object types for search
US9535573B2 (en) 2011-08-26 2017-01-03 Salesforce.Com, Inc. Systems and methods for dynamic list views and detail pages
US9215096B2 (en) 2011-08-26 2015-12-15 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing communication between network domains in a service cloud
US8412178B2 (en) 2011-08-30 2013-04-02 Salesforce.Com, Inc. Mechanism for facilitating dynamic and segment-based monitoring of cellular network performance in an on-demand services environment
US9178753B2 (en) 2011-08-31 2015-11-03 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing access to an online social network
US9830435B2 (en) 2011-10-04 2017-11-28 Salesforce.Com, Inc. Method and system for providing login as a service
US9038074B2 (en) 2011-10-04 2015-05-19 Salesforce.Com, Inc. System, method and computer program product for recursively executing a process control operation to use an ordered list of tags to initiate corresponding functional operations
US9542711B2 (en) 2011-10-07 2017-01-10 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing selective notifications in an online social network
US9058363B2 (en) 2011-10-07 2015-06-16 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing a distribution list of users in an online social network
US9467424B2 (en) 2011-10-07 2016-10-11 Salesforce.Com, Inc. Methods and systems for proxying data
US9767132B2 (en) 2011-10-10 2017-09-19 Salesforce.Com, Inc. Systems and methods for real-time de-duplication
US9589070B2 (en) 2011-10-10 2017-03-07 Salesforce.Com, Inc. Method and system for updating a filter logic expression representing a boolean filter
US9727924B2 (en) 2011-10-10 2017-08-08 Salesforce.Com, Inc. Computer implemented methods and apparatus for informing a user of social network data when the data is relevant to the user
US9007364B2 (en) 2011-10-12 2015-04-14 Salesforce.Com, Inc. Augmented reality display apparatus and related methods using database record data
US9064287B2 (en) 2011-10-13 2015-06-23 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing group-related social network information
US8839448B2 (en) 2011-10-18 2014-09-16 Salesforce.Com, Inc. Generation of a human readable output message in a format that is unreadable by a computer-based device
US9443007B2 (en) 2011-11-02 2016-09-13 Salesforce.Com, Inc. Tools and techniques for extracting knowledge from unstructured data retrieved from personal data sources
US9471666B2 (en) 2011-11-02 2016-10-18 Salesforce.Com, Inc. System and method for supporting natural language queries and requests against a user's personal data cloud
US9047070B2 (en) 2011-11-03 2015-06-02 Salesforce.Com, Inc. System, method and computer program product for defining applications using metadata records created from an object specifying a predefined metadata format
US9152725B2 (en) 2011-11-04 2015-10-06 Salesforce.Com, Inc. Computer implemented methods and apparatus for configuring and performing a custom rule to process a preference indication
US9830050B2 (en) 2011-11-23 2017-11-28 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing a reminder regarding a feed item of a feed of an online social network
US8812438B2 (en) 2012-01-20 2014-08-19 Salesforce.Com, Inc. System, method and computer program product for synchronizing data using data identifying messages
US8731151B2 (en) 2012-02-02 2014-05-20 Salesforce.Com, Inc. Methods and apparatus for partially updating a web page using an embedded iFrame
US9306878B2 (en) 2012-02-14 2016-04-05 Salesforce.Com, Inc. Intelligent automated messaging for computer-implemented devices
US9477698B2 (en) 2012-02-22 2016-10-25 Salesforce.Com, Inc. System and method for inferring reporting relationships from a contact database
US9330145B2 (en) 2012-02-22 2016-05-03 Salesforce.Com, Inc. Systems and methods for context-aware message tagging
US9195835B2 (en) 2012-03-01 2015-11-24 Salesforce.Com, Inc. System and method for initializing tokens in a dictionary encryption scheme
US9503535B2 (en) 2012-03-06 2016-11-22 Salesforce.Com, Inc. Computer implemented methods and apparatus for automatically following entities in an online social network
US9626523B2 (en) 2012-03-08 2017-04-18 Salesforce.Com, Inc. Systems and methods of audit trailing of data incorporation
US8996674B2 (en) 2012-03-19 2015-03-31 Salesforce.Com, Inc. System, method and computer program product for SNMP based mobile device management
US9832156B2 (en) 2012-03-23 2017-11-28 Salesforce.Com, Inc. Social networking system communities and associated user privileges implemented using a database system
US9558277B2 (en) 2012-04-04 2017-01-31 Salesforce.Com, Inc. Computer implemented methods and apparatus for identifying topical influence in an online social network
US9307006B2 (en) 2012-04-11 2016-04-05 Salesforce.Com, Inc. System and method for synchronizing data objects in a cloud based social networking environment
US9361468B2 (en) 2012-04-17 2016-06-07 Salesforce.Com, Inc. Method and system for granting access to secure data
US9753926B2 (en) 2012-04-30 2017-09-05 Salesforce.Com, Inc. Extracting a portion of a document, such as a web page
US9262037B2 (en) 2012-04-30 2016-02-16 Salesforce.Com, Inc. Selective capture of incoming email messages for diagnostic analysis
US9137172B2 (en) 2012-05-02 2015-09-15 Salesforce.Com, Inc. Managing multiple proxy servers in a multi-tenant application system environment
US9110959B2 (en) 2012-05-03 2015-08-18 Salesforce.Com, Inc. System and method for geo-location data type searching in an on demand environment
US9197513B2 (en) 2012-05-03 2015-11-24 Salesforce.Com, Inc. Computer implemented methods and apparatus for representing a portion of a user interface as a network address
US8973106B2 (en) 2012-05-03 2015-03-03 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing permissions to users in an on-demand service environment
US9094359B2 (en) 2012-05-09 2015-07-28 Salesforce.Com, Inc. Method and system for inter-social network communications
US9252976B2 (en) 2012-05-09 2016-02-02 Salesforce.Com, Inc. Method and system for social media cooperation protocol
US9177007B2 (en) 2012-05-14 2015-11-03 Salesforce.Com, Inc. Computer implemented methods and apparatus to interact with records using a publisher of an information feed of an online social network
US9264388B2 (en) 2012-05-18 2016-02-16 Salesforce.Com, Inc. Re-routing incoming email for a multi-tenant database system
US9916592B2 (en) 2012-05-18 2018-03-13 Oracle International Corporation Method and system for implementing implicit follow and automatic unfollow
US9237156B2 (en) 2012-05-21 2016-01-12 Salesforce.Com, Inc. Systems and methods for administrating access in an on-demand computing environment
WO2013174452A1 (en) * 2012-05-24 2013-11-28 Telefonaktiebolaget L M Ericsson (Publ) Meta model driven data export from a database and meta model driven data import to a database
US20130339399A1 (en) * 2012-06-18 2013-12-19 Dexter A. Dorris Dynamic Schema
US9378263B2 (en) 2012-06-19 2016-06-28 Salesforce.Com, Inc. Method and system for creating indices and loading key-value pairs for NoSQL databases
US9979587B2 (en) 2012-06-19 2018-05-22 Salesforce.Com, Inc. Method and system for semi-synchronously exporting data
US9479387B2 (en) 2012-06-22 2016-10-25 Salesforce.Com, Inc. Methods and systems for priority-based notifications for mobile devices
US9148438B2 (en) 2012-06-25 2015-09-29 Salesforce.Com, Inc. System, method and computer program product for publishing non-malicious third party content to a data feed
WO2014000269A1 (en) * 2012-06-29 2014-01-03 Hewlett-Packard Development Company, L.P. Rule-based automated test data generation
US9766881B2 (en) 2012-07-02 2017-09-19 Salesforce.Com, Inc. Social project management system and marketplace
US9715879B2 (en) 2012-07-02 2017-07-25 Salesforce.Com, Inc. Computer implemented methods and apparatus for selectively interacting with a server to build a local database for speech recognition at a device
US9658933B2 (en) 2012-07-02 2017-05-23 Salesforce.Com, Inc. Automatically modifying a test for a program on multiple electronic devices
US9241017B2 (en) 2012-07-03 2016-01-19 Salesforce.Com, Inc. Systems and methods for cross domain service component interaction
US9628493B2 (en) 2012-07-03 2017-04-18 Salesforce.Com, Inc. Computer implemented methods and apparatus for managing permission sets and validating user assignments
US9436701B2 (en) 2012-07-03 2016-09-06 Salesforce.Com, Inc. Methods and systems for regulating user engagement
US9075766B2 (en) 2012-07-12 2015-07-07 Salesforce.Com, Inc. Computer implemented methods and apparatus for determining whether to continue relationships in an online social network
US9245145B2 (en) 2012-07-16 2016-01-26 Salesforce.Com, Inc. Methods and systems for regulating database activity
US9268822B2 (en) 2012-07-18 2016-02-23 Salesforce.Com, Inc. System and method for determining organizational hierarchy from business card data
US9659059B2 (en) 2012-07-20 2017-05-23 Salesforce.Com, Inc. Matching large sets of words
US9619458B2 (en) 2012-07-20 2017-04-11 Salesforce.Com, Inc. System and method for phrase matching with arbitrary text
US9367626B2 (en) 2012-07-23 2016-06-14 Salesforce.Com, Inc. Computer implemented methods and apparatus for implementing a topical-based highlights filter
US9569060B2 (en) 2012-07-25 2017-02-14 Salesforce.Com, Inc. Computer implemented methods and apparatus for composing and batch publishing feed items in a feed-based interaction context
US9886695B2 (en) 2012-07-27 2018-02-06 Salesforce.Com Inc. Sales force automation system and method for real-time traveling salesperson location tracking and account visit selection
US9432320B2 (en) 2012-07-30 2016-08-30 Salesforce.Com, Inc. System and method for providing an information-centric application
US8990958B2 (en) 2012-08-31 2015-03-24 Salesforce.Com, Inc. Systems and methods for content management in an on demand environment
US9747388B2 (en) 2012-08-31 2017-08-29 Salesforce.Com, Inc. Systems and methods for providing access to external content objects
US9292589B2 (en) 2012-09-04 2016-03-22 Salesforce.Com, Inc. Identifying a topic for text using a database system
US9830385B2 (en) 2012-09-04 2017-11-28 Salesforce.Com, Inc. Methods and apparatus for partitioning data
US9575871B2 (en) 2012-09-04 2017-02-21 Salesforce.Com, Inc. System and method for dynamically debugging data in a multi-tenant database environment
US9495342B2 (en) 2012-09-05 2016-11-15 Salesforce.Com, Inc. System and method for automatically inserting correct escaping functions for field references in a multi-tenant computing environment
US9495430B2 (en) 2012-09-06 2016-11-15 Salesforce.Com Systems and methods for batch processing of data records in an on-demand system
US9037611B2 (en) 2012-09-13 2015-05-19 Microsoft Technology Licensing, Llc Generation of a user interface based on a relational data model
US9553783B2 (en) 2012-09-14 2017-01-24 Salesforce.Com, Inc. Spam flood detection methodologies
US9898519B2 (en) 2012-09-14 2018-02-20 Salesforce.Com, Inc. Systems and methods of enriching CRM data with social data
US9495403B2 (en) 2012-09-14 2016-11-15 Salesforce.Com, Inc. Method and system for cleaning data in a customer relationship management system
US9774555B2 (en) 2012-09-14 2017-09-26 Salesforce.Com, Inc. Computer implemented methods and apparatus for managing objectives in an organization in a social network environment
US9977788B2 (en) 2012-09-14 2018-05-22 Salesforce.Com, Inc. Methods and systems for managing files in an on-demand system
US9253283B2 (en) 2012-09-14 2016-02-02 Salesforce.Com, Inc. Systems and methods for ghosting and providing proxies in a network feed
US20140082183A1 (en) 2012-09-14 2014-03-20 Salesforce.Com, Inc. Detection and handling of aggregated online content using characterizing signatures of content items
US9626637B2 (en) 2012-09-18 2017-04-18 Salesforce.Com, Inc. Method and system for managing business deals
US9495557B2 (en) 2012-09-18 2016-11-15 Salesforce.Com, Inc. Methods and systems for managing access to data in an on-demand system
US9069858B1 (en) 2012-09-18 2015-06-30 Salesforce.Com, Inc. Systems and methods for identifying entity mentions referencing a same real-world entity
US9442778B2 (en) 2012-10-01 2016-09-13 Salesforce.Com, Inc. Method and system for secured inter-application communication in mobile devices
US9634977B2 (en) 2012-10-01 2017-04-25 Salesforce.Com, Inc. Systems and methods of redactive messaging
US9418003B2 (en) 2012-10-10 2016-08-16 Salesforce.Com, Inc. System, method and computer program product for conditionally performing garbage collection
US9076072B2 (en) 2012-10-11 2015-07-07 Salesforce.Com, Inc. System and method for web page rendering test automation suite
US9264391B2 (en) 2012-11-01 2016-02-16 Salesforce.Com, Inc. Computer implemented methods and apparatus for providing near real-time predicted engagement level feedback to a user composing a social media message
US9171150B2 (en) 2012-12-14 2015-10-27 Salesforce.Com, Inc. System and method for dynamic analysis tracking objects for application dataflow
US9171169B2 (en) 2012-12-14 2015-10-27 Salesforce.Com, Inc. System and method for dynamic analysis wrapper objects for application dataflow
US9177137B2 (en) 2012-12-14 2015-11-03 Salesforce.Com, Inc. System and method for dynamic analysis tracking object associations for application dataflow
US9152796B2 (en) 2013-10-30 2015-10-06 Salesforce.Com, Inc. Dynamic analysis interpreter modification for application dataflow
US9170908B2 (en) 2012-12-14 2015-10-27 Salesforce.Com, Inc. System and method for dynamic analysis bytecode injection for application dataflow
US9703815B2 (en) 2012-12-17 2017-07-11 Salesforce.Com, Inc. Third party files in an on-demand database service
US9767133B2 (en) 2012-12-18 2017-09-19 Salesforce.Com, Inc. Systems and methods for alternative change processes for changes to data objects
US9195438B2 (en) 2012-12-19 2015-11-24 Salesforce.Com, Inc. System, method and computer program product for creating an application within a system
US9195854B2 (en) 2012-12-19 2015-11-24 Salesforce.Com, Inc. System and method for controlling the on and off state of features at runtime
US20140181703A1 (en) * 2012-12-22 2014-06-26 Oracle International Corporation Dynamically generated user interface
US9495079B2 (en) 2013-01-10 2016-11-15 Salesforce.Com, Inc. Persistent feeder component for displaying feed items received from information feeds of online social networks
US9778820B2 (en) 2013-01-18 2017-10-03 Salesforce.Com, Inc. Managing applications on a computing device
US9607090B2 (en) 2013-01-21 2017-03-28 Salesforce.Com, Inc. Computer implemented methods and apparatus for recommending events
US9465828B2 (en) 2013-01-22 2016-10-11 Salesforce.Com, Inc. Computer implemented methods and apparatus for identifying similar labels using collaborative filtering
US9864739B1 (en) * 2013-03-13 2018-01-09 EMC IP Holding Company LLC Automatic layout of graphical user interface screens from object data
US9823813B2 (en) 2013-03-15 2017-11-21 Salesforce.Com, Inc. Apparatus and methods for performing an action on a database record
US9501363B1 (en) 2013-03-15 2016-11-22 Nuodb, Inc. Distributed database management system with node failure detection
US20140280577A1 (en) 2013-03-15 2014-09-18 Salesforce.Com, Inc. Systems and methods for interacting with an application in a publisher
US9483526B2 (en) 2013-03-21 2016-11-01 Salesforce.Com, Inc. Automatically subscribing users of an enterprise network to a record
US9400840B2 (en) 2013-03-25 2016-07-26 Salesforce.Com, Inc. Combining topic suggestions from different topic sources to assign to textual data items
US9203881B2 (en) 2013-03-25 2015-12-01 Salesforce.Com, Inc. Systems and methods of online social environment based translation of entity methods
US9672575B2 (en) 2013-04-03 2017-06-06 Salesforce.Com, Inc. Capturing information regarding an interaction to a database
US9734187B2 (en) 2013-04-03 2017-08-15 Salesforce.Com, Inc. Atomic transactions in a NOSQL database
US9659303B2 (en) 2013-04-03 2017-05-23 Salesforce.Com, Inc. System and method for handling gamification fraud
US9965524B2 (en) 2013-04-03 2018-05-08 Salesforce.Com, Inc. Systems and methods for identifying anomalous data in large structured data sets and querying the data sets
US9246892B2 (en) 2013-04-03 2016-01-26 Salesforce.Com, Inc. System, method and computer program product for managing access to systems, products, and data based on information associated with a physical location of a user
US9398156B2 (en) 2013-04-12 2016-07-19 Salesforce.Com, Inc. Computer implemented methods and apparatus for managing agent workload in a customer service environment
US9830398B2 (en) 2013-04-17 2017-11-28 Salesforce.Com, Inc. System and method for associating dynamic objects with database records
US9785560B2 (en) 2013-04-19 2017-10-10 Salesforce.Com, Inc. Scene-isolated internet application
US9542472B2 (en) 2013-04-19 2017-01-10 Salesforce.Com, Inc. Facilitating collaboration on a record among a group of users of a feed-based enterprise network
US9641349B2 (en) 2013-04-22 2017-05-02 Salesforce.Com, Inc. Systems and methods of viral enablement of features by peer-to-peer connection
WO2014178743A1 (en) * 2013-04-29 2014-11-06 Grigorev Evgeny Aleksandrovich Method for managing a relational database
US9460474B2 (en) 2013-05-03 2016-10-04 Salesforce.Com, Inc. Providing access to a private resource in an enterprise social networking system
US9647922B2 (en) 2013-05-15 2017-05-09 Salesforce, Inc. Computer implemented methods and apparatus for trials onboarding
US9665270B2 (en) 2013-06-28 2017-05-30 Sap Se Layout algorithm for entity relation model diagram
US9892177B2 (en) 2013-07-11 2018-02-13 Salesforce.Com, Inc. Systems and methods for interacting with external content objects
US9600155B2 (en) 2013-07-15 2017-03-21 Salesforce.Com, Inc. Computer implemented methods and apparatus for customizing a data interface in an on-demand service environment
US9467434B2 (en) 2013-07-15 2016-10-11 Salesforce.Com, Inc. Document rendering service
US20150032729A1 (en) 2013-07-23 2015-01-29 Salesforce.Com, Inc. Matching snippets of search results to clusters of objects
US9798813B2 (en) 2013-07-31 2017-10-24 Salesforce.Com, Inc. Extensible person container
US9866537B2 (en) 2013-08-02 2018-01-09 Salesforce.Com, Inc. Systems and methods for long universal resource locator compression
US9426249B2 (en) 2013-08-05 2016-08-23 Salesforce.Com, Inc. Providing an improved web user interface framework for building web applications
US9524157B2 (en) 2013-08-06 2016-12-20 Salesforce.Com, Inc. Providing an improved web user interface framework for building web applications
US9244660B2 (en) 2013-08-13 2016-01-26 Salesforce.Com, Inc. Responsive self-service website template
US9921724B2 (en) 2013-08-15 2018-03-20 Salesforce.Com, Inc. Presenting data on a mobile device in communication with an on-demand database system
US9973550B2 (en) 2013-09-11 2018-05-15 Salesforce.Com, Inc. Systems and methods for applying intelligence and prioritization to calendared events
US9972015B2 (en) 2013-09-13 2018-05-15 Salesforce.Com, Inc. Methods and systems for facilitating customer support using a social post case feed and publisher
US9277432B2 (en) 2013-10-09 2016-03-01 Salesforce.Com, Inc. Systems and methods for automated on-device performance testing of mobile applications
US9665261B2 (en) 2013-10-28 2017-05-30 Salesforce.Com, Inc. Providing a user interface for customizing state transitions of panes in a bounding window
US9686348B2 (en) 2013-10-28 2017-06-20 Salesforce.Com, Inc. Inter-entity connection maps
US9529652B2 (en) 2013-11-07 2016-12-27 Salesforce.Com, Inc. Triaging computing systems
US9893905B2 (en) 2013-11-13 2018-02-13 Salesforce.Com, Inc. Collaborative platform for teams with messaging and learning across groups
US9798764B2 (en) 2013-12-20 2017-10-24 Salesforce.Com, Inc. Identifying recurring sequences of user interactions with an application
US9753703B2 (en) 2014-02-04 2017-09-05 Salesforce.Com, Inc. Generating identifiers for user interface elements of a web page of a web application
US20150339408A1 (en) * 2014-05-23 2015-11-26 Bank Of America Corporation Universal transaction repository
US9519630B2 (en) 2014-06-30 2016-12-13 Salesforce.Com, Inc. Fast CSS parser engineered for runtime use
US9509715B2 (en) 2014-08-21 2016-11-29 Salesforce.Com, Inc. Phishing and threat detection and prevention
US9774603B2 (en) 2014-08-22 2017-09-26 Salesforce.Com, Inc. Managing user permissions in relation to system events occurring in a database system
US9538377B2 (en) 2014-08-22 2017-01-03 Salesforce.Com, Inc. Switching between restricted-access websites on mobile user devices
US9865313B2 (en) 2014-08-22 2018-01-09 Salesforce.Com, Inc. System and method for dynamic caching
US9632852B2 (en) 2014-08-25 2017-04-25 Salesforce.Com, Inc. Detecting and managing flooding of multi-tenant message queues
US9349101B2 (en) 2014-08-29 2016-05-24 Salesforce.Com, Inc. Systems and methods for partitioning sets of features for a bayesian classifier
US9805051B2 (en) 2014-09-10 2017-10-31 Salesforce.Com, Inc. Synchronization and strategic storage of multiple versions of a file
US9619655B2 (en) 2014-09-12 2017-04-11 Salesforce.Com, Inc. Cloud-based security profiling, threat analysis and intelligence
US9417840B2 (en) 2014-09-16 2016-08-16 Salesforce.Com, Inc. In-memory buffer service
US9460442B2 (en) 2014-09-19 2016-10-04 Salesforce.Com, Inc. Sensor data gathering
US9826045B2 (en) 2014-09-26 2017-11-21 Oracle International Corporation Efficient means to test server generated applications on mobile device
US9851968B2 (en) 2014-09-26 2017-12-26 Oracle International Corporation High performant iOS template based application build system
US9858174B2 (en) 2014-09-26 2018-01-02 Oracle International Corporation Updatable native mobile application for testing new features
US20160092176A1 (en) * 2014-09-26 2016-03-31 Oracle International Corporation Efficient and intuitive databinding for mobile applications
US9710127B2 (en) 2014-10-09 2017-07-18 Salesforce.Com, Inc. User-customizable permissions in a computing environment
US9756110B2 (en) 2014-10-10 2017-09-05 Salesforce.Com, Inc. Systems and methods for optimizing web page load time
US9716730B2 (en) 2014-10-10 2017-07-25 Salesforce.Com, Inc. System, method and computer program product for sharing content via links
US9462002B2 (en) 2014-10-10 2016-10-04 Salesforce.Com, Inc. System, method, and computer program product for sharing files based on user profile visibility
WO2016058153A1 (en) * 2014-10-16 2016-04-21 Yahoo! Inc. Personalizing user interface (ui) elements
US9740743B2 (en) 2014-10-20 2017-08-22 Salesforce.Com, Inc. Matching objects using keys based on match rules
US9544307B2 (en) 2014-10-29 2017-01-10 Salesforce.Com, Inc. Providing a security mechanism on a mobile device
US9646064B2 (en) 2014-12-10 2017-05-09 Salesforce.Com, Inc. Template based software container
US9792008B2 (en) 2014-12-16 2017-10-17 Salesforce.Com, Inc. User interface with analytics overlay
US9805427B2 (en) 2015-01-29 2017-10-31 Salesforce.Com, Inc. Systems and methods of data mining to customize software trial demonstrations
US9785620B2 (en) 2015-02-05 2017-10-10 Salesforce.Com, Inc. Creating linked communications
WO2016130964A1 (en) 2015-02-13 2016-08-18 Abbott Laboratories Decapping and capping apparatus, systems and methods for use in diagnostic analyzers
US9965541B2 (en) 2015-02-24 2018-05-08 Salesforce.Com, Inc. Interest groups based on network feed items
US9275099B1 (en) 2015-03-09 2016-03-01 Vinyl Development LLC Source independent query language
US9940411B2 (en) 2015-04-17 2018-04-10 Salesforce.Com, Inc. Systems and methods of bypassing suppression of event bubbling for popup controls
US9773050B2 (en) 2015-06-19 2017-09-26 Salesforce.Com, Inc. User interface for aggregated task data
US9979689B2 (en) 2015-06-29 2018-05-22 Salesforce.Com, Inc. Authoring tool for creating new electronic posts
US9948743B2 (en) 2015-07-28 2018-04-17 Salesforce.Com, Inc. Managing memory usage in server systems
US9811444B2 (en) 2015-08-04 2017-11-07 Salesforce.Com, Inc. Testing software enhancements in database applications
US9420104B1 (en) 2015-08-18 2016-08-16 Salesforce.Com, Inc. Systems and methods for an omni-channel routing broker
US9710638B2 (en) 2015-08-28 2017-07-18 Salesforce.Com, Inc. Unicode-based image generation and testing
US9619642B2 (en) 2015-08-28 2017-04-11 Salesforce.Com, Inc. Unicode-based image generation and testing
US9710637B2 (en) 2015-08-28 2017-07-18 Salesforce.Com, Inc. Unicode-based image generation and testing
US9767040B2 (en) 2015-08-31 2017-09-19 Salesforce.Com, Inc. System and method for generating and storing real-time analytics metric data using an in memory buffer service consumer framework
US9905034B2 (en) 2015-09-14 2018-02-27 Salesforce.Com, Inc. Secure isolation of scripting from native graphic rendering of animated data visualizations
US9658801B2 (en) 2015-09-15 2017-05-23 Salesforce.Com, Inc. System having in-memory buffer service, temporary events file storage system and backup events file uploader service
US9946593B2 (en) 2015-09-18 2018-04-17 Salesforce.Com, Inc. Recovery strategy for a stream processing system
US9842000B2 (en) 2015-09-18 2017-12-12 Salesforce.Com, Inc. Managing processing of long tail task sequences in a stream processing framework
US9965330B2 (en) 2015-09-18 2018-05-08 Salesforce.Com, Inc. Maintaining throughput of a stream processing framework while increasing processing load
US9977797B2 (en) 2015-09-28 2018-05-22 Salesforce.Com, Inc. Combined directed graphs
US9766965B2 (en) 2015-11-25 2017-09-19 Salesforce.Com, Inc. System and method for monitoring and detecting faulty storage devices
US9965634B2 (en) 2016-01-15 2018-05-08 Salesforce.Com, Inc. Space-efficient storage of encrypted data
US9864867B2 (en) 2016-02-23 2018-01-09 Salesforce.Com, Inc. Secure persistent communication between related domains using cookies
US9846635B2 (en) 2016-03-18 2017-12-19 Salesforce.Com, Inc. Making production data available for testing in a non-production environment
US9980112B1 (en) 2016-11-23 2018-05-22 Salesforce.Com, Inc. System and method for coordinating an emergency response at a facility
US9961519B1 (en) 2017-08-01 2018-05-01 Salesforce.Com, Inc. Facilitating mobile device interaction with an enterprise database system

Citations (73)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4631661A (en) * 1982-12-07 1986-12-23 International Business Machines Corporation Fail-safe data processing system
US5353401A (en) * 1992-11-06 1994-10-04 Ricoh Company, Ltd. Automatic interface layout generator for database systems
US5428776A (en) * 1991-03-12 1995-06-27 Wang Laboratories, Inc. System for composing a graphical interface to a relational database which displays a network of query and source icons
US5499371A (en) * 1993-07-21 1996-03-12 Persistence Software, Inc. Method and apparatus for automatic generation of object oriented code for mapping relational data to objects
US5523942A (en) * 1994-03-31 1996-06-04 New England Mutual Life Insurance Company Design grid for inputting insurance and investment product information in a computer system
US5548749A (en) * 1993-10-29 1996-08-20 Wall Data Incorporated Semantic orbject modeling system for creating relational database schemas
US5550971A (en) * 1993-06-30 1996-08-27 U S West Technologies, Inc. Method and system for generating a user interface adaptable to various database management systems
US5553218A (en) * 1992-03-09 1996-09-03 International Business Machines Corporation Graphical user interface for relating key index properties to database table columns
US5615367A (en) * 1993-05-25 1997-03-25 Borland International, Inc. System and methods including automatic linking of tables for improved relational database modeling with interface
US5627979A (en) * 1994-07-18 1997-05-06 International Business Machines Corporation System and method for providing a graphical user interface for mapping and accessing objects in data stores
US5701543A (en) * 1995-09-19 1997-12-23 Noritsu Koki Co., Ltd. Cartridge case stocker apparatus in automatic film development processor machine
US5764973A (en) * 1994-02-08 1998-06-09 Enterworks.Com, Inc. System for generating structured query language statements and integrating legacy systems
US5778375A (en) * 1996-06-27 1998-07-07 Microsoft Corporation Database normalizing system
US5802514A (en) * 1996-04-09 1998-09-01 Vision Software Tools, Inc. Automated client/server development tool using drag-and-drop metaphor
US5812134A (en) * 1996-03-28 1998-09-22 Critical Thought, Inc. User interface navigational system & method for interactive representation of information contained within a database
US5819264A (en) * 1995-04-03 1998-10-06 Dtl Data Technologies Ltd. Associative search method with navigation for heterogeneous databases including an integration mechanism configured to combine schema-free data models such as a hyperbase
US5832498A (en) * 1994-09-13 1998-11-03 Bull, S.A. Device for generating object-oriented interfaces for relational data bases and a process implemented by this device
US5873093A (en) * 1994-12-07 1999-02-16 Next Software, Inc. Method and apparatus for mapping objects to a data source
US5905985A (en) * 1997-06-30 1999-05-18 International Business Machines Corporation Relational database modifications based on multi-dimensional database modifications
US5937409A (en) * 1997-07-25 1999-08-10 Oracle Corporation Integrating relational databases in an object oriented environment
US5950190A (en) * 1997-05-13 1999-09-07 Aptek, Inc. Dynamic, self-modifying graphical user interface for relational database applications
US5966707A (en) * 1997-12-02 1999-10-12 International Business Machines Corporation Method for managing a plurality of data processes residing in heterogeneous data repositories
US5986673A (en) * 1997-10-17 1999-11-16 Martz; David R. Method for relational ordering and displaying multidimensional data
US6012067A (en) * 1998-03-02 2000-01-04 Sarkar; Shyam Sundar Method and apparatus for storing and manipulating objects in a plurality of relational data managers on the web
US6016394A (en) * 1997-09-17 2000-01-18 Tenfold Corporation Method and system for database application software creation requiring minimal programming
US6029172A (en) * 1996-08-28 2000-02-22 U.S. Philips Corporation Method and system for selecting an information item
US6035300A (en) * 1995-12-15 2000-03-07 International Business Machines Corporation Method and apparatus for generating a user interface from the entity/attribute/relationship model of a database
US6058391A (en) * 1997-12-17 2000-05-02 Mci Communications Corporation Enhanced user view/update capability for managing data from relational tables
US6061394A (en) * 1996-11-28 2000-05-09 Anritsu Corporation Digital communication system modulated signal generation apparatus incorporating fading simulator
US6069627A (en) * 1995-11-01 2000-05-30 International Business Machines Corporation Extender user interface
US6101502A (en) * 1997-09-26 2000-08-08 Ontos, Inc. Object model mapping and runtime engine for employing relational database with object oriented software
US6175837B1 (en) * 1998-06-29 2001-01-16 Sun Microsystems, Inc. Object-relational mapping toll that processes views
US6199068B1 (en) * 1997-09-11 2001-03-06 Abb Power T&D Company Inc. Mapping interface for a distributed server to translate between dissimilar file formats
WO2001033388A2 (en) * 1999-11-01 2001-05-10 Sherwood International Group Limited Method and system for multi-user access of a database over a network
US6266675B1 (en) * 1997-10-07 2001-07-24 Phycom Corporation System and method for using a relational database to enable the dynamic configuration of an application program
US20010011364A1 (en) * 1998-01-07 2001-08-02 Everett W. Stoub System for converting scrolling display to non-scrolling columnar display
US6279008B1 (en) * 1998-06-29 2001-08-21 Sun Microsystems, Inc. Integrated graphical user interface method and apparatus for mapping between objects and databases
US20010034733A1 (en) * 2000-03-03 2001-10-25 Michel Prompt System and method for providing access to databases via directories and other hierarchical structures and interfaces
US6314415B1 (en) * 1998-11-04 2001-11-06 Cch Incorporated Automated forms publishing system and method using a rule-based expert system to dynamically generate a graphical user interface
US20010056460A1 (en) * 2000-04-24 2001-12-27 Ranjit Sahota Method and system for transforming content for execution on multiple platforms
US6374252B1 (en) * 1995-04-24 2002-04-16 I2 Technologies Us, Inc. Modeling of object-oriented database structures, translation to relational database structures, and dynamic searches thereon
US20020088008A1 (en) * 2000-08-21 2002-07-04 Markel Steven O. System and method for distribution of interactive content to multiple targeted presentation platforms
US20020087986A1 (en) * 2000-08-21 2002-07-04 Markel Steven O. System and method for web based enhanced interactive television content page layout
US20020138497A1 (en) * 2001-03-26 2002-09-26 International Business Machines Corporation Method, system, and program for implementing a database trigger
US6493704B1 (en) * 1999-09-13 2002-12-10 Oracle Corporation Method and apparatus for using metadata to dynamically generate a display page to solicit input from a user
US6496833B1 (en) * 1999-11-01 2002-12-17 Sun Microsystems, Inc. System and method for generating code for query object interfacing
US6499036B1 (en) * 1998-08-12 2002-12-24 Bank Of America Corporation Method and apparatus for data item movement between disparate sources and hierarchical, object-oriented representation
US20030004971A1 (en) * 2001-06-29 2003-01-02 Gong Wen G. Automatic generation of data models and accompanying user interfaces
US6523045B1 (en) * 1998-05-29 2003-02-18 Plexus Systems, Llc Graphical user interface shop floor control system
US20030084046A1 (en) * 2001-10-25 2003-05-01 Abm Systems Ltd. Versatile database interface system
US6571232B1 (en) * 1999-11-01 2003-05-27 Sun Microsystems, Inc. System and method for browsing database schema information
US20030135825A1 (en) * 2001-12-05 2003-07-17 Matthew Gertner Dynamically generated mark-up based graphical user interfaced with an extensible application framework with links to enterprise resources
US6609128B1 (en) * 1999-07-30 2003-08-19 Accenture Llp Codes table framework design in an E-commerce architecture
US6631519B1 (en) * 2000-03-30 2003-10-07 Microsoft Corporation Automated schema and interface generation
US6640231B1 (en) * 2000-10-06 2003-10-28 Ontology Works, Inc. Ontology for database design and application development
US20030220893A1 (en) * 2002-05-23 2003-11-27 International Business Machines Corporation Dynamic content generation/regeneration for a database schema abstraction
US20030225768A1 (en) * 2002-06-03 2003-12-04 Microsoft Corporation Workload analysis tool for relational databases
US20040015476A1 (en) * 2000-09-01 2004-01-22 Twaddle Graham Kennedy Method and system for dynamic web-page generation, and computer-readable storage
US6697808B1 (en) * 2001-06-19 2004-02-24 Microstrategy, Inc. Method and system for performing advanced object searching of a metadata repository used by a decision support system
US6738077B1 (en) * 2000-07-18 2004-05-18 Apple Computer, Inc. Dynamic generation and automated distribution of user interface from database model
US6857123B1 (en) * 1998-12-18 2005-02-15 International Business Machines Corporation Method and apparatus for a Meta Data Service in a data processing system
US6867789B1 (en) * 2000-02-15 2005-03-15 Bank One, Delaware, National Association System and method for generating graphical user interfaces
US6915301B2 (en) * 1998-08-25 2005-07-05 International Business Machines Corporation Dynamic object properties
US20050209892A1 (en) * 2004-03-19 2005-09-22 Miller Jonathan K [Automated system and method for providing accurate, non-invasive insurance status verification]
US7062502B1 (en) * 2001-12-28 2006-06-13 Kesler John N Automated generation of dynamic data entry user interface for relational database management systems
US7155667B1 (en) * 2000-06-21 2006-12-26 Microsoft Corporation User interface for integrated spreadsheets and word processing tables
US7302436B2 (en) * 2003-10-02 2007-11-27 Bayerische Motoren Werke Aktiengesellschaft Business workflow database and user system
US7318066B2 (en) * 2000-10-31 2008-01-08 Michael Philip Kaufman System and method for generating automatic user interface for arbitrarily complex or large databases
US7461052B2 (en) * 2004-12-06 2008-12-02 International Business Machines Corporation Abstract query plan
US7730056B2 (en) * 2006-12-28 2010-06-01 Sap Ag Software and method for utilizing a common database layout
US7885981B2 (en) * 2000-10-31 2011-02-08 Michael Philip Kaufman System and method for generating automatic user interface for arbitrarily complex or large databases
US8126937B2 (en) * 2004-10-05 2012-02-28 Sap Ag Visual database modeling
US8161081B2 (en) * 2001-03-16 2012-04-17 Michael Philip Kaufman System and method for generating automatic user interface for arbitrarily complex or large databases

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4631664A (en) 1983-07-19 1986-12-23 Bachman Information Systems, Inc. Partnership data base management system and method
JPH03164816A (en) 1989-11-22 1991-07-16 Mitsubishi Electric Corp Information processor
US5701453A (en) 1993-07-01 1997-12-23 Informix Software, Inc. Logical schema to allow access to a relational database without using knowledge of the database structure
US20020010000A1 (en) 2000-01-25 2002-01-24 Vincent Chern Knowledge-based information retrieval system and method for wireless communication device
FR2813492B1 (en) * 2000-09-06 2006-09-01 Hydrotronic Cutting bar for combine or similar means

Patent Citations (76)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4631661A (en) * 1982-12-07 1986-12-23 International Business Machines Corporation Fail-safe data processing system
US5428776A (en) * 1991-03-12 1995-06-27 Wang Laboratories, Inc. System for composing a graphical interface to a relational database which displays a network of query and source icons
US5553218A (en) * 1992-03-09 1996-09-03 International Business Machines Corporation Graphical user interface for relating key index properties to database table columns
US5353401A (en) * 1992-11-06 1994-10-04 Ricoh Company, Ltd. Automatic interface layout generator for database systems
US5495567A (en) * 1992-11-06 1996-02-27 Ricoh Company Ltd. Automatic interface layout generator for database systems
US5615367A (en) * 1993-05-25 1997-03-25 Borland International, Inc. System and methods including automatic linking of tables for improved relational database modeling with interface
US5550971A (en) * 1993-06-30 1996-08-27 U S West Technologies, Inc. Method and system for generating a user interface adaptable to various database management systems
US5499371A (en) * 1993-07-21 1996-03-12 Persistence Software, Inc. Method and apparatus for automatic generation of object oriented code for mapping relational data to objects
US5548749A (en) * 1993-10-29 1996-08-20 Wall Data Incorporated Semantic orbject modeling system for creating relational database schemas
US5764973A (en) * 1994-02-08 1998-06-09 Enterworks.Com, Inc. System for generating structured query language statements and integrating legacy systems
US5523942A (en) * 1994-03-31 1996-06-04 New England Mutual Life Insurance Company Design grid for inputting insurance and investment product information in a computer system
US5627979A (en) * 1994-07-18 1997-05-06 International Business Machines Corporation System and method for providing a graphical user interface for mapping and accessing objects in data stores
US5832498A (en) * 1994-09-13 1998-11-03 Bull, S.A. Device for generating object-oriented interfaces for relational data bases and a process implemented by this device
US5873093A (en) * 1994-12-07 1999-02-16 Next Software, Inc. Method and apparatus for mapping objects to a data source
US5819264A (en) * 1995-04-03 1998-10-06 Dtl Data Technologies Ltd. Associative search method with navigation for heterogeneous databases including an integration mechanism configured to combine schema-free data models such as a hyperbase
US6374252B1 (en) * 1995-04-24 2002-04-16 I2 Technologies Us, Inc. Modeling of object-oriented database structures, translation to relational database structures, and dynamic searches thereon
US5701543A (en) * 1995-09-19 1997-12-23 Noritsu Koki Co., Ltd. Cartridge case stocker apparatus in automatic film development processor machine
US6069627A (en) * 1995-11-01 2000-05-30 International Business Machines Corporation Extender user interface
US6035300A (en) * 1995-12-15 2000-03-07 International Business Machines Corporation Method and apparatus for generating a user interface from the entity/attribute/relationship model of a database
US5812134A (en) * 1996-03-28 1998-09-22 Critical Thought, Inc. User interface navigational system & method for interactive representation of information contained within a database
US5802514A (en) * 1996-04-09 1998-09-01 Vision Software Tools, Inc. Automated client/server development tool using drag-and-drop metaphor
US5778375A (en) * 1996-06-27 1998-07-07 Microsoft Corporation Database normalizing system
US6029172A (en) * 1996-08-28 2000-02-22 U.S. Philips Corporation Method and system for selecting an information item
US6061394A (en) * 1996-11-28 2000-05-09 Anritsu Corporation Digital communication system modulated signal generation apparatus incorporating fading simulator
US5950190A (en) * 1997-05-13 1999-09-07 Aptek, Inc. Dynamic, self-modifying graphical user interface for relational database applications
US5905985A (en) * 1997-06-30 1999-05-18 International Business Machines Corporation Relational database modifications based on multi-dimensional database modifications
US5937409A (en) * 1997-07-25 1999-08-10 Oracle Corporation Integrating relational databases in an object oriented environment
US6199068B1 (en) * 1997-09-11 2001-03-06 Abb Power T&D Company Inc. Mapping interface for a distributed server to translate between dissimilar file formats
US6016394A (en) * 1997-09-17 2000-01-18 Tenfold Corporation Method and system for database application software creation requiring minimal programming
US6101502A (en) * 1997-09-26 2000-08-08 Ontos, Inc. Object model mapping and runtime engine for employing relational database with object oriented software
US6266675B1 (en) * 1997-10-07 2001-07-24 Phycom Corporation System and method for using a relational database to enable the dynamic configuration of an application program
US5986673A (en) * 1997-10-17 1999-11-16 Martz; David R. Method for relational ordering and displaying multidimensional data
US5966707A (en) * 1997-12-02 1999-10-12 International Business Machines Corporation Method for managing a plurality of data processes residing in heterogeneous data repositories
US6058391A (en) * 1997-12-17 2000-05-02 Mci Communications Corporation Enhanced user view/update capability for managing data from relational tables
US20010011364A1 (en) * 1998-01-07 2001-08-02 Everett W. Stoub System for converting scrolling display to non-scrolling columnar display
US6012067A (en) * 1998-03-02 2000-01-04 Sarkar; Shyam Sundar Method and apparatus for storing and manipulating objects in a plurality of relational data managers on the web
US6523045B1 (en) * 1998-05-29 2003-02-18 Plexus Systems, Llc Graphical user interface shop floor control system
US6279008B1 (en) * 1998-06-29 2001-08-21 Sun Microsystems, Inc. Integrated graphical user interface method and apparatus for mapping between objects and databases
US6175837B1 (en) * 1998-06-29 2001-01-16 Sun Microsystems, Inc. Object-relational mapping toll that processes views
US6499036B1 (en) * 1998-08-12 2002-12-24 Bank Of America Corporation Method and apparatus for data item movement between disparate sources and hierarchical, object-oriented representation
US6915301B2 (en) * 1998-08-25 2005-07-05 International Business Machines Corporation Dynamic object properties
US6314415B1 (en) * 1998-11-04 2001-11-06 Cch Incorporated Automated forms publishing system and method using a rule-based expert system to dynamically generate a graphical user interface
US6857123B1 (en) * 1998-12-18 2005-02-15 International Business Machines Corporation Method and apparatus for a Meta Data Service in a data processing system
US6609128B1 (en) * 1999-07-30 2003-08-19 Accenture Llp Codes table framework design in an E-commerce architecture
US6493704B1 (en) * 1999-09-13 2002-12-10 Oracle Corporation Method and apparatus for using metadata to dynamically generate a display page to solicit input from a user
US6496833B1 (en) * 1999-11-01 2002-12-17 Sun Microsystems, Inc. System and method for generating code for query object interfacing
WO2001033388A2 (en) * 1999-11-01 2001-05-10 Sherwood International Group Limited Method and system for multi-user access of a database over a network
US6571232B1 (en) * 1999-11-01 2003-05-27 Sun Microsystems, Inc. System and method for browsing database schema information
US6867789B1 (en) * 2000-02-15 2005-03-15 Bank One, Delaware, National Association System and method for generating graphical user interfaces
US20010034733A1 (en) * 2000-03-03 2001-10-25 Michel Prompt System and method for providing access to databases via directories and other hierarchical structures and interfaces
US20060020586A1 (en) * 2000-03-03 2006-01-26 Michel Prompt System and method for providing access to databases via directories and other hierarchical structures and interfaces
US6631519B1 (en) * 2000-03-30 2003-10-07 Microsoft Corporation Automated schema and interface generation
US20010056460A1 (en) * 2000-04-24 2001-12-27 Ranjit Sahota Method and system for transforming content for execution on multiple platforms
US7155667B1 (en) * 2000-06-21 2006-12-26 Microsoft Corporation User interface for integrated spreadsheets and word processing tables
US6738077B1 (en) * 2000-07-18 2004-05-18 Apple Computer, Inc. Dynamic generation and automated distribution of user interface from database model
US20020087986A1 (en) * 2000-08-21 2002-07-04 Markel Steven O. System and method for web based enhanced interactive television content page layout
US20020088008A1 (en) * 2000-08-21 2002-07-04 Markel Steven O. System and method for distribution of interactive content to multiple targeted presentation platforms
US20040015476A1 (en) * 2000-09-01 2004-01-22 Twaddle Graham Kennedy Method and system for dynamic web-page generation, and computer-readable storage
US6640231B1 (en) * 2000-10-06 2003-10-28 Ontology Works, Inc. Ontology for database design and application development
US7318066B2 (en) * 2000-10-31 2008-01-08 Michael Philip Kaufman System and method for generating automatic user interface for arbitrarily complex or large databases
US7885981B2 (en) * 2000-10-31 2011-02-08 Michael Philip Kaufman System and method for generating automatic user interface for arbitrarily complex or large databases
US8161081B2 (en) * 2001-03-16 2012-04-17 Michael Philip Kaufman System and method for generating automatic user interface for arbitrarily complex or large databases
US20020138497A1 (en) * 2001-03-26 2002-09-26 International Business Machines Corporation Method, system, and program for implementing a database trigger
US6697808B1 (en) * 2001-06-19 2004-02-24 Microstrategy, Inc. Method and system for performing advanced object searching of a metadata repository used by a decision support system
US20030004971A1 (en) * 2001-06-29 2003-01-02 Gong Wen G. Automatic generation of data models and accompanying user interfaces
US20030084046A1 (en) * 2001-10-25 2003-05-01 Abm Systems Ltd. Versatile database interface system
US20030135825A1 (en) * 2001-12-05 2003-07-17 Matthew Gertner Dynamically generated mark-up based graphical user interfaced with an extensible application framework with links to enterprise resources
US7401094B1 (en) * 2001-12-28 2008-07-15 Kesler John N Automated generation of dynamic data entry user interface for relational database management systems
US7062502B1 (en) * 2001-12-28 2006-06-13 Kesler John N Automated generation of dynamic data entry user interface for relational database management systems
US20030220893A1 (en) * 2002-05-23 2003-11-27 International Business Machines Corporation Dynamic content generation/regeneration for a database schema abstraction
US20030225768A1 (en) * 2002-06-03 2003-12-04 Microsoft Corporation Workload analysis tool for relational databases
US7302436B2 (en) * 2003-10-02 2007-11-27 Bayerische Motoren Werke Aktiengesellschaft Business workflow database and user system
US20050209892A1 (en) * 2004-03-19 2005-09-22 Miller Jonathan K [Automated system and method for providing accurate, non-invasive insurance status verification]
US8126937B2 (en) * 2004-10-05 2012-02-28 Sap Ag Visual database modeling
US7461052B2 (en) * 2004-12-06 2008-12-02 International Business Machines Corporation Abstract query plan
US7730056B2 (en) * 2006-12-28 2010-06-01 Sap Ag Software and method for utilizing a common database layout

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WebDB, Tutorial Guide Release 2.2. OCT 1999. <http://docs.oracle.com/cd/A87860_01/doc/webdb.817/a77075.pdf> *

Cited By (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030159136A1 (en) * 2001-09-28 2003-08-21 Huang Xiao Fei Method and system for server synchronization with a computing device
US7761535B2 (en) * 2001-09-28 2010-07-20 Siebel Systems, Inc. Method and system for server synchronization with a computing device
US20070067710A1 (en) * 2005-09-22 2007-03-22 Clark David K Navigating table data with mouse actions
US8826112B2 (en) * 2005-09-22 2014-09-02 International Business Machines Corporation Navigating table data with mouse actions
US20070143398A1 (en) * 2005-12-16 2007-06-21 Jean Graham Central work-product management system for coordinated collaboration with remote users
US7761591B2 (en) * 2005-12-16 2010-07-20 Jean A. Graham Central work-product management system for coordinated collaboration with remote users
US20090327212A1 (en) * 2006-01-09 2009-12-31 Trevor Bell Efficient SQL access to point data and relational data
US8078598B2 (en) * 2006-01-09 2011-12-13 Siemens Aktiengesellschaft Efficient SQL access to point data and relational data
US8869020B2 (en) * 2006-12-27 2014-10-21 Sap Ag Method and system for generating relational spreadsheets
US20080162532A1 (en) * 2006-12-27 2008-07-03 Rakshit Daga Method and system for generating relational spreadsheets
US20080162553A1 (en) * 2006-12-27 2008-07-03 Rakshit Daga Method and system for generating string-based addresses
US8015210B2 (en) 2006-12-27 2011-09-06 Sap Ag Method and system for generating string-based addresses
US8719124B2 (en) 2007-04-30 2014-05-06 Textura Corporation Construction payment management systems and methods with specified billing features
US9824375B2 (en) 2007-04-30 2017-11-21 Textura Corporation Construction payment management systems and methods with specified billing features
US9372876B2 (en) * 2007-10-26 2016-06-21 Microsoft Technology Licensing, Llc Metadata driven reporting and editing of databases
US20140012883A1 (en) * 2007-10-26 2014-01-09 Microsoft Corporation Metadata driven reporting and editing of databases
US20090248710A1 (en) * 2008-03-27 2009-10-01 Microsoft Corporation Database Part Table Junctioning
US7895174B2 (en) * 2008-03-27 2011-02-22 Microsoft Corporation Database part table junctioning
US20110107243A1 (en) * 2009-11-05 2011-05-05 International Business Machines Corporation Searching Existing User Interfaces to Enable Design, Development and Provisioning of User Interfaces
US8595236B2 (en) * 2009-11-05 2013-11-26 International Business Machines Corporation Searching existing user interfaces to enable design, development and provisioning of user interfaces
US20120137359A1 (en) * 2010-11-29 2012-05-31 Groupe Cgi Inc. Method For Storing (Hiding) A Key In A Table And Corresponding Method For Retrieving The Key From The Table
US20120151382A1 (en) * 2010-12-14 2012-06-14 Microsoft Corporation Generating and managing electronic documentation
US9286061B2 (en) * 2010-12-14 2016-03-15 Microsoft Technology Licensing, Llc Generating and managing electronic documentation
US9141650B1 (en) * 2011-12-06 2015-09-22 The Boeing Company Methods and systems for filtering tree node data to determine part and assembly relationships
US20130179807A1 (en) * 2012-01-10 2013-07-11 General Motors Llc Method and system for database browsing
US9201575B2 (en) * 2012-01-10 2015-12-01 General Motors Llc Method and system for database browsing
US20140047377A1 (en) * 2012-08-09 2014-02-13 Sap Ag Retrieving data from an external data source
US20140149470A1 (en) * 2012-11-27 2014-05-29 Sandeep Rawal Systems and methods for storing and populating forms
US20150286720A1 (en) * 2012-12-11 2015-10-08 Tmm Data, Llc Methods and systems for collecting, managing, and sharing data
US20140310262A1 (en) * 2013-03-15 2014-10-16 Cerinet Usa Inc. Multiple schema repository and modular database procedures
US20160117416A1 (en) * 2014-10-27 2016-04-28 Joseph Wong Automatic detection of queries missing order-by via unit test
US9767219B2 (en) * 2014-10-27 2017-09-19 Successfactors, Inc. Automatic detection of queries missing order-by via unit test
WO2016179536A1 (en) * 2015-05-07 2016-11-10 51 Maps, Inc. Secure container platform for resource access and placement on unmanaged and unsecured devices

Also Published As

Publication number Publication date Type
US7401094B1 (en) 2008-07-15 grant
US7062502B1 (en) 2006-06-13 grant

Similar Documents

Publication Publication Date Title
Prat et al. A UML-based data warehouse design method
Ceri et al. Web Modeling Language (WebML): a modeling language for designing Web sites
US7089239B1 (en) Method and system for preventing mutually exclusive content entities stored in a data repository to be included in the same compilation of content
US7080076B1 (en) System and method for efficiently drafting a legal document using an authenticated clause table
US7613993B1 (en) Prerequisite checking in a system for creating compilations of content
US7299202B2 (en) Intelligent multimedia e-catalog
US7340481B1 (en) Method and system for adding user-provided content to a content object stored in a data repository
US7472137B2 (en) Data query and location through a central ontology model
US7096222B2 (en) Methods and systems for auto-instantiation of storage hierarchy for project plan
US6928431B2 (en) Dynamic end user specific customization of an application&#39;s physical data layer through a data repository abstraction layer
US5832496A (en) System and method for performing intelligent analysis of a computer database
US7043488B1 (en) Method and system for storing hierarchical content objects in a data repository
US6839701B1 (en) Hitmask for querying hierarchically related content entities
US7346844B1 (en) Method and system for moving content in a content object stored in a data repository
US7401097B1 (en) System and method for creating compilations of content
US7634478B2 (en) Metadata driven intelligent data navigation
US7620647B2 (en) Hierarchy global management system and user interface
US6003039A (en) Data repository with user accessible and modifiable reuse criteria
US20100023498A1 (en) Relationship management in a data abstraction model
US6986102B1 (en) Method and configurable model for storing hierarchical data in a non-hierarchical data repository
US7236966B1 (en) Method and system for providing a user-customized electronic book
US6374252B1 (en) Modeling of object-oriented database structures, translation to relational database structures, and dynamic searches thereon
US6895409B2 (en) Method and apparatus for creating an adaptive application
US20020091677A1 (en) Content dereferencing in website development
US4888690A (en) Interactive error handling means in database management

Legal Events

Date Code Title Description
AS Assignment

Owner name: UNIFI SCIENTIFIC ADVANCES, INC., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MIND CONCEPTS TECHNOLOGY, LLC;REEL/FRAME:025500/0683

Effective date: 20100528

AS Assignment

Owner name: ADVANCED DYNAMIC INTERFACES, LLC, TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UNIFI SCIENTIFIC ADVANCES, INC.;REEL/FRAME:028267/0793

Effective date: 20120104