nodeDescription="Checks the existence of the selected keys from message data and metadata.",
nodeDetails="If selected checkbox 'Check that all selected keys are present'\" and all keys in message data and metadata are exist - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.\n"+
"Else if the checkbox is not selected, and at least one of the keys from data or metadata of the message exists - send Message via <b>True</b> chain, otherwise, <b>False</b> chain is used. ",
nodeDescription="Checks the presence of the specified fields in the message and/or metadata.",
nodeDetails="Checks the presence of the specified fields in the message and/or metadata. "+
"By default, the rule node checks that all specified fields need to be present. "+
"Uncheck the 'Check that all specified fields are present' if the presence of at least one field is sufficient.",
nodeDescription="Filter incoming messages by message Originator Type",
nodeDetails="If the entity type of the incoming message originator is expected - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.",
nodeDescription="Filter incoming messages by the type of message originator entity",
nodeDetails="Checks that the entity type of the incoming message originator matches one of the values specified in the filter.",
nodeDescription="Filter incoming messages by GPS based geofencing",
nodeDetails="Extracts latitude and longitude parameters from incoming message and returns 'True' if they are inside configured perimeters, 'False' otherwise.",
nodeDetails="Extracts latitude and longitude parameters from the incoming message and checks them according to configured perimeter. </br>"+
"Configuration:</br></br>"+
"<ul>"+
"<li>Latitude key name - name of the message field that contains location latitude;</li>"+
"<li>Longitude key name - name of the message field that contains location longitude;</li>"+
"<li>Perimeter type - Polygon or Circle;</li>"+
"<li>Fetch perimeter from message metadata - checkbox to load perimeter from message metadata; "+
" Enable if your perimeter is specific to device/asset and you store it as device/asset attribute;</li>"+
"<li>Perimeter key name - name of the metadata key that stores perimeter information;</li>"+
"<li>For Polygon perimeter type: <ul>"+
" <li>Polygon definition - string that contains array of coordinates in the following format: [[lat1, lon1],[lat2, lon2],[lat3, lon3], ... , [latN, lonN]]</li>"+
"</ul></li>"+
"<li>For Circle perimeter type: <ul>"+
" <li>Center latitude - latitude of the circle perimeter center;</li>"+
" <li>Center longitude - longitude of the circle perimeter center;</li>"+
" <li>Range - value of the circle perimeter range, double-precision floating-point value;</li>"+
" <li>Range units - one of: Meter, Kilometer, Foot, Mile, Nautical Mile;</li>"+
"</ul></li></ul></br>"+
"Rule node will use default metadata key names, if the \"Fetch perimeter from message metadata\" is enabled and \"Perimeter key name\" is not configured. "+
"Default metadata key names for polygon perimeter type is \"perimeter\". Default metadata key names for circle perimeter are: \"centerLatitude\", \"centerLongitude\", \"range\", \"rangeUnit\"."+
"</br></br>"+
"Structure of the circle perimeter definition (stored in server-side attribute, for example):"+
dashevchenko
3 years ago