Modifying Task Information in the Task Envelope Data Flow
You can add a functioning task activity to your process model by either adding an existing task from the Solutions view, or by implementing a new task directly from the process canvas. For more information, see webMethods BPM Process Development Help.
Either way, when the task is added, Designer creates two wrapper services to handle the task envelope data:
[
taskName]InputMapService. This is the input mapping service that is responsible for mapping business data and task info from the pipeline to queue a task. Task info is passed to this service in the document
pub.task:TaskQueueInfo.
You can use this document to modify the data being passed to the task from the pipeline. For example, you can use the assignedToList string element to specify one or more task assignees.
[
taskName]OutputMapService. This is the output mapping service that is called by
Process Engine when a task is completed (that is, ended with "Completed", "Error", "Cancelled", or "Expired" status). It contains the document
pub.task:TaskCompletionInfo which is populated with the data from the completed task.
You can use this document to modify the data being passed to the pipeline from the task. For example, you can create error logic that determines a particular error code and add it to the document.
The use of these documents is not required, but they are always available should you want to use them.
For more information about the documents
pub.task:TaskQueueInfo and
pub.task:TaskCompletionInfo and their contents, see the built-in services chapter of the PDF publication
webMethods Task Engine API and Service Reference. For general information about
Task Engine services, see
Working with the Task Engine APIs.
For more information about working with input and output mapping and document handling, see webMethods Service Development Help.
Related Topics