nodeDescription="Calculates and adds 'delta' value into message based on the incoming and previous value",
nodeDescription="Calculates delta and amount of time passed between previous timeseries key reading "+
nodeDetails="Calculates delta and period based on the previous timeseries reading and current data. "+
"and current value for this key from the incoming message",
"Delta calculation is done in scope of the message originator, e.g. device, asset or customer.<br><br>"+
nodeDetails="Useful for metering use cases, when you need to calculate consumption based on pulse counter reading.",
"If there is input key, the output relation will be <code>Success</code> unless delta is negative and corresponding configuration parameter is set. <br>"+
"If there is no input value key in the incoming message, the output relation will be <code>Other</code>.",
nodeDescription="Adds device credentials to the message or message metadata",
nodeDescription="Adds device credentials to the message or message metadata",
nodeDetails="if message originator type is Device and device credentials was successfully fetched, "+
nodeDetails="if message originator type is Device and device credentials was successfully fetched, "+
"rule node enriches message or message metadata with <i>credentialsType</i> and <i>credentials</i> properties "+
"rule node enriches message or message metadata with <i>credentialsType</i> and <i>credentials</i> properties. "+
"and send message via <code>Success</code> chain. Otherwise message will be forwarded via <code>Failure</code> chain.",
"Useful when you need to fetch device credentials and use them for further message processing. For example, use device credentials to interact with external systems.",
nodeDescription="Adds originator customer details into message or message metadata",
nodeDescription="Adds message originator customer details into message or message metadata",
nodeDetails="Enriches incoming message or message metadata with the corresponding customer details. "+
nodeDetails="Useful in multi-customer solutions where we need dynamically use customer contact information "+
"Selected details adds to the message with predefined prefix: <code>customer_</code>. Examples: <code>customer_title</code>, <code>customer_address</code>, etc. <br><br>"+
"such as email, phone, address, etc., for notifications via email, SMS, and other notification providers.",
"The customer is selected based on the originator of the message. Supported originator types: <br><br>"+
nodeDescription="Add originators related device attributes and latest telemetry values into message or message metadata",
nodeDescription="Add originators related device attributes and/or latest telemetry values into message or message metadata",
nodeDetails="Related device lookup based on the configured relation query. "+
nodeDetails="Related device lookup based on the configured relation query. "+
"If multiple related devices are found, only first device is used for message enrichment, other entities are discarded.<br><br>"+
"If multiple related devices are found, only first device is used for message enrichment, other entities are discarded. "+
"If Attributes enrichment configured, <i>CLIENT/SHARED/SERVER</i> attributes are added into message or message metadata "+
"Useful when you need to retrieve attributes and/or latest telemetry values from device that has a relation to the message originator and use them for further message processing.",
"with specific prefix: <i>cs/shared/ss</i>. Latest telemetry value adds into message or message metadata without prefix. <br><br>"+
"See the following examples of accessing those attributes in other nodes:<br>"+
"<code>metadata.cs_serialNumber</code> - to access client side attribute 'serialNumber' that was fetched to message metadata.<br>"+
"<code>metadata.shared_limit</code> - to access shared side attribute 'limit' that was fetched to message metadata.<br>"+
"<code>msg.temperature</code> - to access latest telemetry 'temperature' that was fetched to message.<br>",
nodeDescription="Adds message originator telemetry for selected time range into message metadata",
nodeDescription="Adds message originator telemetry for selected time range into message metadata",
nodeDetails="The node allows you to configure fetch interval and fetch strategy. Fetch strategy section allows you to select fetch mode: <i>First/Last/All</i> <br><br>"+
nodeDetails="Useful when you need to get telemetry data set from the message originator for a specific time range "+
"If selected fetch mode <i>First</i> rule node will retrieve the closest telemetry to the fetch interval's start.<br>"+
"instead of fetching just the latest telemetry or if you need to get the closest telemetry to the fetch interval start or end. "+
"If selected fetch mode <i>Last</i> rule node will retrieve the closest telemetry to the fetch interval's end.<br>"+
"Also, this node can be used for telemetry aggregation within configured fetch interval.",
"If selected fetch mode <i>All</i> rule node will retrieve telemetry from the fetch interval with configurable query parameters.<br><br>"+
nodeDescription="Adds originator tenant details into message or message metadata",
nodeDescription="Adds message originator tenant details into message or message metadata",
nodeDetails="Enriches incoming message or message metadata with the corresponding tenant details. "+
nodeDetails="Useful when we need to retrieve contact information from your tenant "+
"Selected details adds to the message with predefined prefix: <code>tenant_</code>, Examples: <code>tenant_title</code> or <code>tenant_address</code>, etc.",
"such as email, phone, address, etc., for notifications via email, SMS, and other notification providers.",
ShvaykaD
3 years ago