Rule Chain Node

Use this node to break a large, monolithic rule chain into smaller, reusable sub-chains. For example, a root chain can dispatch all incoming messages to device-type-specific sub-chains — each handling its own alarm logic, telemetry normalization, or API calls — without duplicating logic across profiles.

The message is forwarded to the input node of the target rule chain. When the target chain finishes processing, control returns to the calling chain via the sub-chain’s Output nodes.

1. The node determines the target rule chain:
   • If Forward message to the originator’s default rule chain is disabled, the configured rule chain is always used.
   • If it is enabled:
     • For Device originators: the default rule chain from the device’s profile is used.
     • For Asset originators: the default rule chain from the asset’s profile is used.
     • For other originator types, or if the default rule chain cannot be determined: the configured rule chain is used as a fallback.
2. The message is forwarded to the input node of the target rule chain.
3. The message proceeds through the target rule chain according to its configuration.
4. Output connections from the target rule chain’s Output nodes determine the final message routing back to the calling chain.

The output connections are determined by the Output nodes in the target rule chain, not by this node itself. The calling chain resumes from those named outputs.

• Use this node to decompose complex logic into reusable sub-chains.
• Combined with Forward to originator’s default rule chain, a single node can dispatch different device types to their profile-specific rule chains without branching.
• The Output node in a sub-chain returns control to the node that called it via the Rule chain node.

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "TbRuleChainInputNodeConfiguration",
  "type": "object",
  "required": ["ruleChainId"],
  "additionalProperties": false,
  "properties": {
    "ruleChainId": {
      "type": "string",
      "minLength": 1,
      "description": "UUID of the target rule chain to forward messages to."
    },
    "forwardMsgToDefaultRuleChain": {
      "type": "boolean",
      "description": "Whether to dynamically resolve the target rule chain based on the originator's default rule chain."
    }
  }
}