Disclaimer For Inty Customers Moving to Giacom (Excluding US Inty Customers)
Inty has been acquired by Giacom (Affects take place on/ after the 15th of October), therefore if you have been using the Inty integration within HaloPSA you must recreate all mappings in Giacom. First you should clear out the Inty module and then disable the Inty Integration Module.
Then recreate your mappings and import your users and licenses by using the below "Giacom Setup", this will be very similar to the mappings you have set for Inty, it is worthwhile taking note of previous mappings.
To reconfigure your license subscriptions that are synced to recurring invoice lines in Halo (This will not apply if you calculate the recurring invoice line based on "user count on creation" in Halo), you will need to change the recurring invoice lines to be synced to your licenses/ subscriptions, that have now been imported and set to sync, via the Giacom integration, or if you have now synced the users from Giacom instead, the "user count on creation" quantity option on a recurring invoice line, will now be using the user sync from Giacom, which will not require any change to those specific recurring invoice lines (The quantity of users is officially based on the number of users under the specific customer which the recurring invoice relates to).
To change recurring invoice lines on all of your customers, which will now have their quantity automatically calculated based on the license quantity in Giacom. You can import licenses from Giacom, which will appear as a duplicate for each customer, the way you can make the distinguishment between the Inty licenses and Giacom licenses is by looking for the status set on the license. Inty will have a status against the license description, like so:
"Active" being the licenses current status. Giacom licenses will not have a status in their description, therefore when you are choosing the licenses to attach to a recurring invoice line, you can make the distinguishment through the license status.
If you are having any issues with this transition, please contact Halo Support: T +44(0)1449 833 111, Email: support@halopsa.com
Giacom Setup
Within Giacom, an API key can be generated in the Giacom portal by navigating to My Account & Settings > Settings > API
The Integration module in Halo must be enabled for the integration to be active, this can be enabled here Configuration > Integrations > *Search for Giacom* > *Click the plus sign to Enable Giacom*:
Then enter the API Key into the Integration page on Halo:
Clicking the validate button is used to make sure the connection between Halo and Giacom is successful.
The following functionality is available as part of this integration:
- Manually map clients from Giacom to clients in Halo. This can be acheived by using the mappings table on the integration page.
- Import clients from Giacom into Halo, and enable the auto syncing of the customers entity via the Halo Integrator.
- Import subscriptions for any mapped clients, and enable the auto syncing of the subscriptions via the Halo Integrator.
IMPORTANT NOTE: Subscription methods are not cross compatible so swapping from one to the other will create new subscriptions rather than updating old ones
The subscriptionsmanagementreport option on the dropdown is now the option used for pulling through only microsoft subscriptions.
The halo integrator is set up at the bottom of the integration page:
The below option for subscriptions is available as of v2.160
API v2 (v2.184.1+)
Giacom have changed their API so the initial v1 is no longer supported, and a warning will show as this method has now been depreciated. Changing the "Giacom API Version" dropdown to "v2" will use the new API method.
Mappings from v1 will remain when switching versions if the integration is already set up. The first import after switching will match customers by name if there is an existing mapping. If no customers are matched by name, it will create a new mapping. Both of these will be updated to map with the new API upon the first import.
The new API does not allow costPerSeat/totalCost information for licences, and existing subscription IDs will not match if previously imported. This is due to the limitation of the way Giacom have configured their API.
If configuring a new connection for the first time, the mapping setup and import will function the same way as previously detailed in this guide.
