<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><p><strong>In this guide we will cover:</strong></p><p data-pasted="true"><strong>- What is the Assetbots Integration?</strong></p><p><strong>- Connecting to Assetbots</strong></p><p><strong>- Sites</strong></p><p><strong>- Match Assets to Users</strong></p><p><strong>- Asset Imports</strong></p><p><strong>- Import Assets and Sites Automatically</strong></p><p><br></p><p><br></p><p><em>This integration is available from v2.234+</em></p><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">What is the Assetbots Integration?</span></strong></p><p>The Assetbots integration allows you to import sites and assets from Assetbots into Halo. The Halo integrator can be used to have sites and assets import automatically on a scheduled basis too. This integration supports a one way sync only. </p><p><br></p><p><strong><span style="font-size: 14pt;">Connecting to Assetbots</span></strong></p><p data-pasted="true">First head to Configuration > Integrations and enable the Assetbots module using the "+" icon.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI1MzMyODljLTZhMTktNDdhYy04NmYxLWQ3MmFiZWI2YzgwYSJ9.0HxN54fky3DppT9DRLbVjMDNbSeeG2PEeZsMMG2zbik" class="fr-fic fr-fil fr-dib" width="345" height="156"></p><p><strong><span style="font-size: 10pt;">Fig 1. Enable the integration module</span></strong></p><p><br></p><p data-pasted="true">Once enabled add a new connection record and you will see the details tab, here you will need to enter some credentials to connect to your Assetbots instance. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQyOThhZTU5LWYwYWEtNDUxOS1iZTg0LTQyZGZjNjhmMTQ3ZSJ9.Vfflty_CMAUWu9QLBp_k6Fe9xXR7qJaFf3Zw-x2u_wE" class="fr-fic fr-fil fr-dib" width="1870" style="width: 1872px; height: 487.024px;" height="487"></p><p><strong><span style="font-size: 10pt;">Fig 2. Connection details for Assetbots</span></strong></p><p><br></p><p>In the 'Name' field give this connection a name. In the "Database Id" field enter your Assetbots Database Id. Then you will need to generate an API token in your Assetbots instance and enter this into the "API Token" field. </p><p><br></p><p>Once you have entered your credentials, you can use the "Test Configuration" button to test the connection. Once a successful result is received you can begin configuring your site import.</p><p><br></p><p><strong><span style="font-size: 14pt;">Sites</span></strong></p><p>If you do not yet have sites in your Halo, Locations in Assetbots can be imported into Halo as sites. When imported a connection will be established between the location and associated site so that when changes are made to the location in Assetbots (such as to the address, the site in Halo will be updated. If you already have your sites created in your Halo instance you can map existing sites to Assetbots locations to ensure updates to Locations will sync into Halo and update the mapped site in Halo. </p><p><br></p><p>Head to the "Sites" tab to configure site imports and mappings</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQ2NjE5NGI5LWZiYTgtNDMxYi1hNGI2LTI3NDM1MTM2MWI0NSJ9.nQ80UX_CNJLQTHXOafwlVP31nKS4me-QhRh-Bu92mXw" class="fr-fic fr-fil fr-dib" width="1651" style="width: 1653px; height: 916.321px;" height="916"></p><p><strong><span style="font-size: 10pt;">Fig 3. Site import configuration</span></strong></p><p><br></p><p>The "Site Mappings" table is used to map existing Assetbots Locations to existing sites in Halo. Used when each location already exists as a site in Halo. </p><p><br></p><p>To create a mapping, simply choose the Halo site and Assetbot location to map together. Once all sites are mapped use the "Import sites" button to complete a sync, this will solidify the link between the site and Location, and update the Halo site with information from Assetbot (like address). </p><p><br></p><p data-pasted="true">If you do not yet have sites in your Halo instance, you can use the "Import Sites" button to import locations in Assetbots as sites. Once imported, then map the imported Locations to their respective Halo site. </p><p><br></p><p data-pasted="true"><span style="color: rgb(0, 0, 0);"><strong><span style="font-size: 12pt;">Determine the Sites Assets are imported under</span></strong></span></p><p><strong>Site Rules</strong></p><p data-pasted="true">All assets in Halo must belong to a site, therefore you will need to configure site rules to determine the site in Halo assets are created under. All assets in Halo must be assigned to a site, therefore rules allow you to determine the site each asset should belong to based on criteria for the asset. </p><p><br></p><p data-pasted="true">To create a site rule add to the 'Site Rules' table. Here you can set some criteria based on an asset field, if an asset meets this criteria it will be imported to the selected site. In the Figure 4 example any assets that have the 'asset number' field starting with '73' will be imported to the customer Tony's Tyre Emporium and the site 'Cambridge'. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ0NmQzNGQwLTdiYjEtNDBmMC04OTM1LWY0ZTQ1NjM3ZmY5NyJ9.jzgKJH_62Drdgdi5hAS7TlPuY5wCzwp1palj7CZc5g8" class="fr-fic fr-fil fr-dib" width="612" style="width: 614px; height: 459.21px;" height="459"></p><p><strong><span style="font-size: 10pt;">Fig 4. Site Mapping Example</span></strong></p><p><br></p><p>The sequence of the rule will determine the order in which it is checked. Lower sequence rules will be checked first. Once an asset meets criteria for a rule it will be imported to that site and no further rules will be checked. </p><p><br></p><p data-pasted="true">You will also need to set a default site, this is the site that assets will be imported to if they do not match a site mapping or site rule.</p><p><br></p><p><strong>Don't update the asset site for existing or matched assets -</strong> When this setting is enabled assets will be imported to a site in line with the site rules/default site, but after the initial import their site will not change. This allows you to change the asset fields that rules are based on without this changing the site of any existing assets is under when the sync runs. </p><p><br></p><p><strong><span style="font-size: 14pt;">Match Assets to Users</span></strong></p><p>Users in Halo can be matched and assigned to assets upon import. Allowing you to carry over user information for each asset. </p><p><br></p><p>User matching is configured in the "Users" section of the "Sites" tab.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjBkOWUxODU5LWFjNDYtNDFjYi1iYmNiLTFjZjg2ZTkwOTIwOSJ9.j6Acm02OFcpStG22Lmp2cB5QqeiYh76-QFw-_qYtXQ0" class="fr-fic fr-fil fr-dib" width="1881" style="width: 1883px; height: 399.161px;" height="399"></p><p><strong><span style="font-size: 10pt;">Fig 5. User matching configuration</span></strong></p><p><br></p><p><strong>Allow User matching -</strong> Toggling this setting will enable/disable user matching. When disabled assets will not be attempted to match to a user upon import unless matching is enabled for the asset type. </p><p><br></p><p data-pasted="true"><strong>User matching field - </strong>Here you can set an additional field that is used to match users in Assetbots with users in Halo. Users will attempt to be matched on username, email and network login regardless of what is set here. But, you can choose an additional field to use for matching if you use another field to uniquely identify users. </p><p><br></p><p><strong>Assign Assets to their User's Site if a User is successfully matched -</strong> When enabled, assets will be imported to the same site as their user, if they match on a user. This will override the site mapping rules. </p><p><br></p><p><strong>Site rules overrides the Users Site if a User is successfully matched -</strong> When enabled, assets will be imported to the same site as their user, unless they match a site mapping rule. If they match a site mapping rule they will be imported to the site in line with the rule instead. </p><p><br></p><p><strong>Do not remove existing Users from an Asset if a valid User is not found - </strong>When enabled, if the asset is currently matched to a user but when the sync runs they cannot be re-matched to this (or another) user, the existing user will remain assigned to that asset. If disabled the user will be un-assigned from the asset after the sync if it cannot be re-matched. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 14pt;">Asset Imports</span></strong></p><p>Head to the 'Assets' tab. Here you can configure what details are imported with assets.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImNhMjg1NTYwLTVjMDMtNDlkNS1hN2JkLTYzYzg0ZWNlODhiNiJ9.Joy82nYD4iH3cO9QGCMqDPpEBqynBFLtpVsV63O49EQ" class="fr-fic fr-fil fr-dib" width="1776" style="width: 1778px; height: 1019.02px;" height="1019"></p><p><strong><span style="font-size: 10pt;">Fig 6. Asset Import Configuration</span></strong></p><p><br></p><p data-pasted="true"><strong>Asset matching Field -</strong> Here you can set which field is used to match assets in Assetbots to assets in Halo. The asset unique identifier field should be selected here. The Assetbots ID will always be checked first, but if no match can be found this field will be used to make a match. Assets will be given an assetbots ID if it has been created or updated as a result of an import from Assetbots. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 12pt;">Asset Fields</span></strong></p><p>In the field mappings table you can map an Assetbots field to a Halo field, this determines which field data from Assetsbots gets imported into in Halo. When creating field mappings you can either select an Virima field from the dropdown, or enter a custom attribute.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQzOTEwNTYxLTdhYzktNDA2MS1hOTZlLTBjMzlhYjQ1MjlhYSJ9.sETATnk-WBkW3epvOCcvVP1agJQYQkzC_EEM6ML9nMo" class="fr-fic fr-fil fr-dib" width="643" style="width: 645px; height: 420.89px;" height="421"></p><p><strong><span style="font-size: 10pt;">Fig 7. New Field Mapping</span></strong></p><p><br></p><p data-pasted="true">To map a Halo field to an Assetbots custom attribute check 'Manually enter custom attribute?' and a free text field will appear. Here, you will be able to enter the name of the attribute, ensure it is an exact match to how the field is named in Assetbots. </p><p><br></p><p>You can also have a Assetbots field create a new field against an asset in Halo by selecting '*Create a new Field during the next import*' in the Halo service desk field. </p><p><br></p><p>Note: Ensure the field you have selected as the "Asset Matching Field" is mapped. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 12pt;">Asset Types</span></strong></p><p>All assets in Halo must have an 'Asset Type', so you will need to configure how asset types are determined for assets imported from Assetbots. </p><p><br></p><p>First set a default asset group, this will be the group any new asset types are created under. </p><p><br></p><p>Use the 'Determining an Asset's type' field to determine how asset types are assigned to imported assets. The asset types of the assets can either use a fixed type for all assets, be determined from a field, or use asset type mappings that are determined using rules based on the values of the mapped asset fields.</p><p><br></p><p><strong>Import all Assets as the Same Type</strong></p><p>If you would like all imported assets to have the same asset type when imported set the 'Determining an Asset's type' field to be 'use the same type for all Assets' then set the 'Default Asset Type' field to be the asset type you would like assets from Assetbots to be. Figure 8 shows how to set this so all assets are imported as the 'Business Application' asset type. <br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjlhZTgzNmY3LTcwNGItNDE5Mi04OWQxLWZmODMzNzg4YjQ2YyJ9.3A5W469HiyTap5n_r2gjk1QPwuzqWSZQmr-WdloppZA" class="fr-fic fr-fil fr-dib" width="1899" style="width: 1901px; height: 320.948px;" height="321"></p><p><strong><span style="font-size: 10pt;">Fig 8. Import all assets with the same type</span></strong></p><p><br></p><p><strong>Use a Field to Determine Assets' Types</strong></p><p data-pasted="true">If you would like all imported assets' types to be determined by a particular field, set the set the 'Determining an Asset's type' field to be 'Use a field to determine each Asset's type'. </p><p><br></p><p>Then in 'Field for determining an Asset's type' choose the field you would like the type to depend on. The field you choose must contain the name of the desired asset type, if this name can be matched to an existing asset type in Halo, it will be assigned this asset type. If the name is not the same as an asset type in Halo, a new asset type will be created. Note that the names must be identical in order to match. This setting is used if you have a field in Assetbots that already determines an asset's type and you would like the types to be consistent between Halo and Assetbots. You will still need to populate the default asset type field, assets that do not have the selected field populated will be imported as the default asset type. </p><p><br></p><p>In Figure 9 asset types will be determined by the value in the field 'Categories'. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImY3N2ZiMmQ0LTk4M2UtNGNjMi1iZDgxLTc5ZmI0NWYyYWVlZCJ9.o1MAEt61qNDzrpiuk6if14ODGRqLIwiK6ooIQp5YYfk" class="fr-fic fr-fil fr-dib" width="1855" style="width: 1857px; height: 401.792px;" height="402"></p><p><strong><span style="font-size: 10pt;">Fig 9. Determine Assets' Types using a field</span></strong></p><p><br></p><p><strong>Determine Assets' Types using Rules</strong></p><p data-pasted="true">If you would like asset types to be determined by asset rules set the set the 'Determining an Asset's type' field to be 'Determine asset type using rules'. Now you will be able to set asset's types based on rules, These rules are based on field values, and if matched will assign an asset to the chosen asset type. When creating a rule first add criteria for the rule, select the Halo field that you would like to base the criteria on, then set the rule type and the outcome needed in the field to match the rule. If an asset matches this rule it will be imported as this asset type. </p><p><br></p><p>For example, in Figure 10 the rule I have set up will check the name field of an asset, if the name begins with 'LAP' the asset will be imported with the 'Laptop' asset type. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRkMzYwZGMxLTBjMDItNDFkOC04ODE4LThkNjQ2MDFjN2JiMiJ9.5nZXtPe5xO_I-xmQU2mVsL9dd7T6cnGrxVIDX7jqASI" class="fr-fic fr-fil fr-dib" width="608" style="width: 610px; height: 501.594px;" height="502"></p><p><strong><span style="font-size: 10pt;">Fig 10. Determine Asset Types using rules example</span></strong></p><p><br></p><p data-pasted="true">If an asset is imported that does not match any of these rules, it will be created under the default asset type set. Alternatively, if you would like to not import assets that do not match these rules, set the 'Default Asset type' to 'Don't import assets that do not match any rules'.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQ5OTQ4MWQzLTQyMzUtNDZiYy1hMjNiLTc0MGE5NThlNTMzZiJ9._eBc51L1i0eHyMjQQtX2OjgUIQ-tI23Gejq0bIqA9GA" class="fr-fic fr-fil fr-dib" width="1805" style="width: 1807px; height: 486.339px;" height="486"></p><p><strong><span style="font-size: 10pt;">Fig 11. Determine Asset Types using rules and do not Import Assets that dont match a Rule</span></strong></p><p><br></p><p><br></p><p><strong>Don't update the Asset type for existing or matched Assets- </strong>If enabled, any assets that match to an existing asset when importing will not update the existing asset with a different asset type from Assetbots. This allows you to change asset type data in Assetbots without it affecting the existing assets in Halo.</p><p><br></p><p><strong><span style="font-size: 12pt;">Miscellaneous Asset Import Settings</span></strong></p><p>Some additional settings are available to control if/how assets are imported. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjIyMmZjYWIzLTFhYTctNDE1Zi1iY2RhLTMxMGVkNDg5NDAzMCJ9.3ynrMbfu1IUAfaiApBiynrrT_7xvr0TakRX74QbfWAQ" class="fr-fic fr-fil fr-dib" width="1741" style="width: 1743px; height: 929.547px;" height="930"></p><p><strong><span style="font-size: 10pt;">Fig 12. Miscellaneous Asset Import Settings</span></strong></p><p><br></p><p><strong>Don't create new Assets -</strong> When enabled, new assets will not be created when assets are imported from Assetbots, only existing assets will be updated. Useful if you do not want to create any new assets after the initial asset import has been carried out, but you want to ensure the assets created remain updated. </p><p data-pasted="true"><strong>Status of New Assets -</strong> Here choose the status you would like newly created assets from Assetbots to have.</p><p data-pasted="true"><strong>Deactivate Assets in Halo when they are deleted from Assetbots (Halo Integrator only) -</strong> When enabled, when an asset is deleted from Assetbots the associated asset will be deactivated in Halo. This will only apply when the sync is carried out by the Halo integrator. </p><p data-pasted="true"><strong>Status for Assets when they are deleted from Assetbots (Halo Integrator only) - </strong>This is only available when "Deactivate Assets in Halo when they are deleted from Assetbots (Halo Integrator only)" is enabled. Here choose the status assets in Halo should have when the associated asset in Assetsbots is deleted. </p><p><br></p><p><strong><span style="font-size: 14pt;">Import Assets and Sites Automatically</span></strong></p><p>The Halo integrator can be enabled to have assets and/or sites imported automatically on a schedule (daily). To enable this head to the "Syncing" tab and enable "Enable the Halo Integrator for the Assetbots integration". </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImUyOWU4ZDI3LTA2NjMtNDI1MS05YmRmLTMzY2ZlYTE3YTkzZCJ9.hvJR7sL1UUyykZf4b0mDqyfFCmMeTRp4eHPx6u8Q6Tg" class="fr-fic fr-fil fr-dib" width="1100" style="width: 1102px; height: 488.533px;" height="489"></p><p><strong><span style="font-size: 10pt;">Fig 13. Enable the Halo Integrator for the Assetbots integration</span></strong></p><p><br></p><p>Once enabled you will need to choose which entities you would like to be imported, assets and/or sites. </p><p><br></p><p>Now an import of assets and/or sites will be carried our each day to create/update assets/sites in Halo. </p>
