Skip to content

FIX improve expression plugin documentation #845

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlvaroVega merged 3 commits into from
May 6, 2020
Merged

FIX improve expression plugin documentation #845

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d1fe5fd
FIX improve expression plugin documentation
fgalan Feb 24, 2020
0505380
Merge branch 'master' into fgalan-patch-1
fgalan May 6, 2020
31c0b02
FIX CNR
fgalan May 6, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGES_NEXT_RELEASE
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
Set Nodejs 10 as minimum version in packages.json (effectively removing Nodev8 from supported versions)
Add mongodb additional options (`ssl` and `extraArgs`) to be able to connect "MongoDB as a Cloud Service" (#859)
Add support for JEXL as expression language (#801)
Add support for JEXL as expression language (#801, #687)
16 changes: 14 additions & 2 deletions doc/expressionLanguage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,15 @@ provisioning. The following example shows a device provisioning payload with def
"expression": "${@level / 100}"
},
{
"object_id": "tt",
"name": "temperature",
"name": "level",
"type": "Number"
},
{
"name": "latitude",
"type": "Number"
},
{
"name": "longitude",
"type": "Number"
}
]
Expand All @@ -62,6 +69,11 @@ Expression Language (see definition [below](#language-description)). In order fo
evaluated, all the expression patterns must be evaluatable (there must be a value in the measurement for all the
variables of all the expression patterns).

Note that you need to include in the provision operation all the attributes required as inputs for the expressions.
In this example, they are `level`, `latitude` and `longitude`. Otherwise the device sending the measures will get
`{"name":"ATTRIBUTE_NOT_FOUND","message":"Some of the attributes does not exist"}` when it sends some of these
and the expression will not be calculated.

The exact same syntax works for Configuration and Device provisioning.

### Variable values
Expand Down