Rule Node

The Rule Node allows users to incorporate logical decision-making within their workflows. Two types of rules can be implemented within a Rule Node:

1. SimpleRule: A SimpleRule evaluates a condition and splits the workflow into two paths: one for when the condition evaluates to true (True Node) and another for when it evaluates to false (False Node).

2. DecisionTable: A DecisionTable allows for more complex decision structures where multiple conditions and outputs can be evaluated and decided in a tabular form.

3. RuleSet: A RuleSet is a collection of SimpleRules and DecisionTables used to filter and process input attributes or datasets based on specified conditions, By combining multiple rules, users can organize and apply filtering criteria effectively, achieving desired outcomes seamlessly

Note: To add a rule node, the rule is not required to be published, it can be in staging as well. However, publishing the rule is compulsory before publishing the workflow, else the workflow will not be published.

Configuration Tabs for Rule Node

1. Input Params: The Input Params section looks different for different types of Nodes. In the respective field of nodes, you can feed in respective constant values(like string or number) or map any outcomes from any previous Nodes using tokens available in the dropdown list or can map directly the global variables using tokens.

   

   Note: Only compatible data-type tokens are available in the dropdown to select.

   In the dropdown, there are three types of tokens you can see:

   • Trigger Nodes: {{ Trigger.attribute_Name }} for example: Trigger.sensor_id

   • Previous Nodes: {{perv_node_Name.attribute_Name}} for example: SetVariable1.output.key_1

   • Global Attributes: {{globalVar.attribute_Name}} for example: globalVar.edtechLeadsBucketD

   By hovering on the specific attribute, you can see the value of that input param. This feature allows you to check the attribute value you're adding to the input param field.

   

   • Run In Loop: This checkbox allows the rule to be processed multiple times in a loop. If checked, an additional field "enter list or custom token" is enabled to input a list or a custom token created during the trigger configuration.

2. Test Result: Once you've entered the input parameters, you can test the node to ensure it functions as expected by just clicking the 'Test' button. You'll see the following sections:

   • Input section: For the rule node, there is an input section that appear to show you the inputs you've given to the rule node.

   • Output Section: In the output section, same as the rule result tab, you can see the execution result in JSON format, along with the Action name and status(if all conditions are met).

     For loops, only the first 10 items are used for testing.

3. Settings: The Settings section allows you to define broader operational parameters and any additional options controlling the rule node's behavior. Like timeouts, retrials, limits, etc. In rule node, you'll see the following actions:

   • Rule Action Toggle:

     The Rule Action Toggle is used to execute actions when all the conditions of a rule are met. This document explains the functionality and configuration of the Rule Action Toggle, including the effects of its toggled states and the "Wait for action(s) to finish" control.

     • By Default (Off): When the Rule Action Toggle is off, only the rules are executed, and their associated actions are not triggered. The JSON response contains a null output for these actions. The user cannot see the action execution results, can only able to see rule outcomes. You can see in the image, that the action is null here. This means, the actions for the rule are not executed.
     • Toggle On: When the Rule Action Toggle is on, the associated actions are executed asynchronously once the rule's conditions are satisfied. Users can simultaneously see the results of these actions and the rule outcome. Actions are executed and their results are included in the JSON response. After toggling on, now you can see the action details, as shown in the image below:

       • Wait for action(s) to finish (Default Off): When the "Wait for action(s) to finish" toggle is off, actions are executed asynchronously in the background. Rules execute independently without waiting for associated actions to be completed. The JSON output contains only the rule outcomes, with action traces visible in the output once they are complete.

       • Wait for action(s) to finish (On): When the "Wait for action(s) to finish" toggle is on, the rule waits for the action to finish its task before proceeding to the next node. This ensures a synchronous flow where actions are completed before moving on to the next node. The results of actions are included in the JSON output along with the rule outcome.

   • Timeout After: Set a timeout duration for the rule. E.g., entering '30' sets the rule to timeout after 30 seconds.

4. Save: After configuring the node, save your node. It's important to test the node before saving the node if you want to use the output of this node in any of the subsequent nodes.

Note: Parameters coming via API cannot be remapped in this section.