About Send Tasks
The send task is designed to work together with a receive task. A send task delivers a message to a targeted recipient (the receive task) using one of the following protocols:
Subscription (for publishable documents)
JMS (for JMS -triggered processes) (default)
Simple service (for synchronous receive/send)
Send task steps behave as follows:
In a top level process: the send task will publish the associated document.
In a child process called using the dynamic referenced process step: The send task will publish the document, and if it is listed as one of the return documents, the send task will send the document to the parent process instance directly.
In a child process called using a call activity step: the send task will publish the document. The send task will publish the document, and the pipeline will pass from the child to the parent when the child process completes, which could be several steps after the send task step.
Note:
When creating a callable process that is to be called by a call activity step, always implement a send task in the callable process to return to the parent process. If you use either a message end event or message intermediate event, those steps will only publish a document and will not return it to the parent.
When a send task step is used in a process invoked as a referenced subprocess:
If an IS document is configured both as a
Send Document and a
Return Document for the parent process, the document is not published to the messaging provider.
If an IS document is configured as a
Send Document, but not as a
Return Document for the parent process, the document is published to the messaging provider.
Publish steps in models created with versions of Designer earlier than 8.2 are converted to send tasks upon import. These send tasks are automatically configured to use the publish document from the original publish step. Reply steps that use the simple service protocol in earlier Designer models are also converted to send tasks.
Related Topics