Find out about all the exciting, up and coming developments in HaloPSA
Datto RMM Integration Enhancements
Automatically syncing into Halo the information included in tickets logged and processed from Datto RMM.
Microsoft Cloud Solution Provider (CSP) - Phase 1
Import Customer/User data
Import billing information for subscriptions
Monthly and Composite Reports
Introduction of composite PDF reports.
Additional Service Category Grouping
An additional service category grouping to be introduced.
Sales and Purchasing Enhancements
Transfer of Configuration Between Development and Production Environments
Enhancements to improve the ease of transferring configuration between development and production environments.
Agent Home Screen Improvements
Enhancements to the agent home screen to provide dashboarding options.
Introducing functionality to increase collective collaboration between agents via chat boxes and tags/mentions to add into the ticket pages.
Introduction of keyboard shortcuts.
Mailbox matching for CRM
Scan sales teams mailboxes and record emails against opportunities/leads in HaloPSA
WhatsApp Business Integration
Integration with Whatsapp Business.
Atera RMM integration
Automatic import of devices from Atera mapped to Customer records in HaloPSA
Monitoring in Atera to create Tickets in HaloPSA and auto resolve.
To bring the Kashflow Integration into web application from the legacy application.
IT Glue Integration
Automatically adding new assets to IT Glue, synchronising an asset's name and properties to IT Glue and adding a link on the asset's overview to view the instance in IT Glue.
Expansion of ITIL Alignment
Enhancement of CI functionality, and Incident and Service Request management.
Google Maps & Agent Lookup
Adding functionality to track all active agents on Google Maps.
Introducing follower notifications on specific tickets or tickets assigned to a specific agent.
SAML and OpenID Connect
Improvement to the ease of configuration with the general SAML and OpenID connectors.
Project Management Advancements
Expansion on the existing project management functionality in the Halo web-app.
New Mobile Apps
New Halo iOS and Android applications
Self Service Portal Improvements (Phase 2)
Allow users to view invoices and projects on the portal and to update them with notes
Remote session tool to provide instant support to clients.
Automate Office365 tenant changes
Approval processes to automatically create users/assign licenses and update license amounts in Office365 via Azure/CSP/Pax8 and other vendors APIs
Sync Billing Data - Live product lookups - Update Services/Subscriptions from Halo
Device42 integration now available
Import customers and devices from Device42 into Halo. Custom fields can be mapped to Halo fields for both customers and devices.
Webhooks can be configured in Device42 so whenever a customer or device is created/updated/deleted in Device42, they are created or updated in Halo. Deleting a customer or device will make the record inactive in Halo rather than fully deleting the record.
Splunk On Call integration now available
Incidents can be created in Splunk On Call at the same time as a ticket is 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 in 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.
PRTG integration now available.
You can now synchronise and pull assets from PRTG directly into Halo.
To do it, navigate to configuration to configure your integration:
You can configure mappings there for the integration, as well as enable it to happen on a recurring basis using the Halo Integrator:
SolarWinds Orion integration now available.
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.
Examples of the trigger and reset actions are displayed in the integration setup screen.
When a ticket has been created via an alert, agents can acknowledge the alert in SolarWinds Orion through the Halo interface. When the ticket is closed, the alert can also be cleared in SolarWinds Orion.
If enabled, a "Related Alert" section will appear on the side tab of the ticket. This displays the alert name, and allows agents to acknowledge the alert.
Clicking the "Acknowledge Alert" option will open a input screen to add notes with your acknowledgement. An an action will then be added to the ticket. The Halo Integrator will then pass this information to SolarWinds Orion during the next sync.
Enhancements to the search functionality
You can now enable an option to search multiple entities at a time. This opens up an "All" search option.
The Search screen has also had a UI update.
You can also add a quick search to the agent app nav bar. This performs the all search and can be accessed using Ctrl + F within the app.
The search screen is now also avialable on the end user portal. End users can search articles, services and tickets. These can be enabled within the Self Service portal config.
Settings have been added to Advanced Settings to enable the "All" search and Quick Search, and to tune the all search to only look at entities you wish to search on most frequently.
Various other minor improvements to searching have been made.
Added contract scheduling functionality.
On the contract details screen, there is a new tab called 'Schedule'. On this tab, you can allocate time against the contract which can be used for scheduled tickets.
The top of the tab has an overview of the scheduled hours:
Hours remaining is the number of hours not allocated from the total.
Hours allocated is the number of hours associated with schedule appointments. In the above example, there are 96 hours associated with appointments for this contract.
Hours used is the number of hours on appointments in the past.
Hours used (actual) is the amount of time taken added to the ticket associated with the appointment.
Total hours is the sum of all schedule hours on the contract.
This table details the schedule pool of hours for this contract. The sum of these values is used for the total hours figure above.
You can add a list of email addresses which will receive the 'Outstanding Appointments' email. This email will provide information on all the upcoming appointments. Separate multiple email addresses with a comma (,)
If include account manager in emails is enabled then the Outstanding Appointments email will also be CC'ed to the account manager of the customer.
This table details all of the appointments and tickets created against this contract schedule. Tickets will be created against the appointment one day in advance of the appointment start date.
Appointments can be created by using the button. This will open a screen which can be used to create appointments based on your required recurrence pattern.
Outstanding appointment email can be created by using the button. This will create the email in the backend and then NHServer will send it at the next scan.
Appointments can be flagged to send invites out by using the button.
SCOM Integration now available.
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.
Asset serialisation from items now available
In addition to the new stock and consignments features, you can now create assets from items when bringing items into stock or consigning an order or items issued.
To enable, choose an Asset Type for the "Linked Assets Type for serialised Assets" setting on the Item details screen.
If you are not tracking stock levels, assets will be created when you consign an item.
If you are tracking stock, you have the option of whether to create the assets when receiving stock, or when consigning the item. This is a setting in Config > Items.
When adding stock or consigning depending on the above, you will be asked to create assets via a pop-up screen. On this screen, you can either choose an asset tag for each new asset, or auto allocate a tag.
If you serialise when receiving stock, when you consign items you'll instead be asked to choose assets to consign, by either entering their asset tags, browsing what's in stock, or auto allocating.
You can also allow serialisation to happen automatically all the time, by enabling "Automatically create and select serialised assets" in Config > Items. This will prevent the above screens from showing, new assets will automatically be allocated a tag, and assets will automatically be selected for consignment based on age.
Assets created from items will show additional information on the assets Supplier & Maintainance tab. Here you can also prevent the asset from being selected for consignment in the event it is returned to stock again.
Links to serialised assets will also show on the item, goods in and consignment records.
Stock control now available
Enable tracking of stock levels in Config > Items.
These will allow you to track the quantity in stock of an item at different sites.
Make a Site a stock location by enabling the "This Site is a Stock location" setting within a Site.
Items can be listed by location within the Items area using the "Items by Stock Location" view;
Receive stock by selecting "Receive Stock" from the Items list. This option also shows on right click of an item in the list, and on the item details screen.
"Stock" and "Stock History" tabs have been added to the Item details screen. Stock shows the quantity in stock at each location. Stock History shows an audit trail for every stock movement that happens. The quantity in stock will also show areas of the app which list items, such as the item list, adding items to a ticket or order.
You can drill into each Stock Location to view the stock received records for that location, with information such as how many were brought in, how many remain, and serialised assets that are created.
Stock is reduced when items are consigned from either a Sales Order, or Items Issued on a ticket. An option to consign a Sales Order or Items Issued now show on the Sales Order screen, and Items Issued tab of a ticket.
Consigning will consign all lines on the order which need to be consigned, and reduce the stock of the item. When either adding an item to an order, or consigning the order, a stock location can be chosen for each item. There must be enough in stock to consign the order.
When consigned a link to the consignment will show within the line item. Clicking the consignment will show information about the consignment such as the items on it, and any assets that were serialised.
A setting has been added to make it so Items Issued and Orders cannot be invoiced until they are fully consigned. This is available in Config > Sales Orders.
Stock can be transferred between locations using the "Stock Transfer" button on the Item details screen. A stock-take can also be performed to adjust the quantity in stock.