Abstract: A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programing interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

Abstract: A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programing interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

Abstract: A server receives a first hypertext transfer protocol (HTTP) from a client device that requests first and second items of content associated with a webpage and applies a defer directive to the second item. The server retrieves, from a database, via a single worker thread, first data associated with the first item and transmits a first message comprising the first data associated with the first item. The server retrieves, from the database, via the worker thread, second data associated with the deferred item and transmits a second message comprising the second data associated with the second item.

Abstract: The present disclosure is directed to a modified GraphQL server that enables application developers to define custom GraphQL schema fragments. For example, a developer may provide the GraphQL server with a GraphQL standard definition language (SDL) file having annotations that indicate that a customized data-handling script, such as a custom data-fetching script or a custom type resolver script, be called for handling certain data types or fields. These customized data-handling scripts are resolved and called at runtime based on the annotations in the GraphQL SDL file. By enabling developers to define schema fragments in the SDL language and implement data-handling scripts in a suitable scripting language, schema portability can be maintained across client instances, as well as instance release versions.

Abstract: A server receives a first hypertext transfer protocol (HTTP) from a client device that requests first and second items of content associated with a webpage and applies a defer directive to the second item. The server retrieves, from a database, via a single worker thread, first data associated with the first item and transmits a first message comprising the first data associated with the first item. The server retrieves, from the database, via the worker thread, second data associated with the deferred item and transmits a second message comprising the second data associated with the second item.

Abstract: A server receives a first hypertext transfer protocol (HTTP) from a client device that requests first and second items of content associated with a webpage and applies a defer directive to the second item. The server retrieves, from a database, via a single worker thread, first data associated with the first item and transmits a first message comprising the first data associated with the first item. The server retrieves, from the database, via the worker thread, second data associated with the deferred item and transmits a second message comprising the second data associated with the second item.

Abstract: The present disclosure is directed to a modified GraphQL server that enables application developers to define custom GraphQL schema fragments. For example, a developer may provide the GraphQL server with a GraphQL standard definition language (SDL) file having annotations that indicate that a customized data-handling script, such as a custom data-fetching script or a custom type resolver script, be called for handling certain data types or fields. These customized data-handling scripts are resolved and called at runtime based on the annotations in the GraphQL SDL file. By enabling developers to define schema fragments in the SDL language and implement data-handling scripts in a suitable scripting language, schema portability can be maintained across client instances, as well as instance release versions.

Abstract: The present disclosure is directed to a modified GraphQL server that enables application developers to define custom GraphQL schema fragments. For example, a developer may provide the GraphQL server with a GraphQL standard definition language (SDL) file having annotations that indicate that a customized data-handling script, such as a custom data-fetching script or a custom type resolver script, be called for handling certain data types or fields. These customized data-handling scripts are resolved and called at runtime based on the annotations in the GraphQL SDL file. By enabling developers to define schema fragments in the SDL language and implement data-handling scripts in a suitable scripting language, schema portability can be maintained across client instances, as well as instance release versions.

Abstract: A system includes persistent storage configured to store definitions of interfaces of remote software applications, and a software application configured to define the interfaces. The software application identifies a remote software application system by which the remote software applications are exposed for execution, and obtains therefrom a specification of a particular remote software application. The software application determines, based on the specification, (i) objects accessible by way of the particular remote software application and (ii) functions invokable to interact with the objects. The software application generates actions that define an interface for the particular remote software application. Each action is configured to invoke execution of one or more of the functions by transmitting a request to the remote software application system and, in response, receive, by way of the remote software application system, an output of the one or more of the functions.

Abstract: The present disclosure is directed to a modified GraphQL server that enables application developers to define custom GraphQL schema fragments. For example, a developer may provide the GraphQL server with a GraphQL standard definition language (SDL) file having annotations that indicate that a customized data-handling script, such as a custom data-fetching script or a custom type resolver script, be called for handling certain data types or fields. These customized data-handling scripts are resolved and called at runtime based on the annotations in the GraphQL SDL file. By enabling developers to define schema fragments in the SDL language and implement data-handling scripts in a suitable scripting language, schema portability can be maintained across client instances, as well as instance release versions.

Abstract: A computing system includes persistent storage configured to store definitions of actions for integration into workflows, and a software application configured to define an action that invokes a function of an application programming interface (API). The software application obtains a specification and identifies therein definitions of a uniform resource locator (URL) that addresses the API, the function, an input of the function, and an output of the function. The software application generates an input variable of the action that corresponds to the input of the function and an output variable of the action that corresponds to the output of the function. The software application determines a first mapping between the input variable and a URL parameter of the API and a second mapping between the output variable and a response from the API. The first and second mappings are stored in in the persistent storage to define the action.

Abstract: A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programing interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

Abstract: A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programming interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

Abstract: A system includes persistent storage configured to store definitions of interfaces of remote software applications, and a software application configured to define the interfaces. The software application identifies a remote software application system by which the remote software applications are exposed for execution, and obtains therefrom a specification of a particular remote software application. The software application determines, based on the specification, (i) objects accessible by way of the particular remote software application and (ii) functions invokable to interact with the objects. The software application generates actions that define an interface for the particular remote software application. Each action is configured to invoke execution of one or more of the functions by transmitting a request to the remote software application system and, in response, receive, by way of the remote software application system, an output of the one or more of the functions.

Abstract: A computing system includes persistent storage configured to store definitions of actions for integration into workflows, and a software application configured to define an action that invokes a function of an application programming interface (API). The software application obtains a specification and identifies therein definitions of a uniform resource locator (URL) that addresses the API, the function, an input of the function, and an output of the function. The software application generates an input variable of the action that corresponds to the input of the function and an output variable of the action that corresponds to the output of the function. The software application determines a first mapping between the input variable and a URL parameter of the API and a second mapping between the output variable and a response from the API. The first and second mappings are stored in in the persistent storage to define the action.

Abstract: A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programming interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

Abstract: A computing system includes persistent storage configured to store definitions of actions for integration into workflows, and a software application configured to define an action that invokes a function of an application programming interface (API). The software application obtains a specification and identifies therein definitions of a uniform resource locator (URL) that addresses the API, the function, an input of the function, and an output of the function. The software application generates an input variable of the action that corresponds to the input of the function and an output variable of the action that corresponds to the output of the function. The software application determines a first mapping between the input variable and a URL parameter of the API and a second mapping between the output variable and a response from the API. The first and second mappings are stored in in the persistent storage to define the action.