Abstract: Techniques for managing user interface (UI) building blocks (UIBB) include presenting, by a form repeater UIBB, initial UI representations of structured entities through a graphical user interface (GUI), each initial UI representation including one or more fields; receiving a trigger from a user through the form repeater UIBB; determining, based on the trigger, an event condition; and based on the event condition, replacing, by a substitute UIBB, an initial UI representation of a particular structured entity of the initial UI representations of the structured entities with a substitute UI representation of the particular structured entity.

Abstract: Various embodiments of systems and methods for an application creation tool (ACT) toolkit are described herein. The ACT toolkit includes a set of application creation APIs and an application creation service for invoking the set of application creation API. An ACT is in communication with the application creation service of the ACT toolkit. The ACT sends an application creation request to the application creation service for creating a UI application. The ACT can be customized by re-defining the application creation service of the ACT toolkit and establishing a communication between the re-defined application creation service and the ACT. The re-defined application creation service invokes the set of API to create a customized application object for the UI application.

Abstract: Techniques for managing user interface (UI) building blocks (UIBB) include presenting, by a form repeater UIBB, initial UI representations of structured entities through a graphical user interface (GUI), each initial UI representation including one or more fields; receiving a trigger from a user through the form repeater UIBB; determining, based on the trigger, an event condition; and based on the event condition, replacing, by a substitute UIBB, an initial UI representation of a particular structured entity of the initial UI representations of the structured entities with a substitute UI representation of the particular structured entity.

Abstract: A computer-implemented method can include executing a first application in stateful manner, wherein the first application executes continuously while receiving a sequence of a plurality of inputs from a user; and, in response to each of at least some of the plurality of inputs at the first application, executing a second application in a stateless manner by an execution controller, wherein the stateless execution can include the execution controller instructing the second application to execute an ordered stack of action scripts, the second application initiating and executing the ordered stack of action scripts, and the second application terminating upon completion of the executing of the ordered stack of action scripts.

Abstract: Various embodiments of systems and methods for an application creation tool (ACT) toolkit are described herein. The ACT toolkit includes a set of application creation APIs and an application creation service for invoking the set of application creation API. An ACT is in communication with the application creation service of the ACT toolkit. The ACT sends an application creation request to the application creation service for creating a UI application. The ACT can be customized by re-defining the application creation service of the ACT toolkit and establishing a communication between the re-defined application creation service and the ACT. The re-defined application creation service invokes the set of API to create a customized application object for the UI application.

Abstract: Methods, computer-readable media, and systems control a backend. In one implementation, a method controls a backend by executing, at the backend, at least one command. The method may determine, by applying a set of ambistateful criteria, whether to place the backend under stateless control or stateful control, upon completion of executing the at least one command.

Abstract: A computer-implemented method can include executing a first application in stateful manner, wherein the first application executes continuously while receiving a sequence of a plurality of inputs from a user; and, in response to each of at least some of the plurality of inputs at the first application, executing a second application in a stateless manner by an execution controller, wherein the stateless execution can include the execution controller instructing the second application to execute an ordered stack of action scripts, the second application initiating and executing the ordered stack of action scripts, and the second application terminating upon completion of the executing of the ordered stack of action scripts.

Abstract: Systems and methods are provided for cascaded processing a plurality of data objects. Each data object may be assigned to a folder among a plurality of folders, wherein a main process distributes the plurality of folders to a corresponding number of parallel processes of a first tier of processes. Each parallel process may select the data objects to be processed for the respective folder, split the selected data objects into packages of appropriate size, respectively, and distribute the packages similar to a cascade to a corresponding number of further parallel sub-processes of a second tier of processes, whereupon each package is processed.

Abstract: One embodiment of a method comprises adding an action script to an ordered stack of action scripts maintained by an execution controller, wherein the added action script corresponds to a navigation input received at a first application, the added action script is unpopulated by a data input, and the added action script is added last in an order of the ordered stack. The embodiment also comprises providing the ordered stack of action scripts to a second application by the execution controller, and executing at the second application the ordered stack of action scripts according to the order, the ordered stack having the unpopulated first action script. The embodiment also comprises populating the added first action script with the data input, wherein the data input is received at the first application and the populating occurs after the executing.

Abstract: A method includes receiving by a first application an input from a user; performing a service by the second application, the service related to the input received by the first application; obtaining a log of all data locks set by the second application while performing the service, wherein the log indicates a data lock object and a data lock argument for each data lock set by the second application; and setting a generic lock having an associated generic lock object and a generic lock argument, wherein the generic lock argument indicates the data lock object and the data lock argument. In one embodiment, the a unique checksum is created, using an algorithm, for every service response.

Abstract: Methods, computer-readable media, and systems control a backend. In one implementation, a method controls a backend by executing, at the backend, at least one command. The method may determine, by applying a set of ambistateful criteria, whether to place the backend under stateless control or stateful control, upon completion of executing the at least one command.

Abstract: Systems and methods are provided for cascaded processing a plurality of data objects. Each data object may be assigned to a folder among a plurality of folders, wherein a main process distributes the plurality of folders to a corresponding number of parallel processes of a first tier of processes. Each parallel process may select the data objects to be processed for the respective folder, split the selected data objects into packages of appropriate size, respectively, and distribute the packages similar to a cascade to a corresponding number of further parallel sub-processes of a second tier of processes, whereupon each package is processed.