Designer 10.5 | webMethods BPM Task Development Help | Working with Task Expressions | Task Expression Overview
 
Task Expression Overview
The task expression language used within Software AG Designer is proprietary and is essentially simplistic in nature. However, it does offer binding capability to a wide range of data within the task environment, and all the bindings are JSF binding expressions as well. You can find more information about working with the JSF expression language from various sources on the Web.
Task expressions fall into the following general categories:
*Condition expressions that must be matched for an assignment to be applied.
*Action expressions that carries out some user-defined activity.
*Filter expressions that define which tasks appear in the user's inbox.
In addition, you can also use expression terms to create bindings to run-time data associated with the task.
A basic expression statement consists of the following:
[A data field] [An operator] [A data field]
For example, the following condition expression determines if the current task status is "active:"
#{currentTask.taskInfo.status} == "active"
For more information on task status, see About Task Status.
When an expression contains two or more elements, the elements must be separated by a semi-colon (";"). For example:
#{currentTask.taskInfo.priority} = "high"; #{currentTask.applyChanges};
You can build advanced task expressions with the Edit Expression dialog box used for defining advanced conditions and event actions. For more information about advanced task expressions, see Configuring Advanced Task Expressions.
For further information about creating task expressions, see the following topics:
* Configuring Advanced Task Expressions
* Building a Sample Task Expression
* Viewing Sample Task Expression Syntax
* About Condition Expressions
* About Filter Expressions
* About Expression Operators
* About Date/Time Values in Expressions
* About Expression Managed Beans
Related Topics