Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: In a graphical user interface (GUI) for a personal computer system, an improved method and apparatus for accessing and executing commands associated with user applications. In addition to the standard menu categories of a menubar and control icons of a tool bar, the present invention provides a "hyperbutton", a "context sensitive pop-up menu" and a "menu control editor". A hyperbutton displays, in a persistent subview, a user selected default hyperitem from the hyperitems of the menubar. The default hyperitem is automatically executed when selected by the user with a mouse. The hyperbutton displays a title of the default hyperitem. The user can change the default hyperitem using a pop-up menu displayed in response to an interface command such as a right mouse button. A context sensitive pop-up menu is associated with a particular object such as a grid subview. The user configures the context sensitive pop-up menu to contain a custom set of the hyperitems associated with the object.