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 Gateway Types

About Gateway Types

There are four types of gateways, discussed below. When you select a type, in the Properties view of a gateway, the join conditions of the incoming and outgoing links are automatically generated for that type. For a complex gateway, you can add the join condition manually. The default gateway type is Exclusive.
Based on the join conditions of the incoming or outgoing links, a gateway can be classified as one of the following:
  • Inclusive (diamond with O)
    The activity waits for at least one of the incoming links to evaluate to true and for the rest of the incoming links to be set with transition conditions. Any of the outbound links can have transition conditions, and any number of them can evaluate to true.
  • Exclusive
    The default type. The activity waits for at least one of the incoming links to evaluate to true and for the rest of the incoming links to be set with transition conditions. At most, one of the outbound links must evaluate to true. If, at run-time, more than one outbound link evaluates to true, the first link executes.
  • Parallel (diamond with +)
    The activity waits for all incoming links to evaluate to true. All outbound links are true (no transition condition is allowed out of a parallel gateway).
  • Complex (diamond with asterisk)
    The activity waits for all incoming links to be set (either true or false) and for the join condition specified within the complex gateway to evaluate to true. Any of the outbound links can have transition conditions, and any number of them can evaluate to true.
  • Event-based. See
    Pick
    .
The BPEL structured activities, such as if, while, repeat until or for each easy-to-use alternatives to building decision-making with a gateway.
An exclusive gateway is a good choice as the source or target of a loop-back links. For details, see
Mutually Exclusive Transitions
.
Required Properties
Optional Properties
Gateway Type
Name.
 
Join Condition.
Suppress Join Failure.
Comment.
Documentation.
Setting Visual Properties and Using Your Own Library of Images
Execution State.
Extension Attributes and Extension Elements.
Mutually Exclusive Transitions


Updated March 30, 2020