US20230229671A1 - Web services having live data updates - Google Patents
Web services having live data updates Download PDFInfo
- Publication number
- US20230229671A1 US20230229671A1 US18/123,497 US202318123497A US2023229671A1 US 20230229671 A1 US20230229671 A1 US 20230229671A1 US 202318123497 A US202318123497 A US 202318123497A US 2023229671 A1 US2023229671 A1 US 2023229671A1
- Authority
- US
- United States
- Prior art keywords
- data
- content
- webpage form
- record
- user
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 71
- 230000004044 response Effects 0.000 claims abstract description 31
- 230000006854 communication Effects 0.000 claims description 17
- 238000004891 communication Methods 0.000 claims description 17
- 230000007175 bidirectional communication Effects 0.000 claims description 6
- 238000004590 computer program Methods 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 49
- 238000012545 processing Methods 0.000 description 29
- 238000011161 development Methods 0.000 description 19
- 230000001902 propagating effect Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 13
- 230000009471 action Effects 0.000 description 8
- 230000000875 corresponding effect Effects 0.000 description 8
- 230000002085 persistent effect Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000000644 propagated effect Effects 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 239000000203 mixture Substances 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000032258 transport Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000009056 active transport Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F16/972—Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/273—Asynchronous replication or reconciliation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
A method, apparatus, and computer program product for communicating real-time updates among web clients. A structured data object is composed from a set of data nodes according to a domain specific language in response to requesting access to a data within a human resources database. The structured data object is interpreted within a context of a record ID/form to identify content for the web page and to determine whether real-time updates are enabled for the web page. Interpreting the structured data object, displays the form with the content. An event queue is created and a connection to the server hub is established when real-time updates are enabled. In response to receiving an update event in the event queue, a notification of the update event is displayed when the update event matches the record ID/form that a first user has opened.
Description
- This application claims priority and benefit under 35 U.S.C. § 120 as a continuation of U.S. Ser. No. 16/832,931, filed Mar. 27, 2020, the contents of which are hereby incorporated by reference herein in entirety.
- The present disclosure relates generally to an improved computer system and, in particular, to a method and apparatus for accessing information in a computer system. Still more particularly, the present disclosure relates to a method, a system, and a computer program product for communicating real-time updates among web clients.
- Applications are commonly run with a connection to the Internet. The applications may be used for different functions such as e-mail, instant messaging, online retail sales, online auctions, payroll, benefits administration, financial transactions, report generation, and many other functions. These applications include, for example, web applications that run in browsers.
- A web application is a server/client application in which the client runs on a web browser. Web applications are popular because of the widespread use of web browsers. The web browsers provide access to a server on the World Wide Web, which is also referred to just as the Web.
- The web application can be used to perform a variety of activities. For example, users employ the Internet to read articles, watch news reports, listen to music, send messages, perform research, play online games, perform banking transactions, purchase products and services, pay bills, talk to other people using voice communications, and perform other activities over the Internet.
- With the vast number of users that can access different web applications, maintaining and providing access to accurate and up-to-date data records may be harder than desired. For example, when data records are edited by a first user, that information may not be easily accessible to a second user that is concurrently accessing the data records.
- Therefore, it would be desirable to have a method and apparatus that take into account at least some of the issues discussed above, as well as other possible issues. For example, it would be desirable to have a method and apparatus that overcome a technical problem with viewing up-to-date data records that are simultaneously accessed by multiple users in a Web services environment.
- An embodiment of the present disclosure provides a method for communicating real-time updates among web clients. In response to requesting access to a data within a human resources database, a computer system receives a structured data object composed from a set of data nodes according to a domain specific language. The structured data object defines what a web page looks like without content for the web page. The computer system interprets the structured data object within a record ID context to identify content for the web page. In response to interpreting the structured data object, the computer system displays the form with the content. The computer system interprets the structured data object to determine whether real-time updates are enabled for the web page. In response to determining that real-time updates are enabled for the web page, the computer system creates an event queue and establishes a web socket connection to the server hub. In response to receiving an update event in the event queue, the computer system, determines whether the update event matches the record ID/form that the user has opened. In response to determining that the update event matches the record ID/form, the computer system displays a notification of the update event.
- Yet another embodiment of the present disclosure provides a computer system. The computer system comprises a hardware processor. In response to requesting access to a data within a human resources database, a computer system receives a structured data object composed from a set of data nodes according to a domain specific language. The structured data object defines what a web page looks like without content for the web page. The computer system interprets the structured data object within a record ID context to identify content for the web page. In response to interpreting the structured data object, the computer system displays the form with the content. The computer system interprets the structured data object to determine whether real-time updates are enabled for the web page. In response to determining that real-time updates are enabled for the web page, the computer system creates an event queue and establishes a web socket connection to the server hub. In response to receiving an update event in the event queue, the computer system, determines whether the update event matches the record ID/form that the user has opened. In response to determining that the update event matches the record ID/form, the computer system displays a notification of the update event.
- Yet another embodiment of the present disclosure provides a computer program product for communicating real-time updates among web clients. The computer program product comprises a non-transitory computer readable storage media and program code, stored on the computer readable storage media. The program code includes code for receiving a structured data object composed from a set of data nodes according to a domain specific language, in response to requesting access to a data within a human resources database. The structured data object defines what a web page looks like without content for the web page. The program code includes code for interpreting the structured data object within a record ID context to identify content for the web page. The program code includes code for displaying the form with the content, response to interpreting the structured data object. The program code includes code for interpreting the structured data object to determine whether real-time updates are enabled for the web page. The program code includes code for creating an event queue and establishing a web socket connection to the server hub, in response to determining that real-time updates are enabled for the web page. The program code includes code for determining whether the update event matches the record ID/form that the user has opened, in response to receiving an update event in the event queue. The program code includes code for displaying a notification of the update event, in response to determining that the update event matches the record ID/form.
- The features and functions can be achieved independently in various embodiments of the present disclosure, or may be combined in yet other embodiments in which further details can be seen with reference to the following description and drawings.
- The novel features believed characteristic of the illustrative embodiments are set forth in the appended claims. The illustrative embodiments, however, as well as a preferred mode of use, further objectives and features thereof, will best be understood by reference to the following detailed description of an illustrative embodiment of the present disclosure when read in conjunction with the accompanying drawings, wherein:
-
FIG. 1 is a diagram of a data processing environment in accordance with an illustrative embodiment; -
FIG. 2 is a block diagram of an application development system for a domain-specific language entirely composed of structured data objects in accordance with an illustrative embodiment; -
FIG. 3 is a block diagram of a structured data object in accordance with an illustrative embodiment; -
FIG. 4 is a block diagram of an example of an operation of a user interface engine in accordance with an illustrative embodiment; -
FIG. 5 is an illustration of a block diagram of a real-time data update environment in accordance with an illustrative embodiment; -
FIG. 6 is a flowchart of a process for composing a metadata object in accordance with an illustrative embodiment; -
FIG. 7 is a flowchart of a process for displaying a real-time update enabled web page in accordance with an illustrative embodiment; -
FIG. 8 is a flowchart of a process for displaying a real-time update enabled web form in accordance with an illustrative embodiment; -
FIG. 9 is a flowchart of a process for publishing a real-time update to a real-time update enabled web form in accordance with an illustrative embodiment; -
FIG. 10 is a flowchart of a process for displaying a real-time updates in a real-time update enabled web form in accordance with an illustrative embodiment; -
FIGS. 11A-11B are a graphical user interface for composing structured data objects in accordance with an illustrative embodiment; -
FIG. 12 is a first screen of a first graphical user interface of a first client device showing a first example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 13 is a first screen of a second graphical user interface of a second client device showing the first example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 14 is a second screen of the first graphical user interface of the first client device showing the first example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 15 is a second screen of the second graphical user interface of the second client device showing the first example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 16 is a first screen of a first graphical user interface of a first client device showing a second example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 17 is a first screen of a second graphical user interface of a second client device showing the second example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 18 is a second screen of the first graphical user interface of the first client device showing the second example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 19 is a second screen of the second graphical user interface of the second client device showing the second example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 20 is a first screen of a first graphical user interface of a first client device showing a third example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 21 is a first screen of a second graphical user interface of a second client device showing the third example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 22 is a second screen of the first graphical user interface of the first client device showing the third example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 23 is a second screen of the second graphical user interface of the second client device showing the third example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 24 is a first screen of a first graphical user interface of a first client device showing a fourth example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 25 is a first screen of a second graphical user interface of a second client device showing the fourth example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 26 is a second screen of the first graphical user interface of the first client device showing the fourth example of propagating real-time updates between client devices in accordance with an illustrative embodiment; -
FIG. 27 is a second screen of the second graphical user interface of the second client device showing the fourth example of propagating real-time updates between client devices in accordance with an illustrative embodiment; and -
FIG. 28 is a block diagram of a data processing system in accordance with an illustrative embodiment. - The illustrative embodiments provide a method, an apparatus, and a computer program product for communicating real-time updates among web clients. In one illustrative example, in response to requesting access to a data within a human resources database, a computer system receives a structured data object composed from a set of data nodes according to a domain specific language. The structured data object defines what a web page looks like without content for the web page. The computer system interprets the structured data object within a record ID context to identify content for the web page. In response to interpreting the structured data object, the computer system displays the form with the content. The computer system interprets the structured data object to determine whether real-time updates are enabled for the web page. In response to determining that real-time updates are enabled for the web page, the computer system creates an event queue and establishes a web socket connection to the server hub. In response to receiving an update event in the event queue, the computer system, determines whether the update event matches the record ID/form that the user has opened. In response to determining that the update event matches the record ID/form, the computer system displays a notification of the update event.
- The computer-readable program instructions may also be loaded onto a computer, a programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, a programmable apparatus, or other device to produce a computer implemented process, such that the instructions which execute on the computer, the programmable apparatus, or the other device implement the functions and/or acts specified in the flowchart and/or block diagram block or blocks.
- With reference now to the figures and, in particular, with reference to
FIG. 1 , an illustration of a diagram of a data processing environment is depicted in accordance with an illustrative embodiment. It should be appreciated thatFIG. 1 is only provided as an illustration of one implementation and is not intended to imply any limitation, with regard to the environments in which the different embodiments may be implemented. Many modifications to the depicted environments may be made. -
FIG. 1 depicts a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented. Networkdata processing system 100 is a network of computers in which the illustrative embodiments may be implemented. Networkdata processing system 100 containsnetwork 102, which is a medium used to provide communications links between various devices and computers connected together within networkdata processing system 100.Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables. - In the depicted example,
server computer 104 andserver computer 106 connect to network 102 along withstorage unit 108. In addition, client computers includeclient computer 110,client computer 112, andclient computer 114.Client computer 110,client computer 112, andclient computer 114 connect to network 102. These connections can be wireless or wired connections depending on the implementation.Client computer 110,client computer 112, andclient computer 114 may be, for example, personal computers or network computers. In the depicted example,server computer 104 provides information, such as boot files, operating system images, and applications toclient computer 110,client computer 112, andclient computer 114.Client computer 110,client computer 112, andclient computer 114 are clients toserver computer 104 in this example. Networkdata processing system 100 may include additional server computers, client computers, and other devices not shown. - Program code located in network
data processing system 100 may be stored on a computer-recordable storage medium and downloaded to a data processing system or other device for use. For example, the program code may be stored on a computer-recordable storage medium onserver computer 104 and downloaded toclient computer 110 overnetwork 102 for use onclient computer 110. - In the depicted example, network
data processing system 100 is the Internet withnetwork 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers consisting of thousands of commercial, governmental, educational, and other computer systems that route data and messages. Of course, networkdata processing system 100 also may be implemented as a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN).FIG. 1 is intended as an example, and not as an architectural limitation for the different illustrative embodiments. - The illustration of network
data processing system 100 is not meant to limit the manner in which other illustrative embodiments can be implemented. For example, other client computers may be used in addition to or in place ofclient computer 110,client computer 112, andclient computer 114 as depicted inFIG. 1 . For example,client computer 110,client computer 112, andclient computer 114 may include a tablet computer, a laptop computer, a bus with a vehicle computer, and other suitable types of clients. -
FIG. 2 is a block diagram illustrating an application development system for a domain-specific language entirely composed of structured data objects, in accordance with an illustrative embodiment.Application development system 200 may be used to manipulate composable data nodes to build at least one of business rules, miniapps, and apps.Application development system 200 can be implemented in one or more ofserver computer 104,server computer 106,client computer 110,client computer 112, andclient computer 114 ofFIG. 1 . - As used herein, the phrase “at least one of,” when used with a list of items, means different combinations of one or more of the listed items may be used and only one of each item in the list may be needed. In other words, “at least one of” means any combination of items and number of items may be used from the list, but not all of the items in the list are required. The item may be a particular object, thing, or a category.
- For example, without limitation, “at least one of item A, item B, or item C” may include item A, item A and item B, or item B. This example also may include item A, item B, and item C or item B and item C. Of course, any combinations of these items may be present. In some illustrative examples, “at least one of” may be, for example, without limitation, two of item A; one of item B; and ten of item C; four of item B and seven of item C; or other suitable combinations.
-
User interface engine 202 is computer code and underlying data and structured data object which provide underlying functionality and implementation capability for application designers. Primarily,user interface engine 202 operates client-side, meaning thatuser interface engine 202 operates on a specific client user's computer, such as one or more ofclient computer 110,client computer 112, andclient computer 114 ofFIG. 1 . In one illustrative example,user interface engine 202 could be a Web browser or an extension to a Web browser. -
User interface engine 202 may be metadata driven. The metadata may describe a page and page layout of an overall web page without content.User interface engine 202 loads metadata for the page and then run queries against local or remote databases to get customer data used for constructing applications.User interface engine 202 may then perform interpretation of the metadata and retrieved data, presenting an interface customized for each user. - The metadata may take the form of a document object model (DOM) tree composed of JSON (JavaScript Object Notation) objects, though metadata may be composed of multiple data models. The document object model tree is a tree representation of an abstract syntactic structure of source code, independent of any particular representation or encoding. Each node of the tree denotes a construct occurring in the source code. As opposed to parse trees, typically built by a parser during a source code translation and compiling process, the document object model tree can be “abstract,” in that it is independent of any particular representation or encoding, and does not represent every detail appearing in the real syntax.
- Underlying the user interface,
user interface engine 202 may include one or more modules. As depicted,user interface engine 202 includestile renderer module 204,binding module 206, and business rule andworkflow module 208. Each module may be considered a collection of software or computer code which implements the functionality of the module. -
Tile renderer module 204 is computer code whichcomputer 210 may use to render tiles on tangibleuser display device 212.Tile renderer module 204 may receive input from the user, from bindingmodule 206, and from business rule andworkflow module 208 to change and manipulate both the functionality ofcomputer 210, which is used to executetile renderer module 204, as well as tangibleuser display device 212, which is used to display rendered tiles. - Binding
module 206 is computer code whichcomputer 210 may use to bind data and structured data objects to the user interface, possibly a browser, so thatuser interface engine 202 may keep track of all of the data and structured data objects used in executing business rules and workflows, as well as rendering tiles. Additional details regarding the functionality ofbinding module 206 is described below with respect to how data and structured data objects are used inuser interface engine 202. - Business rule and
workflow module 208 is computer code whichcomputer 210 may use to create, join, merge, or otherwise manipulate composable data nodes in order to create miniapps, collections, and bundles. - Business rule and
workflow module 208, using data and structured data objects tracked by bindingmodule 206, is the underlying code which allows a user to manipulate tiles rendered bytile renderer module 204 and thereby create miniapps, collections, and bundles without the user having to code any of the software being developed. Business rule andworkflow module 208 may use composable data nodes, together with work flows and business rules to create the miniapps, collections, or bundles in a user-perceived codeless development environment. - Structured data object
interpreter 214 is hardware or software which is used to interpret or execute business rules in a business system.Interpreter 214 can be software residing in a Web browser oncomputer 210. However, the illustrative embodiments are not necessarily limited to only client computers or Web browsers. -
Interpreter 214 is a code interpreter designed for a domain-specific language entirely composed of structured data objects. In one illustrative example,interpreter 214 takes the form of an abstract syntax tree (AST) interpreter with the exception that the abstract syntax tree (AST) structure is composed of well-defined data nodes constructs, joined together in a domain-specific language. Because the data node constructs are well-defined when they are constructed,interpreter 214 executes the composition of structured data objects without compilation. Data note constructs are composed into well-defined structured data objects according to selected block types and properties, replacing the tokenization and parsing that would otherwise occur during compilation. - In some illustrative embodiments,
user interface engine 202 may take advantage of some server side services operating on one or more server computers, such asserver computer 216. “Server side” means thatcomputer 210 communicates withserver computer 216, possibly over a network such as the Internet. Server side resources are provided to supportuser interface engine 202. While not always necessary for implementation ofuser interface engine 202, server side resources can enhance the functionality ofuser interface engine 202. - For example, the server side resources may include user
interface engine orchestrator 218. In some exemplary illustrative embodiments,user interface orchestrator 218 may be considered part ofuser interface engine 202 such thatuser interface engine 202 operates partially both oncomputer 210, but also on one or more server computers, such asserver computer 216. -
User interface orchestrator 218 may serve as a proxy to speed up processing ofuser interface engine 202.User interface orchestrator 218 may retrieve structured data objects and then identify whether data queries are for customer data, business rules, or any other structured data objects.User interface orchestrator 218 may then request such data, objects, or code, from the data center operating server side.User interface orchestrator 218 may cache retrieved data, structured data objects, code, workflows, or objects to be sent back touser interface engine 202. - Server side services may include other components other than
user interface orchestrator 218. For example, server side resources could include one or more data object andDNA engines 220, which can be used to manage or provide structured data objects for use inuser interface engine 202. Server side resources may also include one ormore persistence engines 222, which can be used to save work done usinguser interface engine 202. Server side resources may also includebusiness rule engine 224, which may be used to create or store business rules that are used byuser interface engine 202 in the user-perceived codeless building of miniapps, collections, and bundles. - Server side resources may also include
workflow engine 226, which may be used to create or store workflows that are used byuser interface engine 202 in the user-perceived codeless building of miniapps, collections, and bundles. - Server side resources may also include user
interface test engine 228, which may be used to test both the functionality ofuser interface engine 202, possibly as well as the miniapps, collections, and bundles created usinguser interface engine 202. - With reference next to
FIG. 3 , an illustration of a block diagram of a structured data object is depicted in accordance with an illustrative embodiment. Structured data object 300 is an example of a composition of well-defined data nodes that can be linked together according to a domain specific language to create miniapps, collections, or bundles in a user-perceived codeless development environment, such asapplication development system 200 ofFIG. 2 . - Structured data object 300 includes
data nodes Data nodes data binding module 206 ofFIG. 2 to create desired business rules.Tile renderer module 204 ofuser interface engine 202 may visuallypresent data nodes application development system 200 ofFIG. 2 . Each ofdata nodes interpreter 214 ofFIG. 2 for implementing the corresponding business rule. The different permutations of the compositions of these functions, as well as differentiated input, enable the execution of the different business rule behaviors at runtime. - The functions of
data nodes data nodes - For example, structured data object 300 further includes
data node 316.Data node 316 provides additional context for execution ofrelated data node 312. Specifically,data node 316 may indicate thatdata node 312, as well as child data nodes thereof, should be interpreted within the context ofdata node 316. - Structured data object 300 further includes
data node 318.Data node 318 provides additional context for execution of both relateddata node 312 anddata node 316. For example,data node 318 may indicate that information required for execution ofdata node 312 should be requested and received from one or more web services.Data node 318 requests and returns the same context updated with the information received through the web services. - Structured data object 300 further includes
data node 320.Data node 320 provides additional context for execution ofrelated data node 314. Specifically,data node 320 may indicate a consuming service for receipt of business rule output provided byrelated data node 314.Data node 320 requests and returns information to a consuming service, such as a web page. -
FIG. 4 is an illustration of a block diagram of an example of an operation ofuser interface engine 202 shown inFIG. 2 , in accordance with an illustrative embodiment. The example shown inFIG. 4 does not necessarily limit operation ofuser interface engine 202 as shown inFIG. 2 . Nevertheless,FIG. 4 may be read in conjunction withFIG. 2 . - In an illustrative embodiment,
tile renderer module 204 inFIG. 2 may be used to generategraphical user interface 400.Graphical user interface 400 may take the form of tiles shown in a Web browser. Each tile may represent a building block. Alternatively, a tile may represent a miniapp, a collection, or even a bundle. Users may interact withgraphical user interface 400, triggering, for example, a “view actions” command 402. - These actions are sent to
dispatcher 404, which may be part ofuser interface engine 202, shown inFIG. 2 .Dispatcher 404 may send the actions to the business rule and workflow module via subscriptions registered withdispatcher 404.Dispatcher 404 may also sendserver actions 406 sent by data center 408 to business rule andworkflow module 208 inFIG. 2 for use in combination with the actions started by the user. - Business rule and
workflow module 208 may run queries and apply business rules and other logic. Business rule andworkflow module 208 may providenavigation 410, data binding 412, and execution by business rules andworkflows executor 414. - Data and
metadata binding module 206 may apply changes to user interface state 416 held in memory. User interface state 416 may be held in a treestructure containing data 418,metadata 420, and tile state. In turn,tile renderer module 204 inFIG. 2 may rendergraphical user interface 400.Tile renderer module 204 may listen to state changes in the tree structure and efficiently updateonly data 418 andmetadata 420 that need re-rendering. - With reference next to
FIG. 5 , an illustration of a block diagram of a real-time data update environment is depicted in accordance with an illustrative embodiment. In this illustrative example, real-time data update environment 500 includesdevelopment system 502.Application development system 502 is an example of a user-perceived codeless development system, such asapplication development system 200 ofFIG. 2 , in whichdevelopers 504 manipulate structured data objects to build at least one of business rules, miniapps, and apps according to a domain-specific language. - Using
admin console 506 ofdevelopment system 502,developers 504 can create and configure theforms 508 for which real-time updates can be implemented.Admin console 506 is an example ofcomputer 210 ofFIG. 2 , providing client-side services fordevelopment system 502.Forms 508 is an example offorms 422 ofFIG. 4 .Forms 508 can be forms that require data to be edited and viewed by multiple users, such as user A 510, anduser B 512. -
Forms 508 may be defined by one or more structured data objects 514. Structured data objects 514 are examples of structured data object 300 ofFIG. 3 . In this illustrative example, structured data objects 514 are configured for real-time data updates. In an illustrative example, structured data objects 514 define a client server integration pattern that, when implemented informs 508, get real-time live data from theWeb server 516 without having to refresh the display ofform 508 byWeb application 518. Structured data objects 514 may be stored indatabase 520. - In one illustrative example, User A 510 logs into the
web application 518 and opens aform 508. In response,Web server 516 identifies the structured data objects 514 corresponding to form 508, and sends the structured data objects 514 toclient 522 of user A 510. In this illustrative example,client 522 is implemented as software in the form of a web browser. -
Web application 518 interprets structured data objects 514 and, based on an indication themetadata object 514, determines whether real-time update is enabled for theform 508. if real-time updates are enabled,web application 518 creates anevent queue 524, and establishes a connection to the real-time Web component 526 ofWeb server 516.Form 508 is now ready to receive real-time updates fromWeb server 516. - In one illustrative example,
Web application 518 connects to real-time Web component 526 via a SignalR Hub API that allows server code to send asynchronous notifications to client-side web applications. SignalR is a software library for Microsoft ASP.NET. - Real-
time Web component 526 takes advantage of several transports, automatically selecting the best available transport given the client's and server's best available transport. When available, the connection betweenWeb application 518 and real-time component 526 can be a websocket connection that enables bi-directional communication between the browser and server. When an upgraded connection is unavailable, real-time Web component 526 falls back to other connection techniques and technologies, such as HTTP. - Whenever data is entered and saved in a
metadata form 508, savedata pipeline 528 is called. Savedata pipeline 528 may be implemented in any appropriate manner. For example, savedata pipeline 528 may be implemented as a stream processing platform using Apache Kafka open-source stream processing software platform or any other appropriate stream processing platform. Savedata pipeline 528 may be implemented as part of, or separate from, a document storage system, in whole or in part. - Save
data pipeline 528 knows the status ofform 508. Savedata pipeline 528 comparesform 508 with its previous state and produces a delta object that depicts any changes made by the user. savedata pipeline 528 creates a JSON syntax from the Delta object and pushes the JSON to real-time queue 530. real-time queue 530 holds the JSON until it is consumed by real-time service 532. - In this example, real-
time service 532 may be referred to as a subscribing application. In this example, real-time service 532 is configured to perform corresponding actions in response to the storage of individual documents and forms, as identified from event message is generated by savedata pipeline 528. Therefore, in this example, real-time service 532 will receive the JSON from real-time queue 530. real-time service 532 may then perform corresponding actions based on the information contained in the JSON. - Real-
time service 532 may convert the JSON into an appropriate form for delivery to and use byclient 522. For example, in one illustrative example, real-time service 532 creates a real-time message by compressing the JSON data to a record ID, data source, changed values and removes unmodified data. The compressed JSON is then passed to real-time Web component 526. - Real-
time Web component 526 then checks for connected clients, such as one or more ofclient 522, and security real-time Web component 526 then publishes the real-time message to the clients that are connected. - A message or signal generated by real-
time Web component 526 may be delivered toclient 522 via an appropriate network connection. The connection may be, for example, without limitation, a wired connection, a wireless connection, a fiber optic connection, or any other appropriate connection or combination of connections for delivering a signal or message from real-time web component 526 toclient 522. - In one illustrative example, the real-time message is a packet that contains the name and parameters of the to-be-called method is sent across the active transport. In one illustrative example, when an object is sent as a method parameter, it is serialized using JSON. The client then matches the method name to methods defined in client-side code. For example, if the update matches the record ID/form that the user has opened, the message is considered useful and the event is added into the queue. However, if the update does not match the record ID/form, the updates are discarded.
-
Web application 518 uses the deserialized parameter data when interpreting the data nodes ofmetadata object 514. For example, the change values received in real-time message can be interpreted byWeb application 518 to override the default values previously retrieved fromdatabase 520. - User A 510 gets the notifications in real-time to see these changes updated by
user B 512. In one illustrative example, user A 510 is then shown/prompted with messages regarding changes made byuser B 512. For example, user A may be prompted whenuser B 512 adds a new record toIHCM database 520, whenuser B 512 has opened a form for editing a record that is being viewed by User A 510, or whenuser B 512 has updated a record that is being viewed by user A 510. In one or more illustrative examples, user A 510 may be prompted to update the records displayed, discard changes made byuser B 512, or merge the display record changes made byuser B 512. - With reference next to
FIG. 6 , a flowchart of a process for composing a metadata object is depicted according to an illustrative example. The process ofFIG. 6 may be implemented as operations performed byapplication development system 200, shown in block form inFIG. 2 . - Using an application development system, developers, such as
developers 504, compose metadata object (step 610). The metadata object can be structured data object 300, shown in block form inFIG. 3 . - Using an application development system, developers, such as
developers 504, configure object properties for real-time data updates (step 620), with the process terminating thereafter. The metadata object can then be saved in a database, such as I HCMdatabase 520 ofFIG. 5 , for consumption by a Web application, such asweb application 518 ofFIG. 5 . - With reference next to
FIG. 7 , a flowchart of a process for communicating real-time updates among web clients is depicted according to an illustrative example. The process ofFIG. 7 may be implemented as operations performed byweb application 518, shown in block form inFIG. 5 . - The process begins by receiving a structured data object composed from a set of data nodes according to a domain specific language (step 710). The structured data object can be received in response to a request for access to data within a human resources database. The structured data object defines what a web page looks like without content for the web page.
- The process interprets the structured data object within a context of a record ID/form (step 720). Interpreting the structured data object identifies content for the web page. Additionally, Interpreting the structured data object identifies whether real-time updates are enabled for the web page.
- The process displays the webpage with the content (step 730). If real-time updates are enabled the webpage, the process creates an event queue and establishes a connection to the server hub (step 740).
- When an update event is received in the event queue, the process determines whether the update event matches the record ID/form that a first user has opened (step 750). The process displays displaying a notification of the update event when the update event matches the record ID/form (step 760), and terminates thereafter.
- With reference next to
FIG. 8 , a flowchart of a process for displaying a real-time update enabled web form is depicted according to an illustrative example. The process is a specific example of steps 710-730 of the process ofFIG. 7 . - The process begins by sending a request to access a web form (step 810). The web form can be a
web form 508, shown in block form inFIG. 5 . - The process receives a structured metadata object (step 820). The structured metadata object is sent from a Web server, such as
Web server 516, in response to receiving the request. The structured metadata object is an example of structuredmetadata object 300, shown in block form inFIG. 3 . - The process then interprets the structured metadata object (step 830). Interpretation can be performed using structured
metadata object interpreter 214 ofFIG. 2 . The metadata object can be interpreted to identify content for the requested form, as well as to determine whether real-time updates are enabled for the form (step 840). - If real-time updates are not enabled (“no” at step 740), the process displays the web form (step 850), with the process terminating thereafter. The web form is displayed, using data identified from the interpretation of the structured data object.
- If real-time updates are enabled (“yes” at step 740), the process creates an event queue (step 860). The event queue is an example of an event queue, 524 shown in block form in
FIG. 5 . The process then establishes a connection to the Web server (step 870). In one illustrative example, the connection can be a web socket connection, enabling bi-directional communication between the client browser and Web server. If the upgraded connection is unavailable, the connection falls back to other connection techniques and technologies, such as HTTP. The Web server registers the connection using a Hub API that allows server code to send asynchronous notifications to client-side web applications. - The process displays the web form (step 850), with the process terminating thereafter. The web form is displayed, using data identified from the interpretation of the structured data object.
- With reference next to
FIG. 9 , a flowchart of a process for publishing a real-time update to a real-time update enabled web form is depicted according to an illustrative example. The process may be implemented as operations performed byWeb server 516, shown in block form inFIG. 5 . - The process begins by receiving record update (step 910). The record update can be, for example, data that is entered and saved in a metadata form, such as
metadata form 508 ofFIG. 5 . The record update can be, for example, the creation of a new record. - The process compares the record update to a prior state of the record, and calculates the Delta (step 920). a delta object that depicts any changes to the record made by the user received in
step 910. - If the Delta object is not nil (“no” At step 930), the process creates a JSON syntax from the Delta object (step 940) and pushes the JSON to real-time queue (step 950), where the JSON is held until it is consumed by a real-time service, such as real-
time service 532 ofFIG. 5 . - The process compresses the JSON data (step 960). For example, the process can compress the JSON data to a record ID, data source, changed values and removes unmodified data.
- The process checks for connected clients, such as one or more of
client 522, and publishes the real-time message to the clients that are connected (step 970), with the process terminating thereafter. - With reference next to
FIG. 10 , a flowchart of a process for displaying a real-time update in a real-time update enabled web form is depicted according to an illustrative example. The process inFIG. 10 is a specific example of steps 750-760 of process 700 ofFIG. 7 . - The process begins by receiving a real-time update from the Web server (step 1010). In one illustrative example, the real-time update is received via a web socket connection, enabling bi-directional communication between the client browser and Web server. In another illustrative example, he update is received via other connection techniques and technologies, such as an HTTP POST.
- The process then compares the record ID contained in the real-time update to record ID's of open forms (step 1020), which can be recorded in the client event queue, such as
event queue 524 ofFIG. 5 . If the record updates do not match (“no” at step 1020), the update is considered unimportant, and is discarded (step 1030). The process terminates thereafter. - If the record updates do match (“yes” at step 1020), the process adds the real-time update to the engine two (step 1040). The process then prompts the user regarding the real-time update (step 1050), and updates the web form and data per any user response (step 1060). The process terminates thereafter.
- With reference next to
FIGS. 11A-11B , a graphical user interface for composing structured data objects is shown in accordance with an illustrative example. Graphical user interface 1100 provides an interface to manipulate composable data nodes to build at least one of business rules, miniapps, and apps, in anapplication development system 200, such asapplication development system 200 ofFIG. 2 . - In this illustrative example, graphical user interface 1100 includes
properties section 1110, in which system developers, such asdevelopers 504, can configure object properties for the compose data object.Property section 1110 and includesproperty 1120. system developers can configure property, 1120 to enable real-time data updates for the composed data object. - Referring generally to
FIGS. 12-15 , a first example of graphical user interfaces for different client devices illustrating real-time updates propagated between the client devices is depicted according to an illustrative embodiment. - With reference specifically to
FIG. 12 ,graphical user interface 1200 is depicted according to an illustrative example.Graphical user interface 1200 can be displayed on a first client device, such as a first one ofclient 522 ofFIG. 5 . In this illustrative example,graphical user interface 1200 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such as user 510 ofFIG. 5 , usesgraphical user interface 1200 to create a new record. In this illustrative example, the record is a new record for a job posting within an organization. - With reference specifically to
FIG. 13 ,graphical user interface 1300 is depicted according to an illustrative example.Graphical user interface 1300 can be displayed on a second client device, such as a second one ofclient 522 ofFIG. 5 . In this illustrative example,graphical user interface 1300 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such asuser 512 ofFIG. 5 , usesgraphical user interface 1300 to view existing records. In this illustrative example, the existing records are for job postings within an organization. - Referring now to
FIG. 14 , when the user has finished editing relevant information for a new record, the user saves the record, such as by interacting withcontrol element 1410. The new record has been submitted to a save data pipeline of the corresponding Web server, such as savedata pipeline 528 ofFIG. 5 . - With reference next to
FIG. 15 ,graphical user interface 1300 is updated automatically upon receipt of the new record.Graphical user interface 1300 displaysnew record 1510, without refreshing, reloading, or otherwise re-retrieving relevant content for the displayed webpage. Additionally,graphical user interface 1300 and display notification 1520, alerting the user regarding thenew record 1510. - Referring generally to
FIGS. 16-19 , a second example of graphical user interfaces for different client devices illustrating real-time updates propagated between the client devices is depicted according to an illustrative embodiment. - With reference specifically to
FIG. 16 ,graphical user interface 1600 is depicted according to an illustrative example.Graphical user interface 1600 can be displayed on a first client device, such as a first one ofclient 522 ofFIG. 5 . In this illustrative example, graphical user interface 500 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such as user 510 ofFIG. 5 , usesgraphical user interface 1600 to create a new record. In this illustrative example, the record is a new record for a job candidate. - With reference specifically to
FIG. 17 ,graphical user interface 1700 is depicted according to an illustrative example.Graphical user interface 1700 can be displayed on a second client device, such as a second one ofclient 522 ofFIG. 5 . In this illustrative example,graphical user interface 1700 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such asuser 512 ofFIG. 5 , usesgraphical user interface 1700 to view existing records. In this illustrative example, the existing records are for job candidates. - Referring now to
FIG. 18 , when the user has finished editing relevant information for a new record, the user saves the record, such as by interacting withcontrol element 1810. The new record has been submitted to a save data pipeline of the corresponding Web server, such as savedata pipeline 528 ofFIG. 5 . - With reference next to
FIG. 19 ,graphical user interface 1700 is updated automatically upon receipt of the new record.Graphical user interface 1700 displaysnew record 1910, without refreshing, reloading, or otherwise re-retrieving relevant content for the displayed webpage. Additionally,graphical user interface 1700displays notification 1930, alerting the user regarding thenew record 1910, as well as updating other relevant content of the webpage. - Referring generally to
FIGS. 20-23 , a third example of graphical user interfaces for different client devices illustrating real-time updates propagated between the client devices is depicted according to an illustrative embodiment. - With reference specifically to
FIG. 20 ,graphical user interface 2000 is depicted according to an illustrative example.Graphical user interface 2000 can be displayed on a first client device, such as a first one ofclient 522 ofFIG. 5 . In this illustrative example, graphical user interface 500 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such as user 510 ofFIG. 5 , usesgraphical user interface 2000 to edit an existing record. In this illustrative example, the record is an existing record for a job candidate. - With reference specifically to
FIG. 21 ,graphical user interface 2100 is depicted according to an illustrative example.Graphical user interface 2100 can be displayed on a second client device, such as a second one ofclient 522 ofFIG. 5 . In this illustrative example,graphical user interface 2100 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such asuser 512 ofFIG. 5 , usesgraphical user interface 2100 to view an existing record. In this illustrative example, the existing records is for a job candidate. - Referring now to
FIG. 22 , when the user has finished editing relevant information for the existing record, the user saves the record, such as by interacting withcontrol element 2210. The new record has been submitted to a save data pipeline of the corresponding Web server, such as savedata pipeline 528 ofFIG. 5 . - With reference next to
FIG. 23 ,graphical user interface 2100 is updated automatically upon receipt of the new record.Graphical user interface 2100 displays the editedinformation 2310 of the existing record, without refreshing, reloading, or otherwise re-retrieving relevant content for the displayed webpage. Additionally,graphical user interface 2100displays notification 2330, alerting the user regarding the editedinformation 2310, as well as updating other relevant content of the webpage. - Referring generally to
FIGS. 24-27 , a fourth example of graphical user interfaces for different client devices illustrating real-time updates propagated between the client devices is depicted according to an illustrative embodiment. - With reference specifically to
FIG. 24 ,graphical user interface 2400 is depicted according to an illustrative example.Graphical user interface 2400 can be displayed on a first client device, such as a first one ofclient 522 ofFIG. 5 . In this illustrative example,graphical user interface 2400 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such as user 510 ofFIG. 5 , usesgraphical user interface 2400 to edit an existing record. In this illustrative example, the record is an existing record for a job candidate. - With reference specifically to
FIG. 25 ,graphical user interface 2500 is depicted according to an illustrative example.Graphical user interface 2500 can be displayed on a second client device, such as a second one ofclient 522 ofFIG. 5 . In this illustrative example,graphical user interface 2500 is an interface for a web application, such asweb application 518 ofFIG. 5 . In this illustrative example, a user, such asuser 512 ofFIG. 5 , usesgraphical user interface 2500 to edit an existing record. In this illustrative example, the record is an existing record for a job candidate. - Referring now to
FIG. 26 , when the user has finished editing relevant information for the existing record, the user saves the record, such as by interacting withcontrol element 2410. The new record has been submitted to a save data pipeline of the corresponding Web server, such as savedata pipeline 528 ofFIG. 5 . - With reference next to
FIG. 27 ,graphical user interface 2500 displays notification 2710, alerting the user that information displayed ingraphical user interface 2500 has been edited by another user. Upon refresh,graphical user interface 2500 displays the record, including information that was edited usinggraphical user interface 2400. - Turning now to
FIG. 28 , an illustration of a block diagram of a data processing system is depicted in accordance with an illustrative embodiment.Data processing system 2800 may be used to implement one or more of the computers of Networkdata processing system 100 inFIG. 1 ,computer 210 andserver computer 216 ofFIG. 2 , as well as other data processing systems that may be used in real-time data update environment 500 ofFIG. 5 . - In this illustrative example,
data processing system 2800 includescommunications framework 2802, which provides communications betweenprocessor unit 2804,memory 2806,persistent storage 2808,communications unit 2810, input/output (I/O)unit 2812, anddisplay 2814. In this example,communications framework 2802 may take the form of a bus system. -
Processor unit 2804 serves to execute instructions for software that may be loaded intomemory 2806.Processor unit 2804 may be a number of processors, a multi-processor core, or some other type of processor, depending on the particular implementation. -
Memory 2806 andpersistent storage 2808 are examples ofstorage devices 2816. A storage device is any piece of hardware that is capable of storing information, such as, for example, without limitation, at least one of data, program code in functional form, or other suitable information either on a temporary basis, a permanent basis, or both on a temporary basis and a permanent basis.Storage devices 2816 may also be referred to as computer readable storage devices in these illustrative examples.Memory 2806, in these examples, may be, for example, a random access memory or any other suitable volatile or non-volatile storage device.Persistent storage 2808 may take various forms, depending on the particular implementation. - For example,
persistent storage 2808 may contain one or more components or devices. For example,persistent storage 2808 may be a hard drive, a solid state hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used bypersistent storage 2808 also may be removable. For example, a removable hard drive may be used forpersistent storage 2808. -
Communications unit 2810, in these illustrative examples, provides for communications with other data processing systems or devices. In these illustrative examples,communications unit 2810 is a network interface card. - Input/
output unit 2812 allows for input and output of data with other devices that may be connected todata processing system 2800. For example, input/output unit 2812 may provide a connection for user input through at least one of a keyboard, a mouse, or some other suitable input device. Further, input/output unit 2812 may send output to a printer.Display 2814 provides a mechanism to display information to a user. - Instructions for at least one of the operating system, applications, or programs may be located in
storage devices 2816, which are in communication withprocessor unit 2804 throughcommunications framework 2802. The processes of the different embodiments may be performed byprocessor unit 2804 using computer-implemented instructions, which may be located in a memory, such asmemory 2806. - These instructions are referred to as program code, computer usable program code, or computer readable program code that may be read and executed by a processor in
processor unit 2804. The program code in the different embodiments may be embodied on different physical or computer readable storage media, such asmemory 2806 orpersistent storage 2808. -
Program code 2818 is located in a functional form on computerreadable media 2820 that is selectively removable and may be loaded onto or transferred todata processing system 2800 for execution byprocessor unit 2804.Program code 2818 and computerreadable media 2820 formcomputer program product 2822 in these illustrative examples. In one example, computerreadable media 2820 may be computerreadable storage media 2824 or computerreadable signal media 2826. - In these illustrative examples, computer
readable storage media 2824 is a physical or tangible storage device used to storeprogram code 2818 rather than a medium that propagates or transmitsprogram code 2818. - Alternatively,
program code 2818 may be transferred todata processing system 2800 using computerreadable signal media 2826. Computerreadable signal media 2826 may be, for example, a propagated data signal containingprogram code 2818. For example, computerreadable signal media 2826 may be at least one of an electromagnetic signal, an optical signal, or any other suitable type of signal. These signals may be transmitted over at least one of communications links, such as wireless communications links, optical fiber cable, coaxial cable, a wire, or any other suitable type of communications link. - The different components illustrated for
data processing system 2800 are not meant to provide architectural limitations to the manner in which different embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system including components in addition to or in place of those illustrated fordata processing system 2800. Other components shown inFIG. 28 can be varied from the illustrative examples shown. The different embodiments may be implemented using any hardware device or system capable of runningprogram code 2818. - The description of the different illustrative embodiments has been presented for purposes of illustration and description and is not intended to be exhaustive or limited to the embodiments in the form disclosed. The different illustrative examples describe components that perform actions or operations. In an illustrative embodiment, a component may be configured to perform the action or operation described. For example, the component may have a configuration or design for a structure that provides the component an ability to perform the action or operation that is described in the illustrative examples as being performed by the component.
- Many modifications and variations will be apparent to those of ordinary skill in the art. Further, different illustrative embodiments may provide different features as compared to other desirable embodiments. The embodiment or embodiments selected are chosen and described in order to best explain the principles of the embodiments, the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (21)
1-21. (canceled)
22. A method for communicating real-time updates among web clients, the method comprising:
receiving, by a computer system responsive to requesting access to a data record stored in a database, a data object comprising a set of data nodes according to a domain specific language, the data object defining a layout for a webpage form;
interpreting, by the computer system, the data object within a context of the data record to identify content for the webpage form;
creating, by the computer system responsive to determining that the data object enables real-time updates for the webpage form, an event queue;
displaying, by the computer system, the webpage form with the identified content; and
displaying, by the computer system responsive to determining that an update event in the event queue matches a record identifier for the data record, a notification and content of the update event.
23. The method of claim 22 , wherein the update event is a notification of changes to the content for the webpage form, the changes to the content for the webpage form including at least one of:
an addition of a second data record;
opening of a second webpage form by a user for editing the data record; or
updating of the data record by user.
24. The method of claim 22 , further comprising:
providing, by the computer system, a prompt to a user for a response to the update event, the prompt including at least one of:
a message to update the content displayed;
a message to discard changes made by a second user; or
a message to merge the content with the changes made by the second user.
25. The method of claim 22 , further comprising:
updating, by the computer system, the content displayed in the webpage form based on information in the update event without refreshing, reloading, or otherwise re-retrieving relevant content for the webpage form.
26. The method of claim 22 , further comprising:
establishing, by the computer system, a connection to a server, the connection providing asynchronous bi-directional communication between a client browser and the server using an Application Program Interface.
27. The method of claim 26 , wherein the connection is a web socket connection.
28. The method of claim 22 , wherein the update event is a compressed JSON syntax of the data record including the record identifier, a data source, and changed values of the data record.
29. A computer system, comprising:
a hardware processor; and
a web browser, in communication with the hardware processor, the web browser configured to:
receive, in response to a request for access to a data record stored in a database, a data object comprising a set of data nodes according to a domain specific language, the data object defining a layout for a webpage form;
interpret the data object within a context of the data record to identify content for the webpage form;
create, responsive to determining that the data object enables real-time updates for the webpage form, an event queue;
display the webpage form with the identified content; and
display, responsive to determining that an update event in the event queue matches a record identifier for the data record, a notification and content of the update event.
30. The computer system of claim 29 , wherein the update event is a notification of changes to the content for the webpage form, the changes to the content for the webpage form including at least one of:
an addition of a second data record;
opening of a second webpage form by a user for editing the data record; or
updating of the data record by user.
31. The computer system of claim 29 , the web browser is further configured to:
provide a prompt to a user for a response to the update event, the prompt including at least one of:
a message to update the content displayed;
a message to discard changes made by a second user; or
a message to merge the content with the changes made by the second user.
32. The computer system of claim 29 , the web browser is further configured to:
update the content displayed in the webpage form based on information in the update event without refreshing, reloading, or otherwise re-retrieving relevant content for the webpage form.
33. The computer system of claim 29 , the web browser is further configured to:
establish a connection to a server, the connection providing asynchronous bi-directional communication between a client browser and the server using an Application Program Interface.
34. The computer system of claim 33 , wherein the connection is a web socket connection.
35. The computer system of claim 29 , wherein the update event is a compressed JSON syntax of the data record including the record identifier, a data source, and changed values of the data record.
36. One or more non-transitory computer readable storage media having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to implement operations comprising:
receiving a data object composed from a set of data nodes according to a domain specific language, the data object defining a layout for a webpage form;
interpreting, using a data record, the data object to identify content for the webpage form;
creating, responsive to determining that the data object enables real-time updates for the webpage form, an event queue;
displaying the webpage form with the content; and
displaying, responsive to determining that an update event in the event queue matches a record identifier for the data record, a notification and content of the update event.
37. The one or more non-transitory computer readable storage media of claim 36 , wherein the update event is a notification of changes to the content for the webpage form, the changes to the content for the webpage form including at least one of:
an addition of a second data record;
opening of a second webpage form by a user for editing the data record; or
updating of the data record by user.
38. The one or more non-transitory computer readable storage media of claim 36 , the operations further comprising:
providing a prompt to a user for a response to the update event, the prompt including at least one of:
a message to update the content displayed;
a message to discard changes made by a second user; or
a message to merge the content with the changes made by the second user.
39. The one or more non-transitory computer readable storage media of claim 36 , the operations further comprising:
updating the content displayed in the webpage form based on information in the update event without refreshing, reloading, or otherwise re-retrieving relevant content for the webpage form.
40. The one or more non-transitory computer readable storage media of claim 36 , the operations further comprising:
establishing a connection to a server, the connection providing asynchronous bi-directional communication between a client browser and the server using an Application Program Interface.
41. The one or more non-transitory computer readable storage media of claim 40 , wherein the connection is a web socket connection.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/123,497 US20230229671A1 (en) | 2020-03-27 | 2023-03-20 | Web services having live data updates |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/832,931 US11609932B2 (en) | 2020-03-27 | 2020-03-27 | Web services having live data updates |
US18/123,497 US20230229671A1 (en) | 2020-03-27 | 2023-03-20 | Web services having live data updates |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/832,931 Continuation US11609932B2 (en) | 2020-03-27 | 2020-03-27 | Web services having live data updates |
Publications (1)
Publication Number | Publication Date |
---|---|
US20230229671A1 true US20230229671A1 (en) | 2023-07-20 |
Family
ID=77854559
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/832,931 Active 2040-10-01 US11609932B2 (en) | 2020-03-27 | 2020-03-27 | Web services having live data updates |
US18/123,497 Pending US20230229671A1 (en) | 2020-03-27 | 2023-03-20 | Web services having live data updates |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/832,931 Active 2040-10-01 US11609932B2 (en) | 2020-03-27 | 2020-03-27 | Web services having live data updates |
Country Status (1)
Country | Link |
---|---|
US (2) | US11609932B2 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220172302A1 (en) * | 2020-12-01 | 2022-06-02 | Adp, Llc | Conversion from schemas to payroll policies |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020165907A1 (en) * | 2001-04-13 | 2002-11-07 | Matthew Dornquast | System and method for real time interactive network communications |
US20070240128A1 (en) * | 2006-04-07 | 2007-10-11 | Patton Richard D | Systems and methods for generating a user interface using a domain specific language |
US20080263179A1 (en) * | 2005-10-28 | 2008-10-23 | Gerard John Buttner | System and method for dynamically updating web pages using messaging-oriented middleware |
US7975019B1 (en) * | 2005-07-15 | 2011-07-05 | Amazon Technologies, Inc. | Dynamic supplementation of rendered web pages with content supplied by a separate source |
US20160162453A1 (en) * | 2001-02-27 | 2016-06-09 | Open Invention Network Llc | Method and apparatus for viewing electronic commerce-related documents |
US20220215606A1 (en) * | 2019-04-15 | 2022-07-07 | Canva Pty Ltd | Systems and methods of generating a design based on a design template and another design |
US11461829B1 (en) * | 2019-06-27 | 2022-10-04 | Amazon Technologies, Inc. | Machine learned system for predicting item package quantity relationship between item descriptions |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002065286A2 (en) * | 2001-02-12 | 2002-08-22 | Lto Limited | Client software enabling a client to run a network based application |
US20060184613A1 (en) | 2005-02-15 | 2006-08-17 | Xata Corporation | Data conduit |
US20100175044A1 (en) * | 2009-01-07 | 2010-07-08 | Infosys Technologies Limited | Method for creating software factory for developing j2ee applications |
EP2383684A1 (en) * | 2010-04-30 | 2011-11-02 | Fujitsu Limited | Method and device for generating an ontology document |
CN102236645B (en) * | 2010-05-06 | 2016-03-30 | 上海五和际软件信息有限公司 | Based on the natural language man-machine conversation device of semantic logic |
US8797920B2 (en) * | 2011-04-20 | 2014-08-05 | IBT—Internet Business Technologies | Methods and systems for access to real-time full-duplex web communications platforms |
US20150172228A1 (en) * | 2012-04-17 | 2015-06-18 | George Zalepa | Method and system for communicating information over a network |
US8612406B1 (en) | 2012-05-22 | 2013-12-17 | Sap Ag | Sharing business data across networked applications |
US20150269130A1 (en) | 2014-03-21 | 2015-09-24 | Ptc Inc. | System and method of using multi-level hierarchical data in displaying real-time web-service objects |
EP4044022A1 (en) * | 2015-07-30 | 2022-08-17 | Wix.com Ltd. | System integrating a mobile device application creation, editing and distribution system with a website design system |
US9959192B1 (en) * | 2015-09-15 | 2018-05-01 | Google Llc | Debugging interface for inserted elements in a resource |
WO2018226621A1 (en) * | 2017-06-05 | 2018-12-13 | Umajin Inc. | Methods and systems for an application system |
CN112955869A (en) * | 2018-11-08 | 2021-06-11 | 英特尔公司 | Function As A Service (FAAS) system enhancements |
US10942709B2 (en) * | 2019-07-02 | 2021-03-09 | Holtworks, LLC | Hyperpiler |
US10853062B1 (en) * | 2019-07-02 | 2020-12-01 | Holtworks, LLC | Hyperpiler |
US11194686B2 (en) * | 2019-10-18 | 2021-12-07 | Adp, Llc | Data agnostic monitoring service |
US11824725B2 (en) * | 2020-03-17 | 2023-11-21 | Rebaca Technologies | State machine emulation using domain-specific language constructs |
-
2020
- 2020-03-27 US US16/832,931 patent/US11609932B2/en active Active
-
2023
- 2023-03-20 US US18/123,497 patent/US20230229671A1/en active Pending
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160162453A1 (en) * | 2001-02-27 | 2016-06-09 | Open Invention Network Llc | Method and apparatus for viewing electronic commerce-related documents |
US20020165907A1 (en) * | 2001-04-13 | 2002-11-07 | Matthew Dornquast | System and method for real time interactive network communications |
US7975019B1 (en) * | 2005-07-15 | 2011-07-05 | Amazon Technologies, Inc. | Dynamic supplementation of rendered web pages with content supplied by a separate source |
US20080263179A1 (en) * | 2005-10-28 | 2008-10-23 | Gerard John Buttner | System and method for dynamically updating web pages using messaging-oriented middleware |
US20070240128A1 (en) * | 2006-04-07 | 2007-10-11 | Patton Richard D | Systems and methods for generating a user interface using a domain specific language |
US20220215606A1 (en) * | 2019-04-15 | 2022-07-07 | Canva Pty Ltd | Systems and methods of generating a design based on a design template and another design |
US11461829B1 (en) * | 2019-06-27 | 2022-10-04 | Amazon Technologies, Inc. | Machine learned system for predicting item package quantity relationship between item descriptions |
Also Published As
Publication number | Publication date |
---|---|
US20210303595A1 (en) | 2021-09-30 |
US11609932B2 (en) | 2023-03-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11102152B2 (en) | System and method of using conversational agent to collect information and trigger actions | |
CN106027330B (en) | A kind of front end system message test method and simulation baffle system | |
US9705946B2 (en) | Method to initiate server based collaboration on e-mail attachments | |
US11936760B2 (en) | Method and system of generating generic protocol handlers | |
US8726285B2 (en) | Method and apparatus for triggering workflow deployment and/or execution | |
US6728762B1 (en) | System and method for browser definition of workflow documents | |
US6731314B1 (en) | Network-based three-dimensional multiple-user shared environment apparatus and method | |
Rezayat | The enterprise-web portal for life-cycle support | |
US6748425B1 (en) | System and method for browser creation and maintenance of forms | |
US6993723B1 (en) | Listing activities in a graphical user interface in a collaborative work tool Architecture | |
CN101097579B (en) | Systems and methods for providing a mockup data generator | |
US6772393B1 (en) | System and method for room decoration and inheritance | |
US8751558B2 (en) | Mashup infrastructure with learning mechanism | |
US20040024820A1 (en) | Method and apparatus for designating endpoints in a collaborative computer system to facilitate maintaining data consistency | |
Ba et al. | Using client-broker-server architecture for Intranet decision support | |
US20100042935A1 (en) | Method and System for Visual Landing Page Optimization Configuration and Implementation | |
AU2008332701A1 (en) | Templating system and method for updating content in real time | |
US20230229671A1 (en) | Web services having live data updates | |
Ahmed | Designing flexible GUI to increase the acceptance rate of product data management systems in industry | |
US10936998B2 (en) | Metadata-based chat wizard | |
US20050193001A1 (en) | Client-side wizard framework | |
US10893012B2 (en) | Context aware metadata-based chat wizard | |
US10719202B2 (en) | System for dynamically rendering a graphical user interface | |
CN103164217A (en) | Standalone data entry for backend system | |
US20220172302A1 (en) | Conversion from schemas to payroll policies |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |