docs(rules_engine_2): document asset support - #15767
Open
blakeaowens wants to merge 1 commit into
Open
Conversation
Rules Engine 2.0 gained Asset (Product) rules: an On Asset Event trigger, a Sweep Over choice on the schedule and manual triggers, an Assets node section (set a field, set organization, add and remove tags, set parent), and asset-aware notifications. This documents what a rule works on, the new trigger and nodes, asset runs and drilldowns, deliveries from asset rules, and the now entity-neutral per-item send ceiling wording. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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
Documents Asset (Product) support in Rules Engine 2.0, shipping in the matching Pro release on this line.
building_rules.md: a new "What a rule works on" section (the trigger decides whether a rule works on Findings or Assets, the editor dims nodes that do not apply, and the schedule and manual triggers carry a Sweep Over setting), plus the trigger list and the scope wording updated to cover both kinds.node_reference.md: node count 25 to 31 in five categories, an On Asset Event trigger entry, Sweep Over rows on the schedule and manual trigger tables, a new Assets section documenting the five asset nodes (Set a Field, Set Organization, Add Tags, Remove Tags, Set Parent), and an Egress intro note on which egress nodes work in Asset rules and which stay Finding-only.runs.md: an Asset runs section (drilldowns into changed and left-alone Assets, the left-alone caveat, the asset provenance endpoint).deliveries.md: a section on deliveries from Asset rules (row visibility follows the Asset, digest and webhook payload shape).configuration.mdanddeliveries.md: the per-item send ceiling wording follows the UI label change from "One Message per Finding" to "One Message per Item"; the ceiling section keeps its heading and anchor.about.md: one paragraph on asset automation.English pages only; translations follow the repo's translation workflow.
🤖 Generated with Claude Code