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

Designer

Designer

Execution Rules for Links

Execution Rules for Links

Once an activity completes, it evaluates any condition on the outgoing links. If no condition is defined and the activity has completed normally, all conditions evaluate to true so that the next activity can start. However, an activity can have a join condition set that further constrains execution. For more information, see
Links and the Join Condition
.
If an activity has faulted or could not be run, all conditions evaluate to false.
An activity can have multiple incoming links. The activity must wait to run until at least one of its incoming links evaluates to true.
If all incoming links are false, the activity cannot run unless a
supressJoinFailure
property is true.
A link can cross the boundary of a structured activity, except for the following:
  • While activity
  • Isolated scope
  • Event handler
  • Compensation handler
A link that crosses the boundary of a fault handler must have its source within the fault handler and its target within a scope that encloses the fault handler scope.
In WS-BPEL, a link cannot create a control cycle by linking to a completed activity. However, in Process Developer, this behavior is allowed, as described in
Process Developer Extension for Links
.

0 COMMENTS

We’d like to hear from you!