Trigger an Incoming Message Activity from a Business Service
You can trigger any incoming message activity in a business process (that is, In-flow Receive Task and Intermediate Catch Message event, and Message Event handler).
The purpose of this business service is to collect the data needed to trigger the incoming message activity or event handler, and send the data to the business process.
Procedure
Right-click on the incoming message activity and select
Business Service
> Generate.
A new Business Service process is generated, using a default name similar to
ProcessPackage-Process. You should rename this to a more descriptive name, to allow you to identify it easily in the list of Business Services, when you have deployed.
The business service process consists of a start event, a user task and a send task.
The
User Task will contain a datafield generated with the same name as the formal parameter defined in the business process.
The
Send Task calls the business process from which it is generated.
Note: A system participant is automatically created for the send task that calls the business process. This participant has the name:
ProcessName_consumer
where:
ProcessName is the name of the business process being called.
Add additional user tasks to meet your requirements.
Tip: By the time that the Send Task is invoked, all parameters to the business process must have been collected. In the generated case, all are mandatory. On the user task, more realistically you might have several user tasks that all collect a proportion of the data.
A business service is generated.
When you deploy this process it will be presented as a business service in a list of business services. See "Business Services" in the
TIBCO Openspace User’s Guide
or
TIBCO Workspace User’s Guide for more information.
