---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# About custom report processor scripts

# About custom report processor scripts {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

On the Vulnerability Integration form, the Report processor is a reference to a script
include that extends the VulnerabilityReportProcessorBase script include. The functionality
contained in this script is called by the VulnerabilityIntegrationController and defines the means
by which the data returned by the integration script are processed.  
Each subclass of VulnerabilityReportProcessorBase has access to contextual information about the calling process. That information is available through the following member variables:

* integrationGr --- a GlideRecord of the Vulnerability Integration record that requested the integration to run.
* integrationProcessGr --- GlideRecord of the Vulnerability Process that provides contextual information for the current process of an integration.
{#c_AboutCustomRptProcScript__ul_wxj_ds3_f5}

The script include must provide an implementation for the `processReport()`
method. The object passed to processReport() is the object returned by retrieveData, and as such,
is a simple object with properties for content, contentType, and extension. The actual logic in
processReport() is implementation-specific and dependent of the report data provided.  
Here is a screen shot of the VulnerabilityReportProcessorBase.processReport(): Figure 1. Custom report processor script