Configure rule chain
Overview
[A]
Start/Stop Chain
Starts or stops the current rule chain.
[D]
Code view
Shows the Code view entered in "Asset Modeling".
[E]
errors
Shows how many errors are present. Clicking on it opens a window that shows the errors in detail.
[F]
Set sequence
After clicking on Set sequence you can determine the order of the blocks by clicking the elements in sequence [L] the Sequence of blocks in which they should be executed.
[G]
Delete
Here the rule chain can be deleted in the app.
[H]
Save
Save your changes.
[I]
Nodes
Nodes are the interfaces to the Eliona systemthat represent various actions or data links.
[J]
Conditions
These can be used to create Conditions between the nodes, including time-based conditions.
[K]
Operations
Performs logical operations (e.g. AND, OR) within the rule chain.
[L]
Linking area
Area in which the Nodes and Connections are placed and linked with each other.
Create a rule chain step by step
Make sure that you are in the configuration of the desired rule chain. -> Open the configuration of an existing rule chain.
Select trigger Decide whether the rule is triggered by events or cycles and configure the asset or the time interval. -> Trigger
Add blocks Drag the required blocks by drag and drop onto the workspace [L]. -> Add blocks
Configure blocks Click the gear icon in the block to make specific settings such as assetattribute or conditions. -> Configure blocks
Connect blocks Connect the blocks by drawing a line from an Output pin to an Input pin (pay attention to matching colors). -> Connect blocks
Check errors Use the error window to locate and fix errors. -> Errors
Set sequence Determine the execution order of the blocks in the “Set order” mode. -> Set sequence
Save changes
Don't forget to save your changes [H]
Trigger
When Trigger [B] you can choose whether the rule chain should be event-based or cycle-based triggered:
Event-based: In this case, in [C] a Asset and its attribute must be selected. Every time new data is written to this attribute, the rule chain is triggered automatically.
Cycle-based: If the rule chain should be triggered cyclically, you can specify in [C] the number of seconds after which the rule chain is executed at regular intervals.
Output nodes are only triggered when the incoming value changes.
Code view
In the Code view you can view the created JSON code of your rule chain and edit it. To activate the Code view it, click on [D]. Once this is activated, the JSON code of the rule chain is displayed, containing the configuration and sequence of the nodes and conditions. You have the option to change the code directly to make specific adjustments instead of using the visual interface.
errors
If you click on Errors [E] a window opens that shows all existing errors in detail.
By clicking the localization icon 
you can jump directly in the linking area [L] to the element that caused the error.
Set sequence
Click on Set sequence [F], to display the execution order of the nodes in the rule chain.
Once this mode is activated, you can click the nodes in the linking area [L] one after another to determine their execution order.
The Order number is automatically incremented and appears at the top right of each node. This lets you see directly in which order the nodes are executed.
Add blocks
To create a rule, the desired blocks can be dragged by drag and drop from the right sidebar to the field [L] and dropped there. Each block represents a specific function that can be used in the rule chain.
Configure block
To configure a block, click the gear icon at the top right of the block. This opens a window in which the individual settings of the block can be adjusted, e.g. the number of input and output pins, the assetto be used, the attributes or the conditions.
Connect blocks
Blocks are connected to each other by drawing a line by drag and drop from an output pin to an input pin of another block. Make sure that the output and input pins have the same color:
Red stands for numerical values.
Blue stands for boolean values (true/false).
Only pins with the same color can be connected to each other to ensure correct data transfer.
Dynamic pin expansion
If all existing pins of a block are already occupied, a new pin appears when hovering over an occupied pin. This can be used to create a connection to another input. As soon as the connection has been created, the new pin is automatically activated and added permanently.
Visualization of values after execution
After a rule chain has been saved and executed at least once, the current values at the input and output pins of the blocks are displayed in purple. These values show which data is flowing through the rule chain and allow direct verification of the logic.
The displayed values are updated each time it is executed again and help with troubleshooting and optimizing the rule chain.
The blocks
Blocks are the basic elements of a rule chain. Each block performs a specific function, e.g. retrieving data, setting conditions, or executing actions such as sending alarms or emails.
Blocks can be connected to each other to control complex processes. The data flow is managed via input and output pins, and only compatible pins can be connected to each other.
In the configuration of a block, a Note can also be stored. This is used to document important information or explanations directly in the block and makes the rule chain easier to understand.
Nodes
Retrieve data
Function: This block reads heap data from a specific asset and its attribute.
Configurable settings:
Output pins: You can configure multiple output pins to send the data to various other blocks.
Asset and attribute: The specific asset and the associated attribute whose data is to be queried.
Write data
Function: Sends data to a defined asset and writes the specified value to a particular attribute.
Configurable settings:
Input pins:
Trigger pin: Triggers writing the value.
Value pin (optional): If this pin is used, the value is taken from the connected source. Otherwise, the value can be entered manually.
Asset, attribute: Selection of the asset and associated attribute into which the data is to be written.
Value: If no value pin is used, a fixed value can be defined here.
Alarm
Function: Triggers an alarm for a specific asset when certain conditions are met.
Configurable settings:
asset: The asset, for which the alarm is triggered.
Priority: The urgency of the alarm (e.g. high, medium, low).
Acknowledgement: It can be specified whether the alarm must be acknowledged manually.
Ticket
Function: Creates a ticket for tracking issues or tasks associated with a asset associated with a
Configurable settings:
Asset: Selection of the asset to which the ticket refers.
Priority: Definition of the urgency of the ticket (e.g. low, medium, high).
Assigned person: Selection of the recipient responsible for handling the ticket.
Reason: Selection of the reason for the ticket from predefined categories.
Title: Enter a meaningful title for the ticket.
Description: Detailed description of the problem or task.
Send email
Function: Sends an email notification to a specific person or group.
Configurable settings:
Subject: The subject of the email.
To: The email address(es) of the recipient.
Text: The actual content of the email.
Script
Function: The Script block enables the execution of a script from the -> Script Engine within the rule chain. Execution is controlled by a boolean input value.
Configurable settings:
Script: Selection of the script to be executed from the Script Engine.
IMPORTANT: Script must be set to "Event triggered" in the grid
Conditions
Condition
Function: Represents a condition that is checked before the rule chain is executed further and outputs the boolean result of the check. This can perform numerical comparisons between inputs.
Configurable settings:
Number of input and output pins: You can configure the number of pins to link multiple conditions.
Comparison operations: Choose from “equal”, “greater than”, “less than”, “greater than or equal”, “less than or equal”.
Value: If only one input pin is used, a fixed value can be entered for comparison. If multiple input pins are used, the inputs are compared with each other.
Time
Function: Inserts delays into the rule chain in order to execute events with a delay or cancel them.
Configurable settings:
Number of input and output pins: Determine how many delays can be set up.
Condition: TON (on-delay) and TOFF (off-delay).
Delay time: The delay in seconds to be applied.
Schedule
Function: The Schedule block enables a rule chain to be triggered based on a defined schedule. Within the specified time window, the block outputs a "true" signal, outside this period the output remains "false".
Configurable settings:
Schedule type: Selection of the schedule, e.g.
Time Schedule – control based on a defined time.
Days Schedule – control based on specific days of the week.
Begin time: Start time of the active period (hh:mm) (only for Time Schedule).
End time: End time of the active period (hh:mm) (only for Time Schedule).
Active days: Selection of the days of the week on which the rule should be active (only for Days Schedule).
Operation
Or
Function: Checks whether one of the input conditions is true or false and outputs the boolean value of this check.
Configurable settings:
Number of input and output pins: Determine the number of conditions to be checked.
And
Function: Checks whether all input conditions are true and outputs the boolean value of this check.
Configurable settings:
Number of input and output pins: Determine the number of conditions that must be true at the same time.
Arithmetic
Function: Performs mathematical calculations with the input parameters to generate a new value.
Configurable settings:
Number of input pins: Determine how many values go into the calculation.
Operation: Choose between addition, subtraction, multiplication, and division.
Value: An optional fixed value included in the calculation.
Other
Note
Function: The Note block serves as a purely informational element within the rule chain. It allows notes or comments to be added to improve the clarity of the rule chain.
Configurable settings:
Text field: Enter any note or description.
Was this helpful?