HaloPSA Roadmap

Azure Translator integration now available

The Azure Translator integration allows you to instantly translate notes from users or other agents into the language that you are currently viewing Halo in.

When active, a translate button will show for each action note. Press it to translate the note. This will auto-detect the language of the note and translate it into your current language using Azure translator.

The note will then be replaced with the translated version and pressing the button again will revert to the original.

Any notes which are translated are stored in the database and the translation is automatically loaded the next time you view the ticket.

To configure, set up a Translator within Azure > Cognitive Services, and obtain an API Key from "Keys and Endpoints", and paste your API key in Config > Integrations > Azure Translator - Translator API key.

There are options to choose between translating only plain text (to reduce usage costs), or HTML (to include images and preserve the formatting in the translation). A monthly character limit can also be added here.

Improvements to Agent Resource Booking

If agent resource booking is enabled you can specify at ticket type level if you want the ticket to allow booking agents and if so, you can also specify if you want the user to be able to book appointments with the assigned agent or a team.

You can set the default team in the ticket type defaults.

You also need to specify the allowed teams for this resource booking.

If it is set to team, the user can pick from the allowed teams when booking an appointment. Also, if it is set to use the assigned agent and the ticket is unassigned it will use ticket's team to assign an appointment.

There is also now a setting at ticket type level to allow user's to book an appointment with an agent from the portal, which will add a button to any ticket of that type when the user is logged in that will take them straight to the booking screen. The user will be informed on the ticket if they already have an appointment scheduled for that ticket.

New dashboard widgets added for Ticket list and Ticket counter

Two new dashboard Widget types have been added, "Ticket List" and "Ticket List Counter".

Ticket List allows you to show a list of tickets based on ticket area, filter profile, lists, team or agent within a dashboard. These behave like the ticket list in the tickets area, allowing you to open, sort, filter and bulk action the tickets in the list. A column profile can also be chosen for the widget. ... > "Open list" will take you to the full list within its relevant area.

Ticket List Counter is similar to Ticket List but instead shows a count of the number of tickets in a list and looks the same as the report counter widget. Clicking the counter takes you to the full list within its relevant area.

HubSpot CRM Integration now available

A HubSpot account can now be connected to your Halo instance. 2-way syncing is available for both Companies and Contacts.

Companies can be filtered based on their Lifecycle Stage in HubSpot. They can also be manually linked to existing Clients/Sites in Halo.

Field mappings can be configured for both Companies and Contacts. The field mappings can be for importing only, or also for syncing back to HubSpot.

Companies and Contacts can be imported manually as well as on a schedule using the Halo Integrator.

Syncing to HubSpot can be enabled for creating and/or updating Companies and Contacts. This can be disabled on a per customer/user basis in Halo (option underneath the "Is Active" field).

Companies and Contacts can also be archived in HubSpot when they are deactivated in Halo.

Added column profiles to Assets

You can now create custom column profiles for assets in a similar way to tickets. Two additional settings have been added to select a default asset column profile. There is a global setting and an agent level setting. The agent level setting will override the global setting. If the agent level setting is set to * Default *, then they will use the global level default setting. The global setting can be found in Configuration > Assets > General Settings > Views:

There is also a button to take you to the column profile configuration page.

The Agent level setting can be found in My Account > Preferences > Assets:

When creating a new Column profile, you will be able to add any of the columns in the default profile, along with any asset fields you may wish to view.

Auvik integration now available

The following functionality is now available:

• Map tenants and their sub-tenants from Auvik to clients and sites in Halo. 
• Import tenants and sub-tenants from Auvik.
• Create mappings between network types and device types from Auvik and asset types in Halo.
• Import networks and devices. Networks and devices will be linked during the import in Halo if they share a relationship in Auvik.
• The above import functionality is available in the Halo Integrator.
• Alerting via webhooks from Auvik. When a ticket is created from an Alert, an option shows in Halo to open the alert in Auvik. An option will also show against the alert in Auvik to open the ticket in Halo. Alerts can be dismissed in Auvik by closing the ticket in Halo. 

New asset screen customisation options have been added

Various new features have been introduced to offer more customisation of the asset details screen in the agent app and self-service portal.

1. In the Asset type field list, an option has been added to place an Asset field on a Custom tab instead of the Details tab. This applies to the Agent app only.

2. In the Asset type field list, an option has been added to add a Group Name to the field. Fields with the same group name, that are on the same tab and next to each other in the list will be grouped together under the heading. This will apply to the agent app and self-service portal.

3. Field visibility and whether it's mandatory on the Agent asset details screen can now be customised within the Asset type field list. The possible values for "Agent Asset details screen visibility" are "Not visible", "Visible - Not Required", "Visible - Required".

4. Field visibility on the self-service portal can be edited from the Asset type field list. The possible values for "User Asset details screen visibility" are "Not visible" and "Visible". 

5. Dynamic field visibility can now be configured for asset fields within the Asset type field list. Asset fields can be made visible when another Asset field is set to a particular value. This works similarly to Ticket level dynamic field visibility. This will apply to the agent app and self-service portal.

6. A new tab called "Layout" has been added to the Asset Type config screen. When Tab layout is set to "Custom", you can then re-order all the system and custom tabs on the agent app's asset details screen for the asset type.

7. When customising tab layout, select the edit button on a tab to alter how the tab displays. The possible options are "Hide", "Show Tab" (default), "Pin to sidebar 1", and "Pin to sidebar 2". The pin to sidebar options allows particular tabs to stick to the right side of the screen, like in the example below where the details tab is pinned to sidebar 1, and a custom tab and the users & linked assets tabs are pinned to sidebar 2.

Improvements to the Azure DevOps integration

1. Changed the way data is sent and retrieved from the Azure DevOps API.

2. You can now manually assign an Azure DevOps project to a product in Halo. Once assigned or imported, a button shows to open the project in Azure DevOps.

3. You can now link multiple Azure DevOps work items to a ticket in Halo. The DevOps details are no longer displayed on the ticket details pane. Instead, a tab now shows with all linked work items. Double clicking the linked work item will open the work item in Azure DevOps.

4. A work item can be designated as the primary work item in Halo. The primary work item's ID number will be displayed in the third party ID field in list views throughout Halo.

4. You can manually link work items to a ticket in Halo. Clicking the below button will open the Halo search screen.

The search screen allows you to search for work items in DevOps. You can search via work item ID or via a search phrase. It is also possible to filter by work item type.

5. The setup screen for the integration has been changed to accommodate other new features of the integration.

6. It is now possible to map category fields to the Area and Iteration path fields in Azure DevOps. You must first choose which category field to use for the mappings, before creating a mapping between each category/path value. This functionality works bi-directionally.

7. The work item description can now be set when creating a work item. This field allows the use of dollar variables.

8. $-AZUREDEVOPSWORKITEMS variable now available. This produces a table of all linked work items, including a clickable link to open each work item in Azure DevOps.

9. The "Create Work Item" system action type can now be used in timed actions in workflows. When the timed action is added, the work item will be created and linked to the ticket in Halo. Requires NHServer v13.34 or above.

10. Two buttons are available in the setup screen to view the required configuration for incoming webhooks.

This opens a popup screen showing the required setup.

11. A new webhook url is now used to process webhooks. Existing webhooks setup in Azure DevOps DO NOT need to be modified, the old url will still work.

Added the option to allow users to create accounts from the end-user login screen

In configuration>self-service portal, you can turn on 'Allow new users to register from the portal' and specify which site to create the users against.

This will add a link to the login screen on the self-service portal where the user can enter a username and email. If the email is not already in use, it will send them an email to confirm their email address and set a password.

If the email domain matches the domain of a site in Halo, it will create the user against that site.

Snow Integration added.

The Snow integration is now available on the Halo Web Application. This integration will work for both internal and publically accessible instances of Snow, however, you will not be able to perform any imports through the web client to internally accessible Snow instances if your Halo couldn't access it.

When navigating to the integration page you'll need to enter your snow application URL, username and password. Note that the user you use for this must have the role of "Api User" else the integration will not function.

After this, you'll be able to import clients, note that the client import will also import licences but will only import licences for clients that have devices imported. Clients with no devices will not have licences imported. This means the first client import will also not import any licences so a client import, then a device import then another client import must be run to import licences. This is a limitation of the Snow API endpoints and the easiest way to access licences and link them without affecting device import speed.

Once you've imported clients you should then be able to devices as no devices can be imported before clients are imported. Before importing devices make sure to set all the mandatory fields for the site, asset type and Asset-user matching type. The final setting chooses which users will be related to the asset in Halo and there are several options.

There are also several miscellaneous options available for the device import is shown below to prevent the updating of certain fields against devices. These were added for those who'd previously used the older snow integration with the Windows Client to prevent the creation of new devices, changing of device types and changing of device locations due to the use of a new id for the Snow Integration in the Web App. 

Note that the Asset import imports both Computers and Mobile Devices as they are classified in Snow.