Repository navigation
docs(pro): document the Locations export field and finding Locations report column - #16369
Open
paulOsinski wants to merge 1 commit into
Open
paulOsinski wants to merge 1 commit into
paulOsinski wants to merge 1 commit into
Conversation
…eport column The findings CSV/Excel export dialog and the report builder's finding entity gained a Locations field that names each finding's affected systems (Pro change), replacing the legacy Endpoints field on Locations-enabled instances. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This branch has not been deployed
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 a Pro feature change: the findings CSV/Excel export dialog and the report builder's Finding entity gained a Locations field that names each finding's affected systems. On instances with the Locations feature enabled, this replaces the legacy Endpoints field, which stops being populated once imports write Location records instead of Endpoint records. Pairs with the Pro pull request on the same release line.
What changed
docs/content/asset_modelling/engagements_tests/PRO__findings.md— the Export Findings section now describes the Locations field (and notes the legacy Endpoints field on non-Locations instances), and that the Locations column of a report template's Findings table carries the same values.docs/content/metrics_reports/reports/PRO__report_builder.md— the Finding entity's reportable fields now document the Locations column alongside the existing Location Count field.Text-only, as required for OSS PR descriptions. The Pro PR carries the screenshots.
🤖 Generated with Claude Code