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: Persistent storage may contain metadata actions and integration actions related to a remote service, wherein the remote service includes a remote service application programming interface (API) that provides access to structured data, and a metadata API that provides access to a schema of the structured data. Processors may be configured to: (i) generate and provide, for metadata action design graphical user interfaces (GUIs), options for specification of a metadata action, where the metadata action defines a metadata query to the metadata API, rules for parsing the schema, and a normalized format for the structured data; (ii) generate and provide, for integration action design GUIs, options for specification of an integration action, where the integration action defines a structured data query to the remote service API and an indication that the metadata action is to be used to represent a result of the structured data query in the normalized format.

Abstract: A wait duration for a timer action element of a design-time flow plan is set. The wait duration being set relative to a specified data point of a table associated with the design-time flow plan. An operation associated with the timer action element executes at run-time to pause a flow for the wait duration prior to execution of an operation associated with an action element that is set to execute subsequent to the timer action element in the design-time flow plan. A specified timeframe for the timer action element of the design-time flow plan is set. The operation associated with the timer action element to pause the flow for the specified wait duration executes at run-time during the set specified timeframe. A natural language annotation associated with the timer action element of the design-time flow plan is displayed. The annotation presents the set duration and timeframe in a human-readable format.

Abstract: Persistent storage may contain a definition of an application programming interface (API) of a remote service, where the API provides access to input information stored at the remote service. One or more processors may be configured to: (i) provide, for display on an action design graphical user interface (GUI), a first menu that allows selection of a first set of the input information to be dynamically retrieved from the API during design of a workflow; (ii) provide, for display on the action design GUI, a second menu that allows selection of a second set of the input information to be dynamically retrieved from the API during design of the workflow; and (iii) provide for display, on the action design GUI, options for specifying the API, how to remotely access the API, and how to parse data received from the API.

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 relates to a transaction licensing system (TLS) for managing transactions and entitlements in a cloud-based system, wherein a transaction is a communication with an external server. The TLS includes at least one transaction licensing database (TLDB) that is configure to store entitlement and transaction data. The entitlements may include a general entitlement pool, as well as specialized entitlement pools with entitlements for executing particular transactions. The TLS is configured to determine identifying information for a transaction and then use this information to determine whether the general or specialized entitlement pools associated with the transaction has entitlements available in the TLDB to execute the transaction. When a suitable entitlement is determined to be available, the transaction is executed and the general or specialized entitlement pool is appropriately decremented. When no suitable entitlements are available, the TLS returns an exception.

Abstract: A computational instance of a remote network management platform may include persistent storage and one or more processors. The persistent storage may contain a recursively-defined complex data object, and one or more processors may be configured to: (i) transmit a depiction of a graphical user interface including a visual representation of the recursively-defined complex data object, where the complex data object as well as each array and object therein is represented as a collapsible menu item that can either display or hide its elements; (ii) receive a modification to an element of the complex data object, wherein the modification is either removal of the element, addition of the element, or a change to the associated type of the element; (iii) update the persistent storage to represent the complex data object as modified; and (iv) transmit an update to the visual representation that reflects the complex data object as modified.

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: Persistent storage may contain metadata actions and integration actions related to a remote service, wherein the remote service includes a remote service application programming interface (API) that provides access to structured data, and a metadata API that provides access to a schema of the structured data. Processors may be configured to: (i) generate and provide, for metadata action design graphical user interfaces (GUIs), options for specification of a metadata action, where the metadata action defines a metadata query to the metadata API, rules for parsing the schema, and a normalized format for the structured data; (ii) generate and provide, for integration action design GUIs, options for specification of an integration action, where the integration action defines a structured data query to the remote service API and an indication that the metadata action is to be used to represent a result of the structured data query in the normalized format.

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: Systems, methods, and media for actions in distributed computing by receiving trigger event specification that defines a trigger event that will cause a notification to be transmitted. A determination is made whether the trigger event has occurred. Responsive to the determination that the trigger event has occurred, a notification is generated. Excess data is removed from the notification. The notification, with the excess data removed, is sent.

Abstract: A system may involve persistent storage defining primitive data types and compound data types, where the compound data types include objects and arrays, where the objects contain sets of elements that have various primitive data types, compound data types, or both, and where the arrays contain sets of elements that all have one particular primitive data type or compound data type. The system may also involve one or more processors configured to provide a representation of a graphical user interface for designing a hierarchy of elements, each of the elements therein having a data type that is either a primitive data type or a compound data type, where elements in the hierarchy are associated with data type change controls, and where object elements in the hierarchy are: (i) associated with child element controls, and (ii) represented as collapsible menu items that can either display or hide their child elements.

Abstract: Persistent storage may contain metadata actions and integration actions related to a remote service, wherein the remote service includes a remote service application programming interface (API) that provides access to structured data, and a metadata API that provides access to a schema of the structured data. Processors may be configured to: (i) generate and provide, for metadata action design graphical user interfaces (GUIs), options for specification of a metadata action, where the metadata action defines a metadata query to the metadata API, rules for parsing the schema, and a normalized format for the structured data; (ii) generate and provide, for integration action design GUIs, options for specification of an integration action, where the integration action defines a structured data query to the remote service API and an indication that the metadata action is to be used to represent a result of the structured data query in the normalized format.

Abstract: Persistent storage may contain a definition of an application programming interface (API) of a remote service, where the API provides access to input information stored at the remote service. One or more processors may be configured to: (i) provide, for display on an action design graphical user interface (GUI), a first menu that allows selection of a first set of the input information to be dynamically retrieved from the API during design of a workflow; (ii) provide, for display on the action design GUI, a second menu that allows selection of a second set of the input information to be dynamically retrieved from the API during design of the workflow; and (iii) provide for display, on the action design GUI, options for specifying the API, how to remotely access the API, and how to parse data received from the API.

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 system may involve persistent storage defining primitive data types and compound data types, where the compound data types include objects and arrays, where the objects contain sets of elements that have various primitive data types, compound data types, or both, and where the arrays contain sets of elements that all have one particular primitive data type or compound data type. The system may also involve one or more processors configured to provide a representation of a graphical user interface for designing a hierarchy of elements, each of the elements therein having a data type that is either a primitive data type or a compound data type, where elements in the hierarchy are associated with data type change controls, and where object elements in the hierarchy are: (i) associated with child element controls, and (ii) represented as collapsible menu items that can either display or hide their child elements.

Abstract: A trigger element of a design-time flow plan is set so that the trigger element activates in response computing conditions being satisfied. A decision action element of the design-time flow plan executed at run-time in response to activation of the trigger element is set. The decision action element is implemented by a decision table that includes decision inputs and respective condition logic based on the decision inputs for each of a plurality of decision answers associated with the decision table. The decision table is external to the design-time flow plan. First and second decision answer action elements are defined to execute at run-time respectively when a decision answer served-up by the decision table corresponds to first and second decision answer paths in the design-time flow plan that are associated with a first and second one of the plurality of decision answers, respectively. The design-time flow plan is published.

Abstract: Persistent storage may contain a definition of an application programming interface (API) of a remote service, where the API provides access to input information stored at the remote service. One or more processors may be configured to: (i) provide, for display on an action design graphical user interface (GUI), a first menu that allows selection of a first set of the input information to be dynamically retrieved from the API during design of a workflow; (ii) provide, for display on the action design GUI, a second menu that allows selection of a second set of the input information to be dynamically retrieved from the API during design of the workflow; and (iii) provide for display, on the action design GUI, options for specifying the API, how to remotely access the API, and how to parse data received from the API.