This article describes the deep linking feature of BrightGauge. Deep linking enables you to turn certain fields into hyperlinks that link directly to a datasource. For example, you can link Ticket Numbers directly to ConnectWise Manage:

As you can see, deep linking is showing in Drilldown, but it also works for List Gauges and Table Gauges.

Note: Deep Linking will show everywhere except on Client Reports. We have kept it disabled for any and all client reports.

 

ConnectWise Manage (On-Premise)

For ConnectWise Manag on-premise users, you will have to go to your datasource and enter these three fields. Once that is complete, any gauges being powered off datasets with the below five fields will be hyperlinked back to your ConnectWise web portal.

  1. ticket_number
  2. config_recid
  3. opportunity_recid
  4. so_activity_recid
  5. Time_RecID

Let us know if you have any feedback! 

 

ConnectWise Manage (Cloud)

For hosted ConnectWise Manage users, you will have to go to your datasource settings page and select just one dropdown field. Once that is complete, for any gauges being powered off datasets with the below five fields will be hyperlinked back to your ConnectWise web portal. Please note that default datasets for CW API contain an "id" field and a "ticket_number" field. The links will appear in Drilldown and List Gauges!

  1. ticket_number
  2. config_id
  3. opportunity_recid
  4. so_activity_recid
  5. Time_RecID

Let us know if you have any feedback!

 

ConnectWise Automate (On-Premise)

For ConnectWise Automate on-premise, you will have to go to your Datasource and enter your URL. Once that is complete, any gauges being powered off datasets with the following field will be hyperlinked back to your ConnectWise Automate web portal.

  • computer_id

Screen_Shot_2015-11-05_at_3.57.09_PM.png

ConnectWise Automate (Cloud)

For hosted ConnectWise Automate, deep linking will automatically be configured using your company URL that is required for the general Datasource configuration. Any gauges being powered off datasets with the following field will be hyperlinked back to your ConnectWise Automate web portal.

  • computer_id

ConnectWise_Automate_2021-05-05_at_1.52.52_PM.jpg

Autotask

For Autotask users, it's simply entering in the Autotask URL you use to access Autotask. For example, see below.

Once you get that updated in your datasources page, the field "ticket_id" will be hyperlinked in any drilldown or list gauge. Please note, this ticket id field is different from the ticket_number field.

Datto REST

For Datto users, this feature works straight out of the box. This means that once the datasource is connected, the following field will be hyperlinked in any drilldown or list gauge:

  • device_serial_number

 

Kaseya BMS (Vorex)

For Kaseya BMS users, this feature works straight out of the box as you already use your BMS URL to connect the datasource. This means that once the datasource is connected, the available fields become hyperlinks in drilldown and list gauges. For BMS, the fields are:

  • ticket_id
  • account_id
  • hardware_asset_id
  • software_asset_id
  • opportunity_id
  • activity_id
  • project_id
  • invoice_id
  • contract_id

 

ServiceNow

For ServiceNow users, deep linking works straight out of the box. Once the datasource is connected, the available fields become hyperlinks in drilldown and list gauges. For ServiceNow, the deep linked fields are:

  • change_request_id
  • company_id
  • contract_sla_id
  • incident_id
  • problem_id
  • service_catalog_request_item_id
  • service_catalog_request_id
  • survey_response_id
  • user_id
  • task_id
  • task_sla_id
  • task_time_entry_id

 

ZenDesk

For ZenDesk users, this feature works straight out of the box as you already enter their ZenDesk URL to connect the datasource. This means that once the datasource is connected, the field "ticket_number" will be hyperlinked in any drilldown or list gauge. Please note, this "ticket_number" field is different from the "id" field.

Was this article helpful?
3 out of 6 found this helpful

Comments

0 comments