> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/whats-new/september-2026/sap-coverage-analysis-full-impact-view.md).
# SAP Coverage Analysis: Full Impact View
The SAP Coverage Analysis table now shows all impacted executables and objects by default, giving full visibility into what was covered and what wasn't, not just the gaps.
### What's New
* **Full impact scope as the default view.** The Coverage Analysis table now surfaces every executable and object touched by a change, regardless of coverage status. Previously, covered objects were hidden from the table, and if an executable was fully covered, the executable itself was hidden too; the same applied to app areas where all changed executables were 100% covered. That gap-only view is now opt-in.
* **Per-object coverage status at a glance.** Each object row now displays a clear **Covered / Uncovered** indicator in the Change Coverage column, so teams can immediately see what was exercised and what was missed.
* **"Uncovered Objects Only" toggle for gap-focused workflows.** Users who prefer the previous behavior can activate this toggle to filter the table down to only uncovered objects. Executables with no remaining uncovered objects, and app areas with no remaining executables, are automatically hidden.
### Why It Matters
Previously, the Coverage Analysis table only surfaced executables and objects that had uncovered changes - fully covered executables, and even entire app areas, were automatically hidden from view. While the overall coverage percentage was visible, there was no way to see the detail behind it: which specific objects were covered, which executables were fully exercised, or which app areas had complete coverage.
The new default view closes that gap. Teams can now inspect the full change scope, covered and uncovered, without needing to look elsewhere to confirm what was tested. The "Uncovered Objects Only" toggle preserves the focused, gap-first workflow for teams that prefer it, while the filter-aware export ensures either view can be shared or archived as-is.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sealights.io/knowledgebase/whats-new/september-2026/sap-coverage-analysis-full-impact-view.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
