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

Required and Optional Properties of a People Activity

Required and Optional Properties of a People Activity

The following table shows the required and optional properties of a people activity.
Required Properties
Optional Properties
One of the following is required:
  • Inline task
  • Inline notification
  • Local task
  • Local notification
For details, see
Creating an Inline Task or Notification
and
Selecting a Local Task or Notification
.
Scheduled Actions
Input variable or
toPart
. For details see,
Selecting Variables
.
Is skippable. See the topic below this table.
Output variable or
fromPart
(Only if task is selected. Not applicable for a notification.). For details, see
Selecting Variables
.
People assignment and priority overrides
 
Attachments
Using the Is Skippable Attribute
This attribute indicates whether the task associated with the activity can be skipped at runtime. A person working on a human task or a business administrator may skip a task. A skipped task becomes obsolete, and no result is returned to the process. This attribute is optional. The default for this attribute is "no".
This attribute does not apply to a notification.


Updated March 30, 2020