Skip to main content

Asset mappings

The Asset mappings page allows you to associate HaloPSA assets with their corresponding Bitdefender GravityZone endpoints. This ensures that service desk tickets generated by the integration explicitly reference the affected HaloPSA asset, improving visibility and traceability for your support teams.

Note

The HaloPSA client must have a valid client mapping established with a GravityZone company, and the assets must exist within a defined asset group in HaloPSA.

Loading assets

To create a asset mappings, follow these steps:

  1. Select a HaloPSA client.

    Only clients with an existing client mapping will be available.

  2. Select the HaloPSA asset group containing the assets you want to map.

  3. (Optional) Filter by asset type.

    You can narrow down the list by selecting one or more asset types.

  4. Click Load assets.

    The available assets from the selected group will be displayed in a table with the following details:

    • Asset number

    • HaloPSA site

    • GravityZone endpoint (default = N/A)

    • Matched status (default = No)

Smart match

The Smart match feature allows the integration to automatically suggest asset mappings between HaloPSA assets and GravityZone endpoints based on selected matching conditions. 

To configure and run Smart Match:

  1. Select matching conditions:

    1. From the HaloPSA condition drop-down list, choose the asset field or custom field to be used in the comparison.

    2. From the GravityZone property drop-down list, select the corresponding endpoint property:

      1. Endpoint label

      2. IP address

      3. MAC address

      4. FQDN

      5. SSID

  2. Define the match mode:

    1. Choose how the comparison should be performed from the Match mode drop-down list:

      1. GravityZone property contains HaloPSA field

      2. HaloPSA field contains GravityZone property

      3. Exact match

    2. Optionally, enable Case sensitive match mode to perform case-sensitive comparisons.

  3. Run Smart Match:

    1. Select the Assets you want to include in the Smart Match process.

    2. Click Start smart match to begin.

HaloPSA_asset_mappings_smart_match1_p_1439620_en.png

After the Smart Match process completes, the suggested GravityZone endpoints will appear in the GravityZone endpoint column, along with the Match Status.

HaloPSA_asset_mappings_smart_match2_p_1439620_en.png

The possible match statuses are:

  1. Smart match – An exact GravityZone endpoint was found for the selected criteria. The endpoint is automatically added in the GravityZone endpoint column.

  2. No match – No GravityZone endpoints were found for the selected criteria.

  3. Duplicate match – Two GravityZone endpoints matched the selected criteria. Both endpoints can be viewed by hovering over the field.

  4. Multiple match – More than two GravityZone endpoints matched the selected criteria. All matched endpoints can be viewed by hovering over the field.

Caution

To confirm and save the proposed mappings or any changes to the Asset Mappings, click Save Changes. If an already saved mapping is selected for Smart Match, the proposed GravityZone endpoints will be re-evaluated based on the newly defined criteria.

HaloPSA_asset_mappings_smart_match3_p_1439620_en.png
Manually mapping assets

To manually map an asset, follow these steps:

  1. Click the Edit icon on the line of the desired asset.

  2. From the drop-down list, select an available GravityZone endpoint.

  3. Click Save to confirm the selection.

  4. Repeat the process for any additional assets that require mapping.

  5. Once all mappings are complete, click Save changes.

    Note

    Until you click Save changes, mapped items will display a Pending status.

Managing existing mappings

Missing assets 

If an asset’s corresponding GravityZone endpoint is no longer available, its matched status will automatically change to Missing.

Removing a mapping 

To delete an existing mapping:

  1. Edit the asset line.

  2. Select Remove mapping, then Save.

  3. Click Save changes.

In this section: