@ -292,30 +292,29 @@ public class CalculatedFieldManagerMessageProcessor extends AbstractContextAware
newCfCtx.init();
newCfCtx.init();
}catch(Exceptione){
}catch(Exceptione){
throwCalculatedFieldException.builder().ctx(newCfCtx).eventEntity(newCfCtx.getEntityId()).cause(e).errorMessage("Failed to initialize CF context").build();
throwCalculatedFieldException.builder().ctx(newCfCtx).eventEntity(newCfCtx.getEntityId()).cause(e).errorMessage("Failed to initialize CF context").build();
# Safety trigger to fall back to use_ts_key_value_partitioning_on_read as true if estimated partitions count is greater than safety trigger value.
# It helps to prevent building huge partition list (OOM) for corner cases (like from 0 to infinity) and prefer fewer reads strategy from NoSQL database
"This node is particularly useful when device isn't using transports to receive data, such as when fetching data from external API or computing new data within the rule chain.",
"This node is particularly useful when device isn't using transports to receive data, such as when fetching data from external API or computing new data within the rule chain.",
"Other entities can be assigned only to one customer, so specified customer title in the configuration will be ignored if the originator isn't a dashboard.",
"Other entities can be assigned only to one customer, so specified customer title in the configuration will be ignored if the originator isn't a dashboard.",
"The output is forwarded to the caller rule chain, as an output of the corresponding \"input\" rule node. "+
"The output is forwarded to the caller rule chain, as an output of the corresponding \"input\" rule node. "+
"The output rule node name corresponds to the relation type of the output message, and it is used to forward messages to other rule nodes in the caller rule chain. ",
"The output rule node name corresponds to the relation type of the output message, and it is used to forward messages to other rule nodes in the caller rule chain. ",
"If the presence monitoring strategy <b>\"On each message\"</b> is selected, sends messages via rule node connection type <code>Inside</code> or <code>Outside</code> every time the geofencing condition is satisfied. "+
"If the presence monitoring strategy <b>\"On each message\"</b> is selected, sends messages via rule node connection type <code>Inside</code> or <code>Outside</code> every time the geofencing condition is satisfied. "+
nodeDetails="Transforms message to email message. If transformation completed successfully output message type will be set to <code>SEND_EMAIL</code>.<br><br>"+
nodeDetails="Transforms message to email message. If transformation completed successfully output message type will be set to <code>SEND_EMAIL</code>.<br><br>"+
privatestaticfinalStringRELATED_DEVICE_NOT_FOUND_MESSAGE="Failed to find related device to message originator using relation query specified in the configuration!";
privatestaticfinalStringRELATED_DEVICE_NOT_FOUND_MESSAGE="Failed to find related device to message originator using relation query specified in the configuration!";
"If multiple related entities are found, only first entity is used for message enrichment, other entities are discarded. "+
"If multiple related entities are found, only first entity is used for message enrichment, other entities are discarded. "+
"Useful when you need to retrieve data from an entity that has a relation to the message originator and use them for further message processing.<br><br>"+
"Useful when you need to retrieve data from an entity that has a relation to the message originator and use them for further message processing.<br><br>"+
privatestaticfinalStringRELATED_ENTITY_NOT_FOUND_MESSAGE="Failed to find related entity to message originator using relation query specified in the configuration!";
privatestaticfinalStringRELATED_ENTITY_NOT_FOUND_MESSAGE="Failed to find related entity to message originator using relation query specified in the configuration!";
default->thrownewTbNodeException("Undefined message properties type '"+name+"'! Only "+supportedPropertiesStr+" message properties types are supported!");
returnMessageProperties.MINIMAL_PERSISTENT_BASIC;
};
case"PERSISTENT_BASIC":
returnMessageProperties.PERSISTENT_BASIC;
case"PERSISTENT_TEXT_PLAIN":
returnMessageProperties.PERSISTENT_TEXT_PLAIN;
default:
thrownewTbNodeException("Undefined message properties type '"+name+
"'! Only "+supportedPropertiesStr+" message properties types are supported!");
"<br/><b>Note-</b> if you use system proxy properties, the next system proxy properties should be added: \"http.proxyHost\" and \"http.proxyPort\" or \"https.proxyHost\" and \"https.proxyPort\" or \"socksProxyHost\" and \"socksProxyPort\","+
"<br/><b>Note-</b> if you use system proxy properties, the next system proxy properties should be added: \"http.proxyHost\" and \"http.proxyPort\" or \"https.proxyHost\" and \"https.proxyPort\" or \"socksProxyHost\" and \"socksProxyPort\","+
"and if your proxy with auth, the next ones should be added: \"tb.proxy.user\" and \"tb.proxy.password\" to the thingsboard.conf file.",
"and if your proxy with auth, the next ones should be added: \"tb.proxy.user\" and \"tb.proxy.password\" to the thingsboard.conf file.",