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

Routing Tasks to People at Run Time

Routing Tasks to People at Run Time

The following illustration shows what happens when a BPEL process executes a People activity.
deploying a process with a people activity
When a BPEL process executes a people activity, the task defined by the activity is routed to all potential owners and administrators defined by the task. Each user can claim a task to work on, making it unavailable for other users.
When the task owner completes the task by submitting the required information into a form, the output data is sent back to the process so that the next activity can execute.
Typically a BPEL process containing a People activity is an asynchronous, long-running process. Since the people activity effectively "invokes" a person, the expected response time is high. For this reason, when you design a BPEL process containing a people activity, you should make the process asynchronous to avoid probable Web service communication timeouts.


Updated March 30, 2020