Abstract: Techniques are provided for designing a mashup. In an example embodiment, a user input is detected. The user input relates a first GUI object, which represents a first widget, to a second GUI object that represents a second widget. The first widget conforms to a first widget specification and the second widget conforms to a second widget specification that is different than the first widget specification. In response to the user input, a variable is defined, where, at run-time, a value of an output parameter of the first widget is assigned to the variable and the variable is used as an input parameter of the second widget. An event definition that defines an event is generated based on the user input, where the event, when detected at run-time, causes contents of at least one of the first widget and the second widget to be refreshed.

Abstract: Techniques are provided for designing, deploying, and executing mashups that integrate human workflows with automated processes. In an example embodiment, a system for executing mashups comprises a human interaction module, an event manager module, and a process orchestration module. The human interaction module is configured to receive user input while a human workflow included in a mashup is being executed, and to raise an event in response to the user input. The event manager module is configured to: receive the event from the human interaction module; based on the event, identify a particular automated process from one or more automated processes that are included in the mashup; and invoke the process orchestration module to execute the particular automated process based on the event. The process orchestration module is configured to execute the particular automated process in response to being invoked by the event manager module.

Abstract: Techniques are provided for designing a mashup. In an example embodiment, a user input is detected. The user input relates a first GUI object, which represents a first widget, to a second GUI object that represents a second widget. The first widget conforms to a first widget specification and the second widget conforms to a second widget specification that is different than the first widget specification. In response to the user input, a variable is defined, where, at run-time, a value of an output parameter of the first widget is assigned to the variable and the variable is used as an input parameter of the second widget. An event definition that defines an event is generated based on the user input, where the event, when detected at run-time, causes contents of at least one of the first widget and the second widget to be refreshed.

Abstract: The invention provides a process-centric, scenario-driven business service assembly software environment that uses encapsulated, iconographic building blocks—each representing a discrete Web Service component to be executed within a business service—to logically depict service processes as well as complex relationships between these processes, their audiences, and means of deployment. Fundamental to the invention are an Interactive Flow Assembler, an Interactive Flow Engine, a design-time Service Manager, and an implicit XML-based data and process model. Business users employ the Interactive Flow Assembler to create online business services that are executed by the Interactive Flow Engine by chaining a series of logical business steps that codify business rules, collect data, and take actions.