HaloPSA

[arnoud]

*** THIS FUNCTIONALITY WILL BE AVAILABLE IN THE NEXT RELEASE ***

NOTE: No changes have been made yet in HaloPSA to support this integration, but they are working on a market place which may make the configuration even easier.

By specifying the HaloPSA ticket number as a reference code for a scan, by default:

1. The device specs are stored as an asset (so that you don't need to enter this data manually);
   
2. The asset is linked to the ticket;
   
3. The scans are logged as internal comments (so you can track the status of the device from check-in to check-out);
   
4. Any changes to the device specs are logged as internal comments (so you can see what has been changed between scans).
   

Please watch the partner video first. @TODO

Requirements:

1. In your HaloPSA account:
   
   1. Create a new API application: Configuration > Integrations > HaloPSA API > View Applications > + New
      
   2. Enter the following: Application Name = 'ScanCircle', Authentication Method = 'Client ID and Secret (Services)', Agent to log in as = select the agent account that will be used to perform the API operations
      
   3. Copy the generated Client Secret (it will only be shown once): optionally click Generate to generate a new value and click Copy
      
   4. On the Permissions tab, check the following options (admin is only temporarily): admin, read:tickets, edit:tickets, read:assets, edit:assets
      
   5. Switch back to the Details tab, save the changes and leave this page open: Details tab > Save
      
2. In your ScanCircle partner environment:
   
   1. Add the HaloPSA integration: Login > Integrations tab > Integration = 'HaloPSA'
      
   2. First fill in the copied Client Secret
      
   3. Then copy the Client ID from the open HaloPSA API application Details tab
      
   4. Fill in the Subdomain with the HaloPSA subdomain
      
   5. Optionally change other fields and the advanced settings, but the defaults usually suffice (for all fields, a description is shown at the righthand side)
      
   6. Click Check to validate the configuration. If the asset type does not yet exist, you will be prompted to have it created automatically. This requires the 'admin' permission and will create the asset type ('ScanCircle Device' or the name specified in the asset parameter) with asset group '? Computing' and the fields: Name, Serial Number, Model, OS Version, Main Board, BIOS, Processor, RAM Memory, Disc Size, Video Card, OS Date, Licence Number, IP Address (fields that do not yet exist will be created)
      
   7. Finally, click OK and don't forget to click Save
      
3. Go back to your HaloPSA account and remove the 'admin' permission: Edit > Permission tab > uncheck 'admin' > Save
   
4. Go back to your ScanCircle partner environment to the Scan widget tab:
   
   1. Specify the name of a URL parameter (e.g. 'ticketno') if you want to set the ticket number in a link, e.g. https://domain.com/scan?ticketno=xyz
      
   2. Specify an input field label (e.g. 'Ticket number') if you want the end-user to see/change/enter the ticket number
      
   3. Optionally specify a category (e.g. 'ticket') if you want this widget to only handle specific HaloPSA reference codes (those containing the text 'ticket:'). Make sure you specify the same category in the 'Integrations' setting. You do not need to specify this if you use a single scan widget and want to allow other reference codes (e.g. email address or phone number) which do not match any ticket number (as failed matches will be forwarded to the next integrations option)
      
   4. Copy the generated HTML code or shortcode to your website
      
5. Day-to-day use:
   
   1. Create a new ticket in HaloPSA: select/enter the end-user, fill in the required fields and click Submit. This will show the ticket number generated in the top left corner and on the tab (e.g. ID:0001234 and 1234);
      
   2. Then perform a ScanCircle scan on the device and enter the generated ticket number as reference code (in this case 1234). This will store the device specs in an asset linked to the ticket and log the scan in the ticket;
      
   3. Now print/email a claim ticket for the customer if required and start fixing the device;
      
   4. Before you return the device, always perform another scan with the ticket number as reference code (logs the end state) and optionally print/email the ScanCircle Scan report (containing the before-and-after state) for the customer;
      
   5. You may allow the customer to periodically scan its device using the ticket number (tip: send them a link containing the ticket number after e.g. 3 months);
      
   6. If you want to update the device specs manually, use the default 'Changes' setting, then update the specs based on the changes in the internal comments.
      

Note: This plugin is as standard provided and maintained by ScanCircle. You do no need to install anything yourself.

If you want to use this plugin, please subscribe to this discussion using the option in the lower left corner of this page so that you will be notified of any updates automatically.