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

What is a People Activity

What is a People Activity

A people activity contains the instructions and data a person needs in order to complete a task. When a business process requires a decision from a person, rather than an invoked service, use a people activity. Within the Process Developer, this is represented as a User Task:
In BPMN, a people activity is implemented as one of the following, depending on whether the activity contains a task or notification:
  • People Activity Containing a Task:
    • User Task
    • Manual Task
  • People Activity Containing a Notification:
    • Send Task
    • Message Send Event
The People activity starts when a task is sent to potential task owners and is complete when the task’s owner returns data to the process. Once the process receives the data, it can continue to the next execution step.
The following illustration shows a basic People activity, using a custom name, within a BPEL process.
The people activity is built with a task definition and other details through the activity’s Properties view or it can be built using Guide Designer. (See
Using Guide Designer User Tasks
for more information.)
When a BPEL process is deployed to the server and is instantiated, the task is sent to all potential owners and administrators. Anyone of these can claim ownership, work on, and complete the task.
For more details, see
Conceptual Overview of the People Activity
.


Updated March 30, 2020