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

Merging Input and Output Fields in a Task Form

Merging Input and Output Fields in a Task Form

Create an HTML form to render a task's input and output messages for Process Central task client. The form opens in a Web Page Editor.
Use the Input to Output Merge Mappings dialog to map a task input message element to a task output element of the same type.
When a task form is generated, the form's input and output sections are generated as separate sections. In cases where the task's input and output messages have the same or similar elements, this leads to a lot of redundancy in the form that is generated. For example, in the case where the input and output messages are exactly the same, the input section provides a read-only view of the data, and the output section provides an editable view of the same fields. Also, initially, when the form is loaded, the output section would be empty and the task owner would have to reenter data from the input fields to the output fields. The use of merge mappings in these scenarios makes the form simpler and easier to use.
Merge mappings is a way to specify that certain sections of the input and output are the same, and are to be treated as such. When such a mapping is specified, the generated task form shows a consolidated view of those mapped elements. The fields contain initial values from the task's input data, and when the task form is saved, the values are saved to the task's output elements.
When you create a new task form, be sure to select the checkbox for Merge input and output fields. The task form wizard presents a dialog for you to add individual mappings between input fields and output fields.
For each element in input that needs to be mapped to an output element, create a new entry in the mappings table. Select
Add
to open the Merge Mapping dialog and select an input element and an output element. Validation messages in this dialog assist you in selecting compatible entries.


Updated March 30, 2020