Data transformation for the patch orchestration integration with HCL BigFix

  • Release version: Australia
  • Updated March 12, 2026
  • 5 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Data Transformation for the Patch Orchestration Integration with HCL BigFix

    This integration allows ServiceNow customers to retrieve and transform data from HCL BigFix for effective patch orchestration. The data is processed through various tables and transform maps specific to BigFix collections, fixlets, device fixlets, and actions.

    Show full answer Show less

    Key Features

    • BigFix Collection Import: Imports data on computers and groups into the BigFix Collection Import table. The transform map is critical for processing this data.
    • BigFix Fixlet Import: Facilitates the import of fixlet data into the BigFix Fixlet Import table, with a dedicated transform map to manage the conversion and processing of this information.
    • BigFix Device Fixlet Import: Imports relevant fixlet data associated with computers into the BigFix Device Fixlet Import table, utilizing a specific transform map.
    • BigFix Actions Import: Handles the import of action data into the BigFix Actions Import table, with a corresponding transform map for processing.

    Key Outcomes

    By utilizing these transform maps, ServiceNow customers can effectively manage the lifecycle of imported data, including:

    • Initialization of values for integration processes.
    • Creation and updates of Configuration Items (CIs) based on predefined rules.
    • Tracking of the number of CIs or fixlets created, updated, and ignored upon completion of the import process.

    These capabilities ensure that customers can maintain accurate and up-to-date patch management data, enhancing their overall IT operations.

    Data is retrieved from the Vulnerability Response patch orchestration with HCL BigFix integration, processed through a set of data sources, and transformed in your ServiceNow AI Platform® instance.

    BigFix Collection import

    The data from the imported assets (computers and computer groups) are loaded into the BigFix Collection Import [sn_vul_bigfix_collection_import] table. The BigFix Computer and Computer Groups Import TM (transform map?) is used to transform the imported information.
    Note:
    Changes to this transform map alter how data from the BigFix Collection import is processed.
    To access this transform map, navigate to System Import Sets > Transform Maps and locate BigFix Computer and Computer Groups Import TM. The following table lists the transform map fields by integration.
    Table 1. BigFix Computer and Computer Groups import transform map script timing
    Script Description
    OnStart (when an import set has created transformation). Script used to initialize the values in the scope variable [sn_vul_bigfix] for the integration process. This script is for internal use and should not be modified or deleted.
    onBefore (before an import set has completed transformation).

    Script used to create and update CIs based on CI Lookup Rules and collections as well as relation between them. Based on the results, this script modifies the values in the scope variable [sn_vul_bigfix]. This script is for internal use and should not be modified or deleted.
    onComplete (when an import set has completed transformation). Script that is used to set the number of CIs created, updated, and ignored. This script is for internal use and should not be modified or deleted.

    BigFix Fixlet import

    The data from the imported fixlets are loaded into BigFix Fixlet Import [sn_vul_bigfix_patch_update_import] table.

    BigFix Fixlet Import TM is used to transform the imported information.

    Note:
    Changes to this transform map alter how data from the BigFix Fixlet import is processed.

    To access this transform map, navigate to System Import Sets > Transform Maps and locate the BigFix Fixlet Import TM.

    The following table lists the transform map fields by integration.

    Table 2. BigFix Fixlet import transform map fields
    Source field Target field Description
    u_id article_id Unique Id of a fixlet in a site.
    u_id source_id Unique Id of a fixlet in a site.
    U_site_name Sn_vul_bigfix_site_name Site name in BigFix where the Fixlet relies.
    U_display_name Title Title of the Fixlet.
    [Script] Bulletin_id Source id of the solution.
    [Script] Sn_vul_solution Solution based on the source id.
    U_source bulletin_source Source vendor of the solution.
    [Script] Date_release Release date of the fixlet.
    U_category Update_category Category of the fixlet.
    [Script] Is_highest_supersedence Boolean for if the fixlet is highest supersedence or not.
    [Script] Is_downloaded Boolean of if the fixlet is downloaded or not.
    [Script] Integration_instance Name of the instance from which the fixlet is imported.
    U_source_severity Source_severity Severity of the fixlet.
    U_applicable_count Num_total Total number of devices with missing fixlets.
    [Script] Last_modified Last modified date of fixlet.
    Table 3. BigFix Fixlet import transform map script timing
    Script Description
    OnStart (when an import set has created transformation). Script that is used to initialize the values in the scope variable [sn_vul_bigfix] for the integration process. This script is for internal use and should not be modified or deleted.
    onBefore (before an import set has completed transformation).

    The script that is used to update the values in the scope variable [sn_vul_bigfix]. This script is for internal use and should not be modified or deleted.
    onComplete (when an import set has completed transformation). Script that is used to set the number of fixlets created, updated, and ignored. This script is for internal use and should not be modified or deleted.

    BigFix Device Fixlet Import

    The data from the imported relevent fixlets on computers are loaded into the BigFix Device Fixlet Import [sn_vul_bigfix_device_patch_import] table.

    BigFix Device Fixlet TM is used to transform the imported information.

    Note:
    Changes to this transform map alter how data from the BigFix Device Fixlet import is processed.

    To access this transform map, navigate to System Import Sets > Transform Maps and locate the BigFix Device Fixlet TM.

    The following table lists the transform map fields by integration.

    Table 4. BigFix Device Fixlet transform map script timing
    Script Description
    OnStart (when an import set has created transformation). Script that is used to initialize the values in the scope variable [sn_vul_bigfix] for the integration process. This script is for internal use and should not be modified or deleted.
    onBefore (before an import set has completed transformation).

    Script that is used to Create and Update CIs based on CI Lookup Rules and collections as well as relation between them. Based on the results, this script modifies the values in the scope variable [sn_vul_bigfix]. This script is for internal use and should not be modified or deleted.
    onComplete (when an import set has completed transformation). Script that is used to set the number of CIs created, updated, and ignored. This script is for internal use and should not be modified or deleted.

    BigFix Actions Import

    The data from the imported actions are loaded into the BigFix Actions Import [sn_vul_bigfix_deployment_import] table.

    The BigFix Actions Import TM is used to transform the imported information.

    Note:
    Changes to this transform map alter how data from the BigFix Actions import is processed.

    To access this transform map, navigate to System Import Sets > Transform Maps and locate the BigFix Fixlet Import TM.

    The following table lists the transform map fields by integration.

    Table 5. BigFix Actions Import transform map fields
    Source field Target field Description
    u_id source_id Unique Id of an action.
    U_name name Name of the action
    [Script] Sn_vul_bigfix_discovered_item Reference of the discovered item on which the patch is deployed
    U_status status Status of the action
    [Script] Sn_vul_patch_orch_update Reference of the patch
    U_apply_count Count_success Success count of action.
    U_retry_count retry Retry count of the action.
    [Script] Deployment_time Start time of the action.
    [Script] deadline End time of the action.
    [Script] Source_created Creation time of the action.
    [Script] Integration_instance Name of the instance from which the action is imported.
    Table 6. BigFix Actions import transform map script timing
    Script Description
    OnStart (when an import set has created transformation). Script that is used to initialize the values in the scope variable [sn_vul_bigfix] for the integration process. This script is for internal use and should not be modified or deleted.
    onBefore (before an import set has completed transformation).

    The script that is used to update the values in the scope variable [sn_vul_bigfix]. This script is for internal use and should not be modified or deleted.
    onComplete (when an import set has completed transformation). Script that is used to set the number of actions created, updated, and ignored. This script is for internal use and should not be modified or deleted.