Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Using Task Data or Mapped Data for a Notification

Using Task Data or Mapped Data for a Notification

Notification data. Use task data or specify how to map data to another variable part.
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.
The Properties view of an inline or local notification has a Data section:
  • 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:
  1. In the Properties view of a notification used as an escalation, select the
    Map Data
    radio button.
  2. Select the
    Dialog
    button in the Expression row for the first message part.
  3. Create an expression for the data mapping, as shown in the following illustration:
    data mapping in a notification as an escalation
Example
This example comes from the 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>


Updated March 30, 2020