Using Task Data or Mapped Data for a Notification

ActiveVOS Designer BPEL for People User’s Guide

Using Task Data or Mapped Data for a Notification

Like a task, a notification has input data based on a WSDL interface. The interface for a notification serving as a task deadline’s escalation action may be the same or different from the interface for the task.

In the Properties view of an inline or local notification, there is a Data section, which has two selections for data usage:

Use Task Data. If the notification's input data is the same as the enclosing task's, then this option is available for selection. The input message of the task is passed to the notification.

Map Data. If the notification’s data is a different type, then you can assign appropriate data to the notification to create a multi-part WSDL message from the data. The part attribute refers to a part of the WSDL message. You must map each part for every part in the WSDL message definition to avoid uninitialized parts in the target WSDL message.

To map data:

In the Properties view of a notification used as an escalation, select the Map Data radio button.
Select the Dialog Button in the Expression row for the first message part.
Create an expression for the data mapping, as shown in the following illustration.

data mapping in a notification as an escalation

Here is an XML example from WS-HT specification:

<htd:toParts>

  <htd:toPart name="firstname">

    htd:getInput("ClaimApprovalRequest","ApproveClaim")

            /firstname

  </htd:toPart>

  <htd:toPart name="lastname">

    htd:getInput("ClaimApprovalRequest","ApproveClaim")

           /lastname

  </htd:toPart>

  <htd:toPart name="taskId">

           htd:getTaskID("ApproveClaim")

  </htd:toPart>

</htd:toParts>