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

Filtering a Task List by Parameter using a WS-HT whereClause

Filtering a Task List by Parameter using a WS-HT whereClause

You can use the following operators in the whereClause:
  • >
  • >=
  • <
  • <=
  • =
  • like
  • and
  • or
  • ()
The following examples show various
whereClause
syntax. Note that the Booleans
and
and
or
are case-sensitive.
For a complete list of task column names, task types, generic human roles and other WS-HT specifications, you can work with the Informatica Business Process Manager SDK.
Example 1
The following example shows a sample
whereClause
using a standard WS-HT task property name.
<htdt:whereClause>Task.Name = 'ApproveLoan'</htdtwhereClause>
Example 2
The following example combines filter properties:
Task.Priority &lt; 3 and Task.Owner = ‘loanrep1'
Example 3
The following example also combines filter properties.
Task.PaProcessId = 10 and(Task.Escalated = true or Task.Priority = 0)
Example 4:
Using Presentation Parameters (Custom Task Properties)
The following example shows using presentation parameters:
Task.Name = ‘LoanApproval' and loanAmount &gt; 10000 and zipCode = '06484'


Updated March 30, 2020