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

About Tasks

About Tasks

To include human participation as part of process execution, you can add a People activity and define a task for it.
A task is a Human Task (WS-HT) construct that relies on a WSDL interface, people assignments, and other details. By itself a task is not executable. It is designed to be used by a People activity. A special type of task is a notification. For details, see
About Notifications
.
The BPEL4People specification defines several ways that People activities can incorporate tasks, as shown in the following illustration.
Process Developer handles each of the task implementations as follows:
  • Inline Task #1.
    Define a task within a People activity for use only within that activity
    For implementation details, see
    Creating an Inline or Local Notification Action for a Task Deadline
    .
  • Inline Task #2 (Local Task).
    Define a task within the Human Interactions element on the Outline view to make it available to all People activities in a process. The People activity can use the task as is or create overrides for some properties.
    For implementation details, see
    Adding a Task or Notification to the Outline View for Process or Scope Use
    .
  • Stand Alone Task #3
    . (This is a future implementation.) Import into the process a human interaction XML document that contains a task definition and refer to the document within a People activity.
  • Stand Alone Task #4
    . (This is a future implementation.) Refer to a remote task.
A task definition includes the following parts:
  • Task Name, Interface, and Priority
  • Role Assignments for a Task or Notification
  • Adding Task or Notification Presentation Properties
  • About Task Deadlines and Escalations
  • Using Expressions for Outcome and Search By
  • Adding Rendering Details for a Task or Notification
See also
Required and Optional Properties for a Task
and
Using the All Tab of a Task
.


Updated March 30, 2020