As we head into the second quarter of the year, we would like to take the opportunity to provide you with an overview of some of the new HaloITSM features that were recently released.
As an organisation, we would like to thank all of those who have provided feedback and suggestions for new features. We have and continue to take into account our clients ideas, in addition to our pool of thoughts internally. From integrations to the self-service portal, we’re making sure everything you need is all in one place.
1. New Features
1.1 Kanban
1.2 New Search Feature
1.3 Continually Chatbot
1.4 Managed PDF Reports
1.5 Voting
1.6 Microsoft Teams
1.7 Monitored Service Status Updates
1.8 Mandatory approvers now available for approval process
1.9 Knowledge Base Articles
1.10 Service category additional Tiers
1.11 Exporting Tickets
2. New Integrations
As part of our new release, we have several additional integrations that are now available with HaloITSM.
2.1 SCOM
Integrate System Center Operations Manager with HaloITSM to centralise your alerts under one system. Alerts can be received from SCOM via SMTP and turned into tickets in Halo. The Halo Integrator can be run on the SCOM server so that when they are resolved in Halo, they are closed in SCOM, and any closure notes are added to the alert.
2.2 PRTG Network Monitor
You can now synchronise and pull assets from PRTG directly into HaloITSM. Mappings can be configured there, and enabled to occur on a recurring basis.
2.3 Device42
Import customers and devices from Device42 into HaloITSM. Custom fields can be mapped to Halo fields for both customers and devices. Webhooks can be configured in Device42, so that when a customer or device is created, updated or deleted in Device42, they are duplicated in Halo. Deleting a customer or device will make the record inactive in Halo rather than fully deleting the record.
2.4 Splunk On-Call
Incidents can now be created in Splunk On Call when they are raised in Halo. This can be achieved for manual tickets, or for tickets raised via email that match an email rule.
When raising a ticket, you can now choose a user or team/escalation policy to assign the incident to Splunk On Call. A default value for this option can be configured at ticket type level.
When responding to or resolving a ticket that is linked to a Splunk On Call incident, the incident will be automatically acknowledged/resolved in Splunk On Call. Notes can also be pushed from a Halo ticket to a Splunk On Call incident.
New incidents and any updates to existing incidents in Splunk On Call can be synced back to Halo using outgoing webhooks.
2.5 Solarwinds Orion
Trigger and reset actions can be configured for alerts in SolarWinds Orion to automatically create and resolve tickets via the Halo API.. Trigger actions can automatically assign tickets to the team and technician of your choice, set the priority of the ticket, and also link an asset to the ticket.
2.6 Powershell
The PowerShell integration can now be configured by hosted customers. When configuring a script, hosted customers will be required to select the Halo Integrator as the method of running the script.
3. Upcoming Developments
For more information:
If you would like to learn more about future developments, check out our roadmap here.
Want a more in-depth discussion of specific features, or simply have a question? Feel free to Contact us, and we’ll get back to you shortly.
