Application builder with automated data objects creation

Patent metadata

Field	Value
Publication number	US-10824403-B2
Application number	US-201615186414-A
Country	US
Kind code	B2
Filing date	Jun 17, 2016
Priority date	Oct 23, 2015
Publication date	Nov 3, 2020
Grant date	Nov 3, 2020

Abstract

Techniques for simplifying the process of building an application and making changes to the application. The process of creating and editing an application is simplified such that a non-technical user can build and edit applications without having any programming or technical knowledge. An infrastructure is provided for building an application that enables a user to create an application by simply designing a user interface for the application using one or more provided user interface (UI) components. A user can build a full executable application by simply using UI components and the back end data objects and schemas used for the application are automatically created and updated by the infrastructure. Due to the automatic creation of the data objects and schemas and the automatic binding of these to the UI components of the application, the application being built is able to run or execute while being built and/or edited.

First claim

What is claimed:

1. A computer-implemented method, the method comprising:
automatically receiving, at a server system, updated application metadata from a client computer for a graphical user interface (GUI) being developed in a view model on the client computer for an application, the application metadata including an updated data model, an updated view model and an updated mapping information, wherein the updated application a first change to the GUI being developed due to addition of a graphical user interface component to a page of the application in the view model on the client computer, wherein the GUI is developed in accordance with a Model-View-ViewModel (MVVM) architecture;
automatically comparing, by a server-side synchronizer module of the server system, the updated data model with a first data model stored in an application store of the server system;
determining, by the server-side synchronizer module of the server system, a change to the first data model based on the comparison;
automatically updating, at the server system during design of the GUI so as to perform a dynamic live update of the first data model, the first data model created for the application based upon the GUI being developed, the updating comprising creating a new data object for the graphical user interface component by updating a database schema created for the application, wherein the new data object created for the graphical user interface component is a table stored in a database;
automatically binding, by the server system, the new data object to the graphical user interface component so as to bind the view model to the first data model during design of the GUI using the received updating mapping information in the updated application metadata;
receiving, at the server system from the client computer, metadat information indicative of a second change to the GUI being developed on the client computer, the second change indicating a change to an attribute of the graphical user interface component, wherein the second change is a deletion or an addition of a column to the graphical user interface component;
responsive to receiving the information indicative of the second change, automatically deleting or adding, at the server system, a column from or to the new data object corresponding to the column deleted or added by the second change by updating the database schema associated with the first data model for the application; and
while the GUI is being developed on the client computer:
receiving, at the server system, data entered into the graphical user interface component on the client computer; and
storing the data in the new data object in the database.

2. The computer-implemented method of claim 1 , wherein the graphical user interface component is a graphical table component.

3. The computer-implemented method of claim 1 , wherein the application metadata comprises data describing a view structure of the application.

4. The computer-implemented method of claim 1 , further comprising refreshing the GUI being developed on the client computer based on the first change.

5. The computer-implemented method of claim 1 , further comprising refreshing the GUI being developed on the client computer based on the second change.

6. The computer-implemented method of claim 1 , further comprising:
refreshing the GUI being developed on the client computer a first time based on the first change; and
refreshing the GUI being developed on the client computer a second time based on the second change.

7. The computer-implemented method of claim 1 , wherein the second change further indicates a change made to a title of a particular column of the graphical user interface component; and
the method further comprising:
responsive to receiving the information indicative of the second change, making a change, at the server system, to a title of a column of the new data object corresponding to the particular column of the graphical user interface.

8. A system comprising one or more processors configured to perform:
automatically receiving, at the system, updated application metadata from a client computer for a graphical user interface (GUI) being developed in a view model on the client computer for an application, the application metadata including an undated data model, and updated view model and an updated mapping information, wherein the updated application metadata indicates a first change to the GUI being developed due to addition of a graphical user interface component to a page of the application in the view model on the client computer, wherein the GUI is developed in accordance with a Model-View-ViewModel (MVVM) architecture;
automatically comparing, by a server-side synchronizer module of the system, the updated data model with a first data model stored in an application store of the system;
determining, by the server-side synchronizer module of the system, a change to the first data model based on the comparison;
automatically updating, during design of the GUI so as to perform a dynamic live update of the first data model, the first data model created for the application based upon the GUI being developed, the updating comprising creating a new data object for the graphical user interface component by updating a database schema created for the application, wherein the new data object created for the graphical user interface component is a table stored in a database;
automatically binding the new data object to the graphical user interface component so as to bind the view model to the first data model during design of the GUI using the received updated mapping information in the updated application metadata;
receiving, at the system from the client computer, metadata information indicative of a second change to the GUI being developed on the client computer, the second change indicating a change to an attribute of the graphical user interface component, wherein the second change is a deletion or an addition of a column to the graphical user interface component;
responsive to receiving the information indicative of the second change, deleting or adding, at the system, a column from or to the new data object corresponding to a column deleted or added by the second change by updating the database schema associated with the first data model for the application; and
while the GUI is being developed on the client computer:
receiving, at the system, data entered into the graphical user interface component on the client computer; and
storing the data in the new data object in the database.

9. The system of claim 8 , wherein the graphical user interface component is a graphical table component.

10. The system of claim 8 , wherein the application metadata comprises data describing a view structure of the application.

11. The system of claim 8 , further comprising refreshing the GUI being developed on the client computer based on the first change.

12. The system of claim 8 , further comprising refreshing the GUI being developed on the client computer based on the second change.

13. The system of claim 8 , further comprising:
refreshing the GUI being developed on the client computer a first time based on the first change; and
refreshing the GUI being developed on the client computer a second time based on the second change.

14. The system of claim 8 , wherein the second change further indicates a change made to a title of a particular column of the graphical user interface component; and
responsive to receiving the information indicative of the second change, making a change, at the system, to a title of a column of the new data object correspond

Assignees

• Oracle Int Corp

Inventors

• Fukala Marek

Classifications

• G06F16/252

  between a Database Management System and a front-end application · CPC title

• G06F8/34

  Graphical or visual programming · CPC title

• G06F8/38 Primary

  for implementing user interfaces · CPC title

• G06F8/355 Primary

  Round-trip engineering · CPC title

• G06F8/35

  model driven · CPC title