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

If

If

BPMN Implementation: Conditional Pattern
An If container executes an activity based on one or more conditions defined by the If and optional Else If elements, followed by an optional else element. The conditions are evaluated in order, and the first one to evaluate to true has its activity executed. The if container is a good choice if all conditionals can be evaluated to a true or false condition.
If you do not define a branch, an implied Else executes an empty activity.
See also
Ungrouping Selected Structured Activities
.
Required Properties
Optional Properties
If Condition
Name. See
Selecting Activity Labels
Join Condition. See
Creating a Join Condition for an Incoming Link
Suppress Join Failure. See
Process Properties
Comment. See
Adding Comments to a Process
Documentation. See
Adding Documentation to a Process
See
Setting Visual Properties and Using Your Own Library of Images
.
Execution State. See
Viewing the Execution State of an Activity or Link
Extension Attributes and Extension Elements. See
Declaring Extension Elements and Attributes
.
To build an If:
  1. From the
    Control Flow
    palette, drag a
    Conditional Pattern
    activity to the Process Editor canvas.
  2. Double-click the
    If Condition
    container to open the Expression Builder.
    Alternately, in the Properties view, click the
    Dialog (...) Button
    next to If Expression.
  3. Select the variables, functions and operators to build a Boolean expression. For details, see
    Using the Expression Builder
    .
  4. From the
    Activity
    palette, drag an activity to the If Condition container, and select activity properties.
  5. Repeat Steps 2 through 5 for the
    Else If
    or
    Else
    branches, if desired.
The following illustration shows an example of an If activity.
XML Syntax
<if standard-attributes> standard-elements <condition expressionlanguage="anyURI"?> bool-expr </condition> activity <elseif>* <condition expressionlanguage="anyURI"?> bool-expr </condition> activity </elseif> <else>? activity </else> </if>
Example:
<if xmlns:inventory="http://supply-chain.org/inventory" xmlns:FLT="http://example.com/faults"> <condition> bpel:getVariableProperty('stockResult', 'inventory:level') > 100 </condition> <flow> <!-- perform fulfillment work --> </flow> <elseif> <condition> <bpel:getVariableProperty('stockResult', 'inventory:level') >= 0 </condition> <throw faultName="FLT:OutOfStock" variable="RestockEstimate" /> </elseif> <else> <throw faultName="FLT:ItemDiscontinued" /> </else> </if>


Updated March 30, 2020