Pipeline Expression Language
Since Version: 3.0
The Pipeline Expression Language (PEL) or just PE (Pipeline Expression) is a powerful and easy to learn expression language based on Spring EL and adds additional features to this widely used "defacto-standard" expression language. It can be used inside a pipeline to dynamically calculate and set values. For data mapping, transformation and to dynamically calculate, set and change values at processing time of a pipeline.
The Pipeline Expression Language is optional. You do not need it for basic tasks. But it gives you additional flexibility and power to automate and integrate nearly any process since it is optimized exactly for this. So it is wise to learn at least the basics of it. Typically, it is easier to learn than a programming language.
It depends on your basic knowdlegde, but in average it is a matter of about 15-30 minutes to understand and use the basic concepts of this powerful expression language.
Basics
Typically a PE starts with #{
and ends with }
. Here is a simple example of a PE, placed inside the value of a command parameter:
pipeline:
- log:
message: "#{1 + 1}"
Output:
2
A PE can be placed in the value part of pipeline headers and values, in parameter values of most commands and in the body of a pipeline. It uses late binding: It will be executed only in case the according entry (header, variable, command parameter, ...) is referenced somewhere. It also supports interpolation in order to use the PEL like a template language inside a text string. So string concatenation can be done like this:
pipeline:
- log:
message: "Result: #{1 + 1}"
Output:
Result: 2
Accessing Sopes
Inside a Pipeline Expression, you can access the values of the pipeline scopes like headers
, vars
and body
. These scopes are provided as implicity objects and therefore they're available inside any Pipeline Expression.
Let's assume, you have defined a variable counter
and you would like to access this counter in your expression, then you could write an expression like this:
#{vars.counter}
Here is an example of a pipeline which uses this expression and outputs the value of counter
to the body:
vars:
counter: 12
pipeline:
- body.set:
value: "The counter is: #{vars.counter}"
This will result in an output like this:
The counter is: 12
Similar you could fo with the headers
scope:
headers:
contentType: "text/plain"
pipeline:
- body.set:
value: "The type is: #{headers.contentType}"
This will result in an output like this:
The type is: text/plain
Relational operators
Is equal ==
Example 1
pipeline:
- log:
message: "#{2 == 1}"
Output:
false
Is not equal !=
Example 1
pipeline:
- log:
message: "#{2 != 1}"
Output:
true
Less than <
Example 1
pipeline:
- log:
message: "#{1 < 5}"
Output:
true
Example 2
pipeline:
- log:
message: "#{0.5 < 1}"
Output:
true
Less or equal than <=
Example 1
pipeline:
- log:
message: "#{1 <= 5}"
Output:
true
Greater than >
Example 1
pipeline:
- log:
message: "#{1 > 5}"
Output:
false
Greater or equal than >=
Example 1
pipeline:
- log:
message: "#{5 >= 5}"
Output:
true
Detect alphabetical order with <
, >
, <=
, >=
Example 1
pipeline:
- log:
message: "#{'Adam' < 'Zacharias'}"
Output:
true
Regular expression matching matches
Example 1
pipeline:
- log:
message: "#{'5.0067' matches '^-?\\d+(\\.\\d{2})?$'}"
Output:
false
Logical operators
and
Example 1
pipeline:
- log:
message: "#{true and false}"
Output:
false
or
Example 1
pipeline:
- log:
message: "#{true or false}"
Output:
true
not
, !
Example 1
pipeline:
- log:
message: "#{!true}"
Output:
false
Example 2
pipeline:
- log:
message: "#{not true}"
Output:
false
Mathematical operators
Addition +
and subtraction -
Example 1 - Addition
pipeline:
- log:
message: "#{1 + 1}"
Output:
2
Example 2 - Subtraction
pipeline:
- log:
message: "#{10 - 1}"
Output:
9
Example 3 - Addition an subtraction
pipeline:
- log:
message: "#{25 - 5 + 10}"
Output:
30
Example 4 - String concatenation
pipeline:
- log:
message: "#{'Hello ' + 'World!'}"
Output:
Hello World!
Multiplication *
and division /
, %
Example 1 - Multiplication
pipeline:
- log:
message: "#{3 * 5}"
Output:
15
Example 2 - Negative multiplication
pipeline:
- log:
message: "#{-1 * 5}"
Output:
-5
Example 3 - Division
pipeline:
- log:
message: "#{20 / 5}"
Output:
4
Example 4 - Modulus
pipeline:
- log:
message: "#{7 % 4}"
Output:
3
Example 5 - Operator precedence
pipeline:
- log:
message: "#{5 + 4 - 1 * 2}"
Output:
7
Example 6 - Brackets
pipeline:
- log:
message: "#{(5 + 4 - 1) * 2}"
Output:
16
Assignment
Example 1
pipeline:
- set:
value: "1"
output: "#{vars.counter}"
- log:
message: "#{vars.counter}"
Output:
1
Example 2
vars:
counter: 12
pipeline:
- set:
value: "#{vars.counter + 1}"
output: "#{vars.counter}"
- log:
message: "#{vars.counter}"
Output:
13
Working with lists {,}
and maps {:}
Creating a new list
Example 1 - A new empty list
vars:
numbers: "#{{}}"
pipeline:
- log:
message: "#{vars.numbers}"
Output:
[]
Example 2 - A new list with default content
vars:
numbers: "#{{1, 2, 4}}"
pipeline:
- log:
message: "#{vars.numbers}"
Output:
[1, 2, 4]
Example 3 - A new, nested list
vars:
scores: "#{{ {1, 3}, {5, 8} }}"
pipeline:
- log:
message: "#{vars.scores}"
Output:
[[1, 3], [5, 8]]
Accessing lists and arrays
Example 1
vars:
numbers: "#{{1, 2, 4}}"
pipeline:
- log:
message: "#{vars.numbers[1]}"
Output:
2
Creating a new map / dictionary
Example 1 - A new empty map
vars:
persons: "#{ {:} }"
pipeline:
- log:
message: "#{vars.persons}"
Output:
{}
Example 2 - A new map with default values
vars:
persons: "#{ {hanna:'burger', max:'hotdog', julie:'salad'} }"
pipeline:
- log:
message: "#{vars.persons}"
Output:
{hanna=burger, max=hotdog, julie=salad}
Example 3 - A new map with later binding
vars:
persons: "#{ {:} }"
pipeline:
- log:
message: "#{vars.persons['Hanna'] = 23}"
Output:
{Hanna=23}
Accessing maps/dictionaries
Example 1
vars:
persons: "#{ {hanna:'burger', max:'hotdog', julie:'salad'} }"
pipeline:
- log:
message: "#{vars.persons['max']}"
Output:
hotdog
Navigating objects
A PE can point to values inside an object (or nested data structure), like this JSON for example:
{
"person": {
"name": "Bart Simpson",
"age": 12,
"hobbies": [
"skateboard",
"tv",
"pranks"
]
}
}
You can navigate any structured object available inside a vars or body scope using the dot operator. For example:
#{person.name}
To access a list/array, you can use the index operator []:
#{person.hobbies[0]}
Example
In this more advanced example, there are different things to mention:
- We create an inline map as initial vars value.
- Multi line values are done by using
'
(this trims any new line and space character at the beginning and end of the string, which is important to interpret it here as map instead of a string). - We set the body using the initial vars value using the command
set.body
also with a multi line value. - Multiple lines can also be set using
|
. Differently to'
in this case new lines will be kept so that the output of the body will look exactly as formatted in the value parameter. This is perfect if you want to write a template for example with exact format output as the value looks like. - There are comments in the configuration. A comment line starts with
#
.
See the official YAML documentation about how to deal with multi-line values. Here is a good summary: https://yaml-multiline.info/
# Set inline map as initial body value
vars:
data: '#{
{
person: {
name: "Bart Simpson",
age: 12,
hobbies: {
"skateboard",
"tv",
"pranks"
}
}
}
}'
pipeline:
# Set in the body a multiline string
- set.body:
value: |
Name: #{vars.data.person.name}
Age: #{vars.data.person.age}
Hobby: #{vars.data.person.hobbies[0]}
Formatted output:
Name: Bart Simpson
Age: 12
Hobby: skateboard
Avoid NullPointerException
In case you would like to access a property of an object which doesn't exist, a NullPointerException
will be thrown, indicating that the object you're trying to access doesn't exist. Let's see this example which will result in such an exception:
vars:
data: null
pipeline:
set.body:
value: "#{vars.data.name}"
This will throw an exception since the object data
is null
and therfore the property name
cannot be loaded.
In order to return null
instead of throwing an exception, you can use the safe navigation operator ?.
. This example will not throw an exception. Instead, it will simply put null
into the body:
vars:
data: null
pipeline:
set.body:
value: "#{vars.data?.name}"
It is also possible to use this operator on nested properties:
vars:
data: null
pipeline:
set.body:
value: "#{vars.data?.deep?.deeper?.value}"
This example will also put null
into the body instead of throwing a NullPointerException
.
Filtering
The PEL can be used to filter lists in an easy way.
Selection Expression .?
With the selection syntax you can select a subset of items from a given collection to be returned as new collection by specifying a selection expression.
Similar to the WHERE
part of an SQL query.
The syntax is like this:
collectionName.?[selectionExpression]
Whereas collectionName
is the variable name of the collection (can be an array, map, list, aso.) and selectionExpression
is the expression which selects the items to be returned from the list.
Example 1
Lets assume we have a collection of entities like this stored in the body:
[
{
"person": {
"name": "Bart Simpson",
"age": 12,
"hobbies": [
"skateboard",
"tv",
"pranks"
]
}
},
{
"person": {
"name": "Maggie Simpson",
"age": 1,
"hobbies": [
"drinking milk",
"crawling",
"crying"
]
}
}
]
Then, we can select a subset of the entries using a selection like this:
pipeline:
- log:
message: "#{body.?[person.name == 'Maggie Simpson']}"
Output would be a sublist with the entries matching the criteria:
[
{
"person": {
"name": "Maggie Simpson",
"age": 1,
"hobbies": [
"drinking milk",
"crawling",
"crying"
]
}
}
]
Here is the same example but with the data set embedded into the pipeline in the vars scope:
vars:
data: '#{{
{
person: {
name: "Bart Simpson",
age: 12,
hobbies: {
"skateboard",
"tv",
"pranks"
}
}
},
{
person: {
name: "Maggie Simpson",
age: 1,
hobbies: {
"drinking milk",
"crawling",
"crying"
}
}
}
}}'
pipeline:
- log:
message: "#{vars.data.?[person.name == 'Maggie Simpson']}"
Projection Expression .!
With the projection syntax you can select specific property values out from a collection of objects.
Similar to the SELECT
part of an SQL query.
The syntax is like this:
collectionName.![projectionExpression]
Whereas collectionName
is the variable name of the collection (can be an array, map, list, aso.) and projectionExpression
is the expression which selects the properties to be returned from each object in the list.
Example 1
Lets assume we have a collection of entities like this stored in the body:
[
{
"person": {
"name": "Bart Simpson",
"age": 12,
"hobbies": [
"skateboard",
"tv",
"pranks"
]
}
},
{
"person": {
"name": "Maggie Simpson",
"age": 1,
"hobbies": [
"drinking milk",
"crawling",
"crying"
]
}
}
]
Then, we can select properties from this collection like this:
pipeline:
- log:
message: "#{body.![person.name]}"
Output:
['Bart Simpson', 'Maggie Simpson']
And here the example with embedded data set in the vars scope:
vars:
data: '#{{
{
person: {
name: "Bart Simpson",
age: 12,
hobbies: {
"skateboard",
"tv",
"pranks"
}
}
},
{
person: {
name: "Maggie Simpson",
age: 1,
hobbies: {
"drinking milk",
"crawling",
"crying"
}
}
}
}}'
pipeline:
- log:
message: "#{vars.data.![person.name]}"
Ternary Operator (If-Then-Else)
The ternary operator can be used to define an if-then-else condition in your expression in a single line.
pipeline:
- set.body:
value: "#{10 > 100 ? 'condition is true' : 'condition is false'}"
This example would output condition is false
in the body. As you can see, the part left of the question mark ?
defines the condition to be evaluated. If this condition evaluates to true
, then the part left of the colon :
is executed. Otherwise the right part:
condition ? trueExpression : falseExpression
Functions
There are many built-in functions available which additionally can simplify your automation and integration tasks. See chapter Built-In Functions for more details.
If you would like to create your own functions instead, see chapter Custom Functions.
Report an Issue
In case you're missing something on this page, you found an error or you have an idea for improvement, please click here to create a new issue. Another way to contribute is, to click Edit this page below and directly add your changes in GitHub. Many thanks for your contribution in order to improve PIPEFORCE!