Skip to content
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

[Doc] Fix explicitAttrs doc #1529

Merged
merged 1 commit into from
Nov 22, 2023
Merged

[Doc] Fix explicitAttrs doc #1529

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 6 additions & 0 deletions doc/api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -436,6 +436,9 @@ conditionally TimeInstant) will be propagated to NGSI interface (note that in th
not a JSON but a JEXL Array that looks likes a JSON). Only static attributes included in that array will be propagated
to NGSI interface.

All attributes contained in the array must be defined as `attributes` or `static_attributes`. Not defined measures
(`object_id`) will be dropped, even if they are defined in the `explicitAttrs` array.

Case 4:

```
Expand All @@ -447,6 +450,9 @@ propagated to NGSI interface (note that in this case the value of `explicitAttrs
that looks likes a JSON). This is necessary when same attribute names are used within multiple entities. Only static
attributes included in that array will be propagated to NGSI interface.

Note that in the previous case show above, when selecting the object_id (with `{object_id:'active_id'}`), the attribute
must be defined. In other words, it would not work if the attribute with the corresponding `object_id`, is not defined.

Case 5:

```
Expand Down