Databases Reference
In-Depth Information
The final part of the
clause
contains the value that we want to compare our task
attribute against; here we have a choice of content, based on what we want to carry
out. The valid options are as follows:
value
: Use this when we just want to compare the value of our task attribute
against a single value.
dateValue
: This should be used in place of
value
, when the value we want
to compare is a date.
valueList
: This can contain a list of one or more values, which we would
use with either the
IN
or
NOT_IN
operator.
columnValue
: We would use this when we want to compare our task
attribute against another task attribute. This has the same structure as the
column
element.
identityTypeValue
: We can use this to compare the value against an
identity type (that is, user, group, or application role).
identityTypeValue
: This can contain a list of
identityTypeValue
elements
, which we would use with either the
IN
or
NOT_IN
operator.
•
•
•
•
•
•
In addition, the
clause
element contains two attributes:
joinOperator
: This is only required when we have two or more clauses in
the same
predicate
, and specifies how we want to chain additional clauses
together. Valid values are
AND
or
OR
.
ignoreCase
: This takes a
boolean
value and allows us to specify whether
string-based comparisons should be case sensitive.
•
•
In the case of our query, we want to restrict it to just return Order Fulfillment
tasks. We can do that by querying on the column
TaskDefinitionName
in the table
WFTask
. Adding a clause to filter on this would give us the following predicate:
<predicatexmlns="http://xmlns.oracle.com/bpel/workflow/taskQuery">
<assignmentFilter>
Creator
</assignmentFilter>
<predicate>
<clause>
<columntableName="
WFTask
">
<columnName>
TaskDefinitionName
</columnName>
</column>
<operator>
EQ
</operator>
<value>
OrderFulfillmentTask
</value>
</clause>
</predicate>
</predicate>
