---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/impact

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Scan Engine Developer dashboard

# Scan Engine Developer dashboard {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The Developer dashboard includes trend charts and the following overview modules.
{#scan-engine-development-team-dashboard__table_qcw_zml_fhc__entry__2}

| Information module | Description |
|-|-|
| My open findings by impact to instance | * A developer's total findings grouped by impact to instance. * Impacts to instance range from 1 (minor impact) to 10 (significant impact). * Select a bar in the chart to view the findings in a new browser tab. {#scan-engine-development-team-dashboard__ul_rcw_zml_fhc} |
| My technical debt by category | * The estimated amount of development time required to resolve all findings within each category. * The value in the center is the combined total technical debt displayed in either time or count for all categories. {#scan-engine-development-team-dashboard__ul_ucw_zml_fhc} |
[Tabelle : 1. Developer dashboard overview]

{#scan-engine-development-team-dashboard__table_qcw_zml_fhc}

## Developer trend charts {#scan-engine-development-team-dashboard__section_vqx_2nl_fhc}

The Developer dashboard includes the following trend charts.
{#scan-engine-development-team-dashboard__table_wyf_jnl_fhc__entry__2}

| Chart | Description |
|-|-|
| My findings by priority | A developer's assigned findings listed by highest impact to instance and lowest time to resolve. Address these findings to achieve the highest impact in return for the lowest effort. |
| Policy prioritized findings | * A developer's findings that have a Priority status within a policy. * Findings listed here were last updated by the developer. {#scan-engine-development-team-dashboard__ul_xyf_jnl_fhc} |
| My open findings | The current open findings that the Scan Engine has identified in a developer's code. |
| My exceptions | The current exceptions a developer has submitted that require a Team Lead's approval. |
| My findings by file type | * The heatmap of your findings by file type. This lets you quickly see which development areas need the most attention. * Select a number in any cell to see the full list of findings for that file type/category. {#scan-engine-development-team-dashboard__ul_zyf_jnl_fhc} |
| My resolved findings | Findings that have been resolved in a developer's code. |
[Tabelle : 2. Developer dashboard trend charts]

{#scan-engine-development-team-dashboard__table_wyf_jnl_fhc}

## Developer dashboard data sources {#scan-engine-development-team-dashboard__section_v5l_tcp_nhc}

The following tables show the data source for each overview module and trend chart in the Developer dashboard.  
Hinweis:  
All components require either the impact.admin or impact.developer role to use.
{#scan-engine-development-team-dashboard__table_htn_ycp_nhc__entry__2}

| Component | Data Source |
|-|-|
| My open findings by impact to instance | sn_se_summary_scan_detail |
| My technical debt by category | sn_se_summary_scan_detail |
[Tabelle : 3. Developer overview data sources]

{#scan-engine-development-team-dashboard__table_htn_ycp_nhc} {#scan-engine-development-team-dashboard__table_pbg_zcp_nhc__entry__2}

| Component | Data Source |
|-|-|
| My open findings by priority | sn_se_finding |
| Policy prioritized findings | sn_se_finding |
| My open findings | sn_se_summary_scan_detail |
| My exceptions | sn_se_exception_reason |
| My findings by file type | sn_se_summary_scan_detail |
| My resolved findings | sn_se_resolved_finding_history |
[Tabelle : 4. Developer trend chart data sources]

{#scan-engine-development-team-dashboard__table_pbg_zcp_nhc}