Label
|
Data Type
|
---|---|
Name
|
String data object
|
ProductId
|
String data object
|
Discount
|
Numeric data object
|
Cost
|
Numeric data object
|
SalePrice
|
Numeric data object
|
ShipDate
|
Date data object (includes both date and time values)
|
ProductId == "A123B"
(ProductId == "A123B") && (Name == "Smith")
Discount >= 5
SalePrice == (Cost – Discount)
upcase(ProductID) == "A1235CC"
${}
syntax so that the complete path to the data object can be specified. (See Data Object Substitution.) This is useful if a global data object defined on the root task and a local data object have the same name, and if you want the decision gateway to use the global object. In this example, the decision gateway uses the data object Discount that is defined on the parent workflow.
${/Main/Discount} > 1000
datepart(ShipDate) == today()
timepart(ShipDate) >= today()
ShipDate > today()