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

Process Developer Extension for Links

Process Developer Extension for Links

According to the WS-BPEL 2.0 execution rules for links, a link cannot create a control cycle by linking to a completed activity. In addition, a link cannot cross the boundary of a structured activity, such as a while activity. However, Process Developer includes an extension that allows these behaviors under certain conditions.
The following illustration shows two cases of using loop-back links to a completed activity. On the left is an example of a valid use of a loop-back link. On the right is a case that will cause an error in static analysis because it violates the fork join restriction described below.
By default, the link extension is turned on, allowing you to use loop-back links. You can turn off the extension on a process-by-process basis by setting the
Links are Transitions
property in the All tab of a process.
Execution Rules for Extension to Links
The basic execution rules for Process Developer extension to links are the following.
  • When the source of a link completes, then if the transition condition evaluates to true or there is no condition, the transition fires; if the target of the link is an activity with no other incoming transitions, the activity executes.
  • BPEL's constraints regarding how links can cross the boundaries of containers continue to hold except that a Process Developer extension link can cross out of a Repeat Until activity if the source of the link has the
    Mutually Exclusive Transitions
    property is set to
    Yes
    in an activity's Properties view. By default, this property is set to
    Yes
    for an exclusive gateway, and
    No
    for all else.
  • When an activity has
    Mutually Exclusive Transitions
    set to
    Yes
    , the normal control flow of any container that contains the activity is continued only if none of the outbound links from the activity can execute. The behavior should be obvious based on the process diagram since it follows standard BPMN semantics.
BPMN disallows links from crossing the border of any bordered activity. However, BPEL allows links to cross scope boundaries, so Process Developer also allows this behavior, even though it is not valid BPMN.
Usage Restriction for Activities in Parallel Execution
If two or more activities execute in parallel, and you want to create a link that loops back to before the parallelism, the parallelism must be encapsulated within a Fork Join container. This restriction ensures that there will not be concurrent execution of looping activities since the fork join ensures that all activities on parallel paths complete and join together before the next execution of the loop.
We recommend that you use mutually exclusive links as the source links of a gateway activity that is an exclusive type. Drawing links out of an exclusive gateway clarifies the intended behavior of outbound links. Note that using Process Developer extension links as loop-back links is similar to using a While or Repeat Until activity that is already structured for you.
Process Developer Extension Namespace for Links
You may notice that your processes include the Process Developer extension for links in the Extensions node of the Outline.


Updated March 30, 2020