Wiki source code of Basic configuration of rule chains
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | = 1.About rule chains = | ||
2 | |||
3 | The system provides a rule chain library for developers to configure message transformation, filtering, computation, and transmission on their own. | ||
4 | |||
5 | = 2.Rule chain creation = | ||
6 | |||
7 | The system provides a default root rule chain that supports user use. No changes are made on the root rule chain, but the root rule chain is exported and re imported, and then modified and configured in the newly imported rule chain. | ||
8 | |||
9 | Firstly, follow the steps below to export the root rule chain. After clicking on export, the system will automatically download it, and the exported file will be in JSON format. | ||
10 | |||
11 | [[image:1730343544790-113.png||height="711" width="1364"]] | ||
12 | |||
13 | Re import the exported configuration into the system. After clicking on import, the system will directly jump to the configuration page of the newly imported rule chain. Simply click on the "Apply Change" button in the bottom right corner. | ||
14 | |||
15 | Re exit to the rule chain library menu to see the newly imported rule chain library configuration. | ||
16 | |||
17 | [[image:1730344152898-509.png||height="711" width="1363"]]4 | ||
18 | |||
19 | |||
20 | [[image:1730344348542-260.png||height="701" width="1361"]] | ||
21 | |||
22 | = 3.Rule chain modification = | ||
23 | |||
24 | Follow the steps below to modify the basic information of the rule chain. You can rename the rule chain imported in the previous section. | ||
25 | |||
26 | [[image:1730344632740-435.png||height="702" width="1362"]] | ||
27 | |||
28 | [[image:1730345137320-999.png||height="705" width="1366"]] | ||
29 | |||
30 | [[image:1730345353615-959.png||height="706" width="1369"]] | ||
31 | |||
32 | = 4.Rule chain deletion = | ||
33 | |||
34 | You can delete a newly created rule chain by following the following steps. | ||
35 | |||
36 | note: the default root rule chain provided by the system cannot be deleted. | ||
37 | |||
38 | [[image:1730346321550-495.png||height="705" width="1371"]] | ||
39 | |||
40 | = 5.Rule chain configuration = | ||
41 | |||
42 | If you need to configure the rule chain, you need to follow the following steps to enter the configuration page of the rule chain. | ||
43 | |||
44 | [[image:1730346571913-889.png||height="714" width="1373"]] | ||
45 | |||
46 | [[image:1730346890962-926.png||height="711" width="1376"]] | ||
47 | |||
48 | [[image:1730347084731-765.png||height="717" width="1377"]] | ||
49 | |||
50 | [[image:1730347231071-931.png||height="712" width="1377"]] | ||
51 | |||
52 | Next, we will explain the configuration of rule nodes that may be commonly used in different classes to manipulate data. As the default device configuration was applied in the creation of the previous device , | ||
53 | |||
54 | the rule chain used in the default device configuration is the Root Rule Chain. Therefore, the following demonstrations are all configurations made in the Root Rule Chain. | ||
55 | |||
56 | = 6.About Nodes = | ||
57 | |||
58 | == 6.1 filter == | ||
59 | |||
60 | === 6.1.1 check fidles presence === | ||
61 | |||
62 | === 6.1.2 script === | ||
63 | |||
64 | === 6.1.3 switch === | ||
65 | |||
66 | == 6.2 properties == | ||
67 | |||
68 | === 6.2.1 calculate delta === | ||
69 | |||
70 | === 6.2.2 customer attributes === | ||
71 | |||
72 | === 6.2.3 customer details === | ||
73 | |||
74 | === 6.2.4 tenant attributes === | ||
75 | |||
76 | === 6.2.5 tenant details === | ||
77 | |||
78 | === 6.2.6 fetch device credentials === | ||
79 | |||
80 | == 6.3 transformation == | ||
81 | |||
82 | === 6.3.1 copy keys === | ||
83 | |||
84 | === 6.3.2 delete keys === | ||
85 | |||
86 | === 6.3.3 rename keys === | ||
87 | |||
88 | === 6.3.4 deduplication === | ||
89 | |||
90 | === 6.3.5 script === | ||
91 | |||
92 | == 6.4 action == | ||
93 | |||
94 | === 6.4.1 math function === | ||
95 | |||
96 | === 6.4.2 create alarm && clear alarm === | ||
97 | |||
98 | === 6.4.3 delay === | ||
99 | |||
100 | === 6.4.4 generator === | ||
101 | |||
102 | === 6.4.5 log === | ||
103 | |||
104 | == 6.5 external == | ||
105 | |||
106 | === 6.5.1 kafka === | ||
107 | |||
108 | === 6.5.2 mqtt === | ||
109 | |||
110 | === 6.5.3 rest api call === |