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 Link

What is a Link

A link is a structure that connects two activities and controls the order of execution of the two activities. In the BPMN-Centric palette, a link is called
edge
.
A link can include a condition, further controlling when, or if, an activity executes. The condition is an XPath (or other language) expression.
You can add multiple links between basic activities and between structured activities. You can also add links to a basic activity contained by a structured activity.
A link works inside of a flow. When you add a link between two activities, Process Developer creates a flow activity including a link definition, as shown.
Link XML Syntax
<flow> <link name="L1" /> activity1 <source linkName="L1" /> ... activity2 <target linkName="L1" /> ... </flow>
For more information about when to use links vs. using sequence, scope and other structured activities, see
Designing With Links vs. Structured Activities
.


Updated March 30, 2020