Oracle International Corporation

Nextworld, LLC

David Allen Schneider

Blake T Sullivan

Michael Elges

Axel Allgeier

Venkata Guddanti

Vito Solimene

Deborah Gail Shupe

Tal Broda

Pavitra Subramaniam

Edward Farrell

Max Starets

Michael William McGrath

Dipankar Bajpai

Shailesh Vinayaka

William Bruce Kilgore

Anki R Nelaturu

Xi Li

Gary Adams

Robert Provencal

Gary Van Matre

Scott Michael O'Bryan

Mark Vakoc

Robert Vandette

Steven Bradley Likes

Congxiao Lu

Cheyanne Miller

Joseph Yates

Viviana Shain

Joshua Miers

Asynchronous fallback save operations herein (also referred to herein as a background save) provide a means for saving very large transactions from a client device within a stateless architecture. When dealing with large transactions, it may take a long time to process records—so long that the connection between the server and the client may time out, causing the user to lose all work or progress that was being saved. Thus, the present technology serves to prevent this 'time out' problem while simultaneously allowing users to continue working on something else while a save is still completing. In some implementations, once a user has submitted a save request, the save operation may be carried out in a background thread pool, allowing the user to continue move on to a new task.

Systems and methods for asynchronous fallback save operations

Various embodiments of the present technology generally relate to automated tools for tracking, recording, restoring and auditing transactions. In accordance with various embodiments, applications and servers can provide a variety of features including, but not limited to, behind the scene monitoring activity (transaction or business) and recording, persisting client activity, ubiquitous autosave, business workflow and approval lifecycles, error correction at the business level, management of the state of the transaction without the user having to manage the activity, tracking posted and unposted transactions (e.g., business state), and the like. The applications can communicate with a unified transaction engine that combines awareness of database transaction state along with business transaction states. As a result, the end-user and/or developer do not have to be concerned about the underlying differences between the database transaction state and business transaction states, and can focus on where their transaction is in its lifecycle.

Automated transaction engine

In one set of embodiments, methods, systems, and apparatus are provided that include presenting, by a computer system, a task flow in a popup component of an application user interface executing in a user interface layer, where the task flow executes in an application layer of the computer system, and also include communicating, by the computer system, a first notification from the application layer to the user interface layer in response to normal completion of the task flow, and updating, e.g., closing, the component in the application user interface based upon the first notification. A second notification may be communicated from the user interface layer to the application layer in response to a user interface event that is associated with the popup component and causes an abnormal termination of the task flow. Presenting may include displaying the task flow in a region component in the popup component.

Task flow interface in a popup region

A system performs thread synchronization across layers of code that implement an application, including native code, system code, and code in a virtual machine ('VM'). The system makes a call by the native code to the system code; and sends a message by the system code to the code in the VM. The system then sends a first response by the code in the VM to the system code; and sends a second response by the system code to the native code, where each one of the native code, the system code, and the code in the VM implements wait and notify functionality for communication with other codes that implement the application.

Thread synchronization for platform neutrality

A system for generating a web page that integrates content from different content sources. The system defines a request configured to be transmitted from a consumer application to a producer application. The request is for the producer application to provide content to the consumer application. The system adds additional custom data to the request via a plurality of integration points. The additional custom data is configured to be interpreted by handlers corresponding to the integration points. The system receives content produced by the producer application. The producer application produces the content based upon the request and the additional custom data. The system displays the received content to appear as an integrated whole with other content on a page.

Generating web pages with integrated content

A system that pushes active data to a client receives a first request for a page that includes active data from the client. The active data includes a component and a corresponding model for a data source of the component. The system determines if the model is active and if so, instantiates an encoder that corresponds to the component. The system queries the model for the active data and renders a user interface representation of the data. The system then returns a response to the request with the user interface representation.

Active data push delivery

Growing community of inventors

Aurora, CO, United States of America

David Allen Schneider