docs(rules_engine_2): document the SLA configuration and Risk Priority asset actions - #15786
Closed
svader0 wants to merge 2 commits into
Closed
docs(rules_engine_2): document the SLA configuration and Risk Priority asset actions#15786svader0 wants to merge 2 commits into
svader0 wants to merge 2 commits into
Conversation
Pairs with the dojo-pro change that lets a rule act on Assets instead of Findings. Adds the four new nodes to Node Reference: two triggers (Manual Asset Run, On Asset Change) and two actions (Assign SLA Configuration, Assign Risk Priority). States plainly that an Asset already recalculating is skipped by the SLA action, not dropped, and that both action pickers need their matching permission or a hand-written rule errors on the run. Extends Building Rules with the Asset scope, the Asset item field list, and the fact that Asset scope defaults to what the owner can edit, not just see, unlike Finding scope. Text only, no screenshot: the sandbox that did this work could not reach a running app to take an honest one.
Asset scope reuses the Assets list filterset, which has no asset-type filter, unlike name, tags, criticality, lifecycle and Organization. States that plainly where Asset scope is introduced, and points at the workaround: scope broadly and add an If / Filter condition on product.asset_type instead.
Collaborator
Author
|
Superseded by #15788. This branch was cut from |
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 two new Rules Engine 2.0 actions: setting an Asset's SLA configuration, and setting its Risk Priority.
Asset support is already documented. This adds the two action nodes to the node reference, and fills two gaps on the Building Rules page:
finding,testorengagementblock, so the new table lists what it does carry.product.asset_type, which compares the type's code rather than its display label.Two behaviours are written down because a run reports them and they are otherwise puzzling:
Pairs with a DefectDojo Pro change that adds the two nodes.
Test Commands
Docs only. Built locally with Hugo (
npm ci && npm run build), no errors, and the new headings and anchors resolve in the built HTML.