HaloITSM Roadmap

Improvements to the Okta integration

The following features have been added to the Okta integration:

• Map users in Okta to sites/agents in Halo. Filter options are available for Okta groups and Okta user statuses.
• Map Okta user fields to Halo fields.
• Manage agent roles and change advice board memberships with Okta groups.
• Import users and agents both manually and on a recurring schedule.
• Select which Okta statuses make a user/agent active in Halo.

Added Microsoft Graph as a connection option to the Exchange Calendar integration

You can now select Microsoft Graph as a connection option in the Exchange Calendars integration.

Appointments that are created/updated/deleted in Halo will be synced immediately to Exchange as the create/update/delete event happens in Halo.

Appointments and changes to appointments in Exchange can be imported manually in the Halo UI or via the Halo Integrator on a schedule. Recurring appointments cannot be created through Halo, but they can be imported and updated in Halo.

Appointment types now have an additional option to create appointments of that type as a Microsoft Teams meeting in Exchange.

If you have created a Teams meeting, the appointment will display an option to join the meeting next to the complete option:

Atera RMM integration now available

• Import customers from Atera RMM
• Import Agents, Generic, HTTP, SNMP, TCP and HTTP devices from Atera RMM
• Process alerts from Atera RMM, including automatic closure of a ticket if the alert automatically resolves in Atera RMM
• Deactivate devices in Halo if they are removed from Atera RMM

You can now process different billings items in different areas

On the left hand side menu in the billing area, you can now access different things for invoicing:

If you navigate to one of them, you will be able to see more items at once and just process items of a given kind:

Sales and Purchasing enhancements

Several improvements and new features have been introduced to enhance the Sales and Purchase orders;

• Total stock count now shows on sales order lines
• You can now choose lines and the quantity when creating a purchase order from a sales order
• Indicator that a PO has been received from an SO
• An option has been added to add a note and change the status of a ticket when a PO is received
• You can now reserve stock and assets for orders (option in Item configuration)
• Stock received from a PO can be auto reserved for the SO
• When creating a PO from an SO you'll now get to choose whether the items are delivered to the user or into stock
• Receiving a PO which is delivered to the user will now auto-consign the Sales order
• You can now partially consign orders
• The number consigned now shows on order lines
• PO and SO statuses can now have system uses which allow them to be closed more easily
• Bringing a PO into stock will close it
• Additional views have been added within the Orders area to list Open or Closed orders
• Line item notes now show on hover of a line
• You can now partially invoice a Sales Order
• You can now view Quotes and Orders from a client record
• Items can now be marked as Contract items
• Items can now be linked to a project template
• Actioning of order lines - depending on the item configuration, a Contract, Recurring Invoice, and/or Project can be created for a line from the Sales order screen
• Items can now be excluded from invoices from the item configuration
• The cost now shows on stock history records
• A link has been added to view stock details from the add line item screen

Sales Mailbox integration

Sales Mailbox Integration

This integration allows you to create actions on open opportunities from emails within specified sales mailboxes. The integration will scan the sales mailboxes and detect if the email can be added to an opportunity based on the opportunity email address and the subject. 

It can be configured and enabled in Sales > Sales Mailbox.

More information can be found at https://halo.haloservicedesk.com/portal/kb?id=1185

Microsoft CSP integration now available

A partner managed application can now be created in your own Azure tenant, and have its permissions elevated so that it can access user data from all of your partner's tenants.

Once connected to your partner managed application in Halo, you can import all of your customer records from CSP, along with any licenses associated with them.

Similar to the Azure Active Directory integration, site mappings can be created to import subsets of users from your partner's tenants. These site mappings can be created manually or automatically whenever a customer is assigned an Azure tenant id.

Users can then be imported into these sites. If the user is assigned licenses in Azure, and the license exists against the customer record, then the user will be associated with that license during the import.

Further improvements to this integration will be coming throughout 2021.

Composite pdf reports now available. Added additional pdf template and report customisation options.

Within the reports menu, there is now an option for Composite Reports.

These allow you to create a pdf template that includes the data and/or charts from multiple reports and add other HTML content. This is done by adding the Report to the template, and then using the ReportData or ReportChart variable for that report within the pdf templates HTML.

PDF template enhancements have been made so that you can create multiple pages for a PDF report. You can also add a cover page that excludes headers and footers and can have its own background image. You can now use variables within HTML headers and footers.

Options have been added to Reports to override how the data table is shown. HTML can be specified for the table, and rows of the table to change the appearance of the data in both the report and ReportData variables. This can be done from the Appearance tab of a report.

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.