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

Using Expressions for Outcome and Search By

Using Expressions for Outcome and Search By

Create an expression for task outcome.
You can use the following two expressions:
  • Outcome
    This optional element identifies the field of an XSD simple type variable in the output message that reflects the business result of a task. Using Outcome enables you to create a query to produce an
    xs:string
    which represents the outcome of the task. This query is run against the specified part of the output data.
    This element is not displayed in an Process Developer task client, but can be useful as part of the HT API.
  • Search By
    This optional element lets you create an expression which produces an
    xs:string
    that can be used to quickly locate a task within the a task client application. The expression evaluates using the input data for the task. For example, a loan application request contains several data parts, including an application ID customer name, and other loan details. The Search By expression may extract the application ID from the input data. In a task client, a user can type in an application ID in the Search By field to quickly retrieve a particular task.
    The Search By expression created in Designer might be:
    htd:getInput('loanPart')/@applicationId
    where
    application Id
    evaluates to a five-digit number associated with the loan application request. In the Process Developer task client, a user would enter a five-digit number in the Search By field, such as "12345", to locate a particular task.


Updated March 30, 2020