Last modified by Hera Guo on 2024/11/11 16:48
From version 2.1
edited by Hera Guo
on 2024/10/31 14:53
Change comment: There is no comment for this version
To version 4.1
edited by Hera Guo
on 2024/11/07 15:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,9 @@
1 +**Table of Contents:**
2 +
3 +{{toc/}}
4 +
5 +
6 +
1 1  = 1.About rule chains =
2 2  
3 3  The system provides a rule chain library for developers to configure message transformation, filtering, computation, and transmission on their own.
... ... @@ -157,7 +157,7 @@
157 157  * **Exclude zero deltas from outbound message:**Only output data with delta difference non-zero.
158 158  * **Explanation:** Non mandatory field, additional explanation;
159 159  
160 -According to the running results, there are three types of exits for this rule node:** Success**, **Failure**, and **Other**:
166 +According to the running results, there are three types of exits for this rule node:** Success**, **Failure**, and **Other**:
161 161  
162 162  * **Success:** The data export for successful incremental calculation;
163 163  * **Failure:** The data exit for message processing failure. If Tell Failure if delta is negative is checked, the data with a negative increment will be calculated and output from this exit;
... ... @@ -229,20 +229,149 @@
229 229  
230 230  === 6.2.5 tenant details ===
231 231  
238 +
239 +
240 +
241 +
242 +This rule node is used to add some detailed information configured for tenants to the message and distribute data based on the processing results. The configuration content of this node is exactly the same as that of the customer details rule node, and will not be repeated here.
243 +
244 +A simple usage example is as follows:
245 +
246 +[[image:1730964386323-616.png||height="740" width="1394"]]
247 +
248 +
249 +
232 232  === 6.2.6 fetch device credentials ===
233 233  
252 +
253 +
254 +
255 +
256 +This node is used to add the device's key and token type to the message and pass it to downstream nodes. The node configuration includes:
257 +
258 +**Name:** required field, indicating the name of the node;
259 +
260 +**Retrieve credentials to metadata: **Select the option and add the device key information to the metadata. Otherwise, add it to the message data and select it by default;
261 +
262 +**Explanation: **Non mandatory field, additional explanation;
263 +
264 +According to the running results, there are two types of exits for this rule node: Success and Failure.
265 +
266 +A simple usage example is as follows:
267 +
268 +
269 +
270 +[[image:1730965249482-406.png]]
271 +
272 +
273 +
234 234  == 6.3 transformation ==
235 235  
236 -=== 6.3.1 copy keys ===
276 +=== 6.3.1 copy key-value pairs ===
237 237  
238 -=== 6.3.2 delete keys ===
239 239  
279 +
280 +
281 +
282 +This node is used to copy key values from metadata to data, or to copy key values from data to metadata. The node configuration includes:
283 +
284 +**Name: **required field, indicating the name of the node;
285 +
286 +**Copy from:** a selection option that allows you to choose the direction of copying, from data to metadata or from metadata to data.
287 +
288 +The following input boxes allow you to enter the name of the attribute to be copied, and you can enter multiple names. After entering, press Enter to complete the typing once;
289 +
290 +**Explanation:** Non mandatory field, additional explanation;
291 +
292 +According to the running results, there are two types of exits for this rule node: Success and Failure.
293 +
294 +A simple usage example is as follows:
295 +
296 +
297 +
298 +[[image:1730965445070-151.png]]
299 +
300 +
301 +
302 +=== 6.3.2 delete key-value pairs ===
303 +
304 +
305 +
306 +
307 +
308 +This node is used to delete key values in data or metadata. The node configuration includes:
309 +
310 +**Name: **required field, indicating the name of the node;
311 +
312 +**Delete from: **Select an option that allows you to choose where to delete data, from the data, or from the metadata.
313 +
314 +The following input boxes allow you to enter the name of the attribute to be copied, and you can enter multiple names. After entering, press Enter to complete the typing once;
315 +
316 +**Explanation: **Non mandatory field, additional explanation;
317 +
318 +According to the running results, there are two types of exits for this rule node: Success and Failure.
319 +
320 +A simple usage example is as follows:
321 +
322 +
323 +
324 +[[image:1730965545372-196.png]]
325 +
326 +
327 +
240 240  === 6.3.3 rename keys ===
241 241  
330 +
331 +
332 +
333 +
334 +This node is used to rename attributes in data or metadata. The node configuration includes:
335 +
336 +**Name:** required field, indicating the name of the node;
337 +
338 +**Rename keys in:** a selection option that allows you to choose where to change the data, either from the data or from the metadata.
339 +
340 +The following Key name and New Key name appear in pairs, indicating the original attribute name and the new attribute name;
341 +
342 +**Explanation:** Non mandatory field, additional explanation;
343 +
344 +According to the running results, there are two types of exits for this rule node: Success and Failure.
345 +
346 +A simple usage example is as follows:
347 +
348 +
349 +[[image:1730965632561-703.png]]
350 +
242 242  === 6.3.4 deduplication ===
243 243  
353 +
354 +
355 +
356 +
357 +This node can be used for message deduplication or changing the frequency of sending messages downstream. The configuration content of the node includes:
358 +
359 +**Name: **required field, indicating the name of the node;
360 +
361 +**Interval:** required field, indicating the time interval, that is, how often data is sent downstream;
362 +
363 +**Strategy: **Select option, indicating the strategy for sending messages downstream. The system provides three strategies for developers to choose from, namely First Message, Last Message, and All Messages. The first two strategies are to send the earliest or latest data downstream, and the last strategy is to send a JSON string group of all data. When selecting the latter left strategy, it is also necessary to configure the Output message type and queue. The former is for message type configuration, while the latter is for queue configuration;
364 +
365 +**Explanation:** Non mandatory field, additional explanation;
366 +
367 +According to the running results, there are two types of exits for this rule node: Success and Failure.
368 +
369 +A simple usage example is as follows:
370 +
371 +
372 +
373 +[[image:1730965718765-507.png]]
374 +
375 +
376 +
244 244  === 6.3.5 script ===
245 245  
379 +
380 +
246 246  == 6.4 action ==
247 247  
248 248  === 6.4.1 math function ===
1730964386323-616.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +211.4 KB
Content
1730965249482-406.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +198.7 KB
Content
1730965445070-151.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +198.5 KB
Content
1730965545372-196.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +201.8 KB
Content
1730965632561-703.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +204.7 KB
Content
1730965718765-507.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +198.9 KB
Content