Abstract: A pattern-based service bus includes a plurality of bus endpoints, a bus-hosted service, and a bus storage component. The plurality of bus endpoints interact with bus participants external to the pattern-based service bus, wherein each of the plurality of bus endpoints are identified by a unique address, and type of interaction to be provided by the bus endpoint. The bus-hosted service implements patterns that define allowed interactions between each of the plurality of bus endpoints and the bus-hosted service, wherein the implemented patterns can be utilized by the plurality of bus endpoints to interact with the bus-hosted service. The bus storage component interacts with the bus-hosted service to store information relevant to operation of the pattern-based service bus.

Abstract: A pattern-based service bus includes a plurality of bus endpoints, a bus-hosted service, and a bus storage component. The plurality of bus endpoints interact with bus participants external to the pattern-based service bus, wherein each of the plurality of bus endpoints are identified by a unique address, and type of interaction to be provided by the bus endpoint. The bus-hosted service implements patterns that define allowed interactions between each of the plurality of bus endpoints and the bus-hosted service, wherein the implemented patterns can be utilized by the plurality of bus endpoints to interact with the bus-hosted service. The bus storage component interacts with the bus-hosted service to store information relevant to operation of the pattern-based service bus.

Abstract: A pattern-based service bus includes a plurality of bus endpoints, a bus-hosted service, and a bus storage component. The plurality of bus endpoints interact with bus participants external to the pattern-based service bus, wherein each of the plurality of bus endpoints are identified by a unique address, and type of interaction to be provided by the bus endpoint. The bus-hosted service implements patterns that define allowed interactions between each of the plurality of bus endpoints and the bus-hosted service, wherein the implemented patterns can be utilized by the plurality of bus endpoints to interact with the bus-hosted service. The bus storage component interacts with the bus-hosted service to store information relevant to operation of the pattern-based service bus.

Abstract: The workflow management system provides automatic management and execution of workflows that include both automated and user-driven actions. The system monitors connected external systems and/or users for the occurrence of events, which trigger the execution of one or more workflow plans. Each workflow plans consists of a plurality of actions and user actions to be performed in a sequential manner. Actions are executed automatically by the system, but user actions are executed asynchronously due to the inclusion of users in the workflow plan. The system handles the asynchronous nature of user actions by maintaining a pending user action database that users can access to view pending user actions, complete user actions, and reserve user actions for subsequent completion.

Abstract: A pattern-based service bus includes a plurality of bus endpoints, a bus-hosted service, and a bus storage component. The plurality of bus endpoints interact with bus participants external to the pattern-based service bus, wherein each of the plurality of bus endpoints are identified by a unique address, and type of interaction to be provided by the bus endpoint. The bus-hosted service implements patterns that define allowed interactions between each of the plurality of bus endpoints and the bus-hosted service, wherein the implemented patterns can be utilized by the plurality of bus endpoints to interact with the bus-hosted service. The bus storage component interacts with the bus-hosted service to store information relevant to operation of the pattern-based service bus.

Abstract: The workflow management system provides automatic management and execution of workflows that include both automated and user-driven actions. The system monitors connected external systems and/or users for the occurrence of events, which trigger the execution of one or more workflow plans. Each workflow plans consists of a plurality of actions and user actions to be performed in a sequential manner. Actions are executed automatically by the system, but user actions are executed asynchronously due to the inclusion of users in the workflow plan. The system handles the asynchronous nature of user actions by maintaining a pending user action database that users can access to view pending user actions, complete user actions, and reserve user actions for subsequent completion.