The logic nodes within process control include Timer, Branch Judgement, and Multi-path Judgement. This topic describes the method to configure process control nodes in the blueprint editor.
Timer
The Timer node supports delayed timing, fixed-point timing, loop delay timing, and loop cycle timing.
Scenarios: The Timer is suitable for scenarios that require timing. When the time count reaches the time point set in the configuration item, the timer node throws the When Timing Ends event, outputs the upstream node's output result, and triggers subsequent actions.
Add a Timer node to the canvas to view the events/actions supported by the Timer node and configuration parameters. For the addition method, see Using logic nodes.
Table 1. Event/action parameter description
Event/Action | Description |
Start Timing | Start the timer. |
Stop Timing | Stop the timer. The next time Start Timing is triggered, timing will restart. Generally used in loop timing. |
When Reaching The Timing Point | Throw an event when reaching the timing point, triggering the descendant node to execute an action. In loop timing, this event will be thrown repeatedly. |
Table 2. Configuration item description
The table only provides parameter descriptions in Other Configurations. For other parameter configurations, see Common parameter description.
Parameter | Description |
Timing Method | Supports two methods: Delayed Timing and Fixed-point Timing. |
Loop Timing | Whether repeated timing is needed. When the Timing Method is Fixed-point Timing, after enabling Loop Timing, a Fixed-point Cycle will be configured, allowing custom settings for the start time and interval time within the Fixed-point Cycle. |
Delay Time | Countdown in seconds. Only effective when the Timing Method is Delayed Timing. |
Fixed-point Time | Countdown in seconds. When reaching a specific standard time point, an event is thrown. Only effective when the Timing Method is Fixed-point Timing and Loop Timing is disabled. |
Output Result: Does not change the upstream node's output result. When the timer is triggered, it outputs the upstream node's output result.
Branch judgement
The Branch Judgement node is an If-Else conditional judgement node. When the set condition is met, it throws the Satisfied event. If the set condition is not met, it throws the Not Satisfied event.
Scenarios: For example, in a scenario where the visibility effect of two layers is triggered based on the switch status. The Branch Judgement node can be used to determine the current switch status. If it is in the open state, layer A is displayed and layer B is hidden. If it is in the closed state, layer B is displayed and layer A is hidden.
Add a Branch Judgement node to the canvas to view the events/actions supported by the Branch Judgement node and configuration parameters. For the addition method, see Using logic nodes.
Table 3. Event/action parameter description
Event/Action | Description |
Judgement | Input the upstream node's output result for conditional judgement. |
Satisfied | The upstream node's output result meets the set condition. |
Not Satisfied | The upstream node's output result does not meet the set condition. |
Table 4. Configuration item description
The table only provides parameter descriptions in Other Configurations. For other parameter configurations, see Common parameter description.
Parameter | Description |
Judgement Type |
|
Processing Method | Write the processing method using JavaScript, returning a BOOLEAN type result. If the result is TRUE, the execution condition of the processing method is satisfied. If the result is FALSE, the execution condition of the processing method is not satisfied. Processing methods can be added cumulatively. Example: When clicking the Tab list, if the label ID (i.e., id in the code) equals 1, the common title is in the display state. If the label ID is not equal to 1, the common title is in the hidden state. The code for the processing method is as follows. |
Output Result: Does not change the upstream node's output result. When branch judgement is triggered, it outputs the upstream node's output result that meets the condition.
Multi-path judgement
The Multi-path Judgement node is a Case-When node. By judging the upstream node's output result, it triggers the first descendant node that meets the condition to execute the corresponding action.
Scenarios: For example, setting the color of map scatter points based on the current input value in the Number Input Box. The Multi-path Judgement node can be used to determine which range the current input value falls into, thereby triggering the setting of scatter point colors. For example, in the configuration item, if the value is greater than 100, it is red. Between 50 and 100, it is yellow. Less than 50, it is blue.
Add a Multi-path Judgement node to the canvas to view the events/actions supported by the Multi-path Judgement node and configuration parameters. For the addition method, see Using logic nodes.
Table 5. Event/action parameter description
Event/Action | Description |
Judgement | Input the upstream node's output result for multi-path judgement. |
case-N | Processing method. If the current processing method is satisfied, the event is thrown. Multiple processing methods can be added in the configuration panel. After adding, the Multi-path Judgement node displays the processing methods you added. Different processing methods can connect to different descendant nodes to achieve multi-path judgement. |
Satisfy Default Condition | If the default condition is satisfied, the event is thrown. |
Table 6. Configuration item description
The table only provides parameter descriptions in Other Configurations. For other parameter configurations, see Common parameter description.
Parameter | Description |
Processing Method | Write the processing method using JavaScript, returning a BOOLEAN type result. Processing methods can be added cumulatively.
Example: When clicking the Tab list, if the label ID (i.e., id in the code) equals 1, the common title is in the display state. If the label ID equals 2, the common title is in the hidden state. If the label ID is not equal to 1 or 2, the common title is in the display state (i.e., executing the event corresponding to the default condition). The code for the processing method is as follows. |
Output Result: Does not change the upstream node's output result. When multi-path judgement is triggered, it outputs the upstream node's output result that meets the condition.