Abstract: Application customizable to enable administrators of various reward/loyalty programs to control communications to members. In one embodiment, an administrator is enabled to configure various rules corresponding to an event with the application of the rules to a member information identifying which ones of multiple contents is to be sent to which of the members using which one of different channels. The rules are then stored in a non-volatile memory. On identifying the occurrence of the event, the rules, and the member information are examined to determine that a first and a second content are to be sent respectively to a first and a second member using a first and second channel. Accordingly, the first content is sent to the first member using the first channel and the second content is sent to the second member using the second channel.

Abstract: A framework for integrating applications using the Workflow Toolkit provides a graphical development environment for developing an Extensible Workflow. The Workflow Toolkit may include a user interface displaying a first list of application programming interface (API) services provided by a first application and a second list of API services provided by a second application. The Workflow Toolkit may then generate an integration component in response to a user selecting both a first API service from the first list and a second API service from the second list. The integration component can then be called from the first API service, and the integration component in turn calls the second API service. In response to the second API service being called, the second API service may return a result. When this result is received by the integration component, the integration component may return an integration result based on the result received from the second API.

Abstract: A framework for integrating applications using the Workflow Toolkit provides a graphical development environment for developing an Extensible Workflow. The Workflow Toolkit may include a user interface displaying a first list of application programming interface (API) services provided by a first application and a second list of API services provided by a second application. The Workflow Toolkit may then generate an integration component in response to a user selecting both a first API service from the first list and a second API service from the second list. The integration component can then be called from the first API service, and the integration component in turn calls the second API service. In response to the second API service being called, the second API service may return a result. When this result is received by the integration component, the integration component may return an integration result based on the result received from the second API.