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

Example XPath Expressions

Example XPath Expressions

The following are example expressions for message, element and complex schema type variables.
  • Element type variable:
    Example:
    $AStatus/e:statusDescription
    Selects the
    statusDescription
    child node of
    AStatus
    element
  • Message type variable:
    Example:
    $StatusVariable.StatusPart2/e:statusDescription
    Selects the
    statusDescription
    child node of the
    StatusPart2
    part of
    StatusVariable
  • Schema complex type variable:
    Example:
    $Results/e:AuctionResult[2]/@AuctionID
    Selects the
    AuctionID
    attribute of the second
    AuctionResult
    child node
  • Expression statement
    itemsShipped = itemsShipped + itemsCount:
    $itemsShipped + $shipnotice.props/itemsCount
  • Convert
    a variable and part to a string:
    string($input.parameters)
  • Referencing a child node by localname only
    This can be useful when a schema has an
    xsd:any
    element in it, such as:
    <xs:any minOccurs="0" maxOccurs="unbounded"      namespace="##other" processContents="lax"/>
The Expression Builder doesn't show the structure in the variable tree view. To use the element, the namespace prefix can be ignored as in this example:
$creditInformation/*[local-name()= "previousLoanApplicationAttempts"][1] /*[local-name()="applicationDate"]
Selects the date of the first previous loan application, if information about previous loan applications is supplied as additional content for the creditInformation message.


Updated March 30, 2020