Nextworld, LLC

Oracle International Corporation

Vito Solimene

Axel Allgeier

David Allen Schneider

Deborah Gail Shupe

Yu-feng Gu

Anthony H Cheng

Lujiang Liu

Kimberly Jacot

Madhuri Kolhatkar

Robert Provencal

Cheyanne Miller

Joseph Yates

Viviana Shain

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 empower business domain experts to create 'no-code' enterprise applications with a variety of features (e.g., workflow, multi-currency, etc.). By using the tools of various embodiments, the domain expert just has to know the business and not how to code in order to create enterprise applications. In some embodiments, the domain expert can access a tool that allows the domain expert to convey intent and desires instead of providing code. The intent and desire of the domain expert can then be abstracted, translated, and stored as a metadata representation. The metadata representation can then be used to automatically generate appropriate code artifacts for the applications. The code artifacts can include snippets of code written in a variety of languages. These code artifacts can then be wrapped, using a runtime engine for example, to create the application which can be distributed to the end-users.

Systems and method for creating enterprise software

Systems and methods for creating enterprise software

In non-limiting examples of the present disclosure, systems, methods and devices for assisting with provisioning individualized application instances are provided. A request to render an individualized instance of an application may be received. A determination may be made based on the request as to whether a sparse metadata chunk exists for each of a plurality of user interface elements associated with the application. A sparse metadata application artifact may be generated for each user interface element for which a sparse metadata chunk is determined to exist. A base user interface chunk of metadata may be identified for each user interface element for which a sparse metadata chunk is determined not to exist. A base metadata application artifact may be generated for each identified base user interface chunk of metadata, and the individualized instance of the application may be caused to be displayed.

Customized application architecture utilizing sparse and base metadata layers

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

A dashboard application can enable a user to quickly view data (and, in a particular aspect, data from one or more business applications) in an efficient manner. The dashboard application can be used to view data about one or more metrics that reflect the performance of a business, as derived from data maintained (perhaps in an associated data store) by the business application(s). The dashboard application can provide the ability to select a level of granularity at which data should be displayed and/or filtered for display.

Drill down functionality in a dashboard application

Growing community of inventors

Highlands Ranch, CO, United States of America

Vito Solimene