From 2adb1c48e045c35c2e603b958879232df9330f43 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ferm=C3=ADn=20Gal=C3=A1n=20M=C3=A1rquez?= Date: Thu, 17 Oct 2024 09:01:34 +0200 Subject: [PATCH] FIX typos in update api.md --- doc/api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api.md b/doc/api.md index 5b9ac8aa4..27b9b3c1b 100644 --- a/doc/api.md +++ b/doc/api.md @@ -277,12 +277,12 @@ IOTAgent, you can create it in advance using the Context Broker By default, the entity name used to persist the device measures in the Context Broker can be defined in the device provisioning or, if the device is autoprovisioned, it is generated by the IoT Agent as a concatenation of the entity type and the device ID. If you need to generate the entity name differently, it is possible to define an expression to -generate it, using the [Expression Language](#expression-language-support) through the `entityNameExp` attribute in the +generate it, using the [Expression Language](#expression-language-support) through the `entityNameExp` field in the group. With this feature, the entity name can be generated dynamically based not only on the device ID and entity type, but -also on the measures reported by the device or any other context information. The `entityNameExp` attribute is only -available at the group level. **Important**: when using `entityNameExp`, the `entity_name` attribute in the device +also on the measures reported by the device or any other context information. The `entityNameExp` field is only +available at the group level. **Important**: when using `entityNameExp`, the `entity_name` field in the device provisioning is ignored. This means that the entity name used to store the device information in the Context Broker is always generated by the `entityNameExp` expression. If you need to explicitly define the entity name for a particular device, you can include a particular condition in the `entityNameExp` expression to handle that case (e.g.