docs(rule-engine): add Create Nested Rule Chain and Forward Messages sections#402
Open
ShvaykaD wants to merge 3 commits into
Open
docs(rule-engine): add Create Nested Rule Chain and Forward Messages sections#402ShvaykaD wants to merge 3 commits into
ShvaykaD wants to merge 3 commits into
Conversation
…sub-sections Adds two sub-sections under "## Managing Rule Chains" between "### Set a Rule Chain as Root" and "### Delete a Rule Chain": - Create a Nested Rule Chain — Ctrl+R / right-click extraction workflow that splits selected nodes from one rule chain into a new sub-chain. - Forward Messages to Another Rule Chain — adding a Rule Chain flow node so messages from a parent chain are routed into an existing target chain. Both sub-sections match sibling style (no prose before <Steps>) and link to the Rule Chain flow node reference. The new anchors are referenced from marketplace rule-chain readmes in thingsboard/iot-hub.
vvlladd28
reviewed
May 21, 2026
| selection, **Create nested rule chain** stays disabled. | ||
| 4. Press **Ctrl+R**, or **right-click** the selection and choose **Create nested rule chain**. | ||
| ThingsBoard creates a new rule chain from the selected nodes and replaces them in the | ||
| current chain with a single [**Rule Chain**](https://thingsboard.io/docs/reference/rule-engine/nodes/flow/rule-chain/) node pointing at it. |
Member
There was a problem hiding this comment.
You need to use relative links.
Used auto-generated link:
<DocLink product={props.product} path="reference/rule-engine/nodes/flow/rule-chain/">Rule Chain</DocLink>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds two new sub-sections to the Rule Engine user-guide page under Managing Rule Chains:
Ctrl+R/ right-click extraction workflow that splits selected nodes from one rule chain into a new sub-chain.Both sub-sections sit between Set a Rule Chain as Root and Delete a Rule Chain, and match the existing sibling-section style (no preamble before
<Steps>, link to the Rule Chain flow node reference docs). The Rule Chain node reference page (/docs/reference/rule-engine/nodes/flow/rule-chain/) gets a couple of inbound links.Motivation: several marketplace rule-chain templates in
thingsboard/iot-hubpreviously inlined the sameCtrl+R+ Rule-Chain-node mechanic in their READMEs (~30 lines each), which scaled poorly as more "extend the root chain" templates shipped. The marketplace READMEs now link to these canonical sections instead.How it looks on the UI
Type of change
src/content/_includes/**)Affected products
CE / PE / PaaS — all editions share
rule-engine.mdxvia_includes.Related issues
Checklist