Integrating IT Glue with Halo will allow syncing of Organisations and flexible Assets on a scheduled basis, with an option to enable 2 way syncing of Organisations.
First head to Configuraion>Integrations & enable the IT Glue module:
You'll find that within this module, you are first required to provide details of your IT Glue URL & API Key. Details on onbtaining an IT Glue API key can be found here.
Once you have entered your IT Glue details, click the 'Test Connection' button to ensure Halo can successfully communicate with IT Glue.
The first step toward configuring the IT Glue integration is to import IT Glue Organisations/Locations into Halo as Customers/Sites.
The table you see in this section is used to establish mappings between IT Glue Organisations/Locations and existing Halo Customers/Sites. This table is primarily used for situations where the name of an IT Glue Organisation does not exactly match that of an existing customer in Halo i.e: Tony's Tyres in Halo may be called Tony's Tyres LTD in IT Glue.
Mapped customers (records added to this table) will not have their names in Halo changed upon importing. Non-mapped customers will match based on name. IT Glue Organisations without a location will not be imported into Halo.
Below this mapping table, you have a 'Customer Type' selection. You can use this to allocate a specific customer type to customers created via IT Glue imports, or you can use the IT Glue Organisation Type to set the customer type.
NB: Customer Types are amended via heading to Configuration>Users>Customer Types
You can then select the IT Glue Organisation statuses to consider as 'Active'. IT Glue Organisations with these statuses will be imported into Halo as active customers, while all other Organisations that are imported will be imported into Halo as inactive customers.
Flexible Asset Imports
Once you have imported your Organisations from IT Glue into Halo, you are ready to move on to the configuration of flexible asset imports.
Flexible assets of a certain type are imported into Halo via establishing a mapping between the IT Glue flexible asset type & the Halo Asset type. This is achieved via adding to the 'mapping table' present in the Flexible Assets section of the IT Glue configuration screen.
Once you have added an IT Glue flexible asset type - Halo asset type mapping, you can add field mappings which will allow you to determine what information you would like to import from IT Glue.
Below this table, you will find an option to select a 'Default Site'. This is the Site in Halo that flexible assets will be imported into if their IT Glue location has not been previously imported.
You can also set an 'Asset Matching Field' - this field is used to match imported flexible assets to existing assets in Halo. By default, the IT Glue ID will always be checked first.
The Halo Integrator
The importing of Organisations/Locations & flexible assets can be configured to run on a scheduled basis via the Halo Integrator. To enable this, simply check the 'Enable the Halo Integrator for the IT Glue Integration' checkbox:
You can then select the entity/entities you would like to import.
NB: Only entities that have been updated in IT Glue since the previous import will be retrieved.
Syncing to IT Glue
2-way syncing can be enabled for Organisations/Locations via selecting the 'Enable syncing to IT Glue' checkbox:
This will then attempt to create/update Organisations and Locations whenever respective Customers/Sites are updated in Halo.
Here, you can select the Organisation status to be used in IT Glue for when a customer is made active in Halo & can also set an IT Glue Organisation status for when a customer in Halo is made inactive.
The ability to sync name changes from Halo to IT Glue can also be enabled.