HaloITSM Roadmap

Customer and Payment updates can now be received via webhooks from QuickBooks Online

You can now allow Halo to receive updates whenever a customer is created or updated, and whenever a payment is created or updated for an invoice in QuickBooks Online. 

Once an invoice is fully paid, the date paid field will be automatically set to the current date.

Stripe integration now available

Invoices can now be paid via Stripe in both the Halo agent application and also the self-service portal.

If the invoice has not yet been paid, a Receive Payment option will display in the agent application.

In the self-service portal, a Pay button is displayed next to each outstanding invoice.

When clicking the either of the payment buttons, a payment form will be displayed allowing the end-user to pay the invoice, or the agent to take payment from the end user.

The ability to setup recurring payments for recurring invoices, and connected account functionality will be arriving later in Q2.

Added customer SQL import option

The SQL import integration can now be used to import customers.

The customers are matched using their customer reference and the customer's top-level can be matched on the top level's name.

You can map various customer fields, including any custom fields.

You can also map a new site name and address for when the import creates a new customer and site.

You can also restrict the import to not update the customers' top level and to not create any new customers.

Addigy Integration is now available

This integration allows for importing of Addigy devices with the ability to map Addigy fields to Asset fields and Custom fields.

Devices can be imported on a recurring schedule using the Halo integrator.

Creating tickets from Addigy alerts is also possible.

Requires NHServer v13.43+.

Scheduled Emails for Composite reports is now available

It is now possible to configure an email schedule for Composite Reports via the new Scheduled Emails tab on the composite report config screen.

This is configured like standard report scheduling, except you can only email the pdf, and you can choose a customer in the schedule config.

In order to generate these reports on a schedule, the charts in pdf reports have been modified to generate server-side instead of client-side. The pdf renderer has been upgraded to facilitate this.

You can also see a creation log for composite report schedules via the setup screen.

Improvements to scheduling for standard reports have been made to allow the same chart to show in pdfs that show in the client.

Requires NHServer v13.43+.

The Sage Intacct Integration is now available

Like all the other billing integrations, you can find this either in config > integrations or in Config > Billing. Currently as Halo doesn't have a developer licence you will have to use your own to use this integration. Once you've configured your details into the integration page you can do the following:

Tax Rates

You can Map Tax Rates to Sage tax rates:

These are used to match invoice line tax rates to Intacct's though we do also specify exact tax values when syncing to Intacct.

Accounts Codes

When enabling Intacct in Halo, we automatically turn on the accounts codes module for ease of use. You can then import all General Ledger Accounts Codes from Sage Intacct with the import and amend the names as needed.

Clients

You can import all your clients from Sage into Halo and it will try and match clients on accounts id and then on client name if needed. Note that when syncing back from Halo to Sage, there are some fields that don't sync back due to limitations in the Sage SDK. This is specific to the delivery address.

Items

You can import Item GL Groups before items to allow you to import items from sage into Halo. You can again sync changes to these back again to Sage Intacct as needed.

Invoices

Invoices are a 1 way sync to sage from Halo. To facilitate config to match the usage of Sage, we've added Item Group level Nominal codes such that you can mirror your config in  sage. We currently sync all invoices as sales invoices as well as this is what the Intacct SDK allows. We'll look into expand this as possible.

Improvements to the Jira integration

1. Changed the way data is sent and retrieved from the Jira API.
   
   
2. You can now link multiple Jira issues to a ticket in Halo. The Jira details are no longer displayed on the ticket details pane. Instead, a tab now shows with all linked issues. Double-clicking the linked issue will open the issue in Jira.
   
   
3. An issue can be designated as the primary issue in Halo. The primary issue's ID number will be displayed in the third party ID field in list views throughout Halo.
4. You can manually link issues to a ticket in Halo. Clicking the below button will open the Halo search screen. The search screen allows you to search for issues in Jira. You can search via issue key or via the issue summary. It is also possible to filter by issue type.
   
   
5.  The setup screen for the integration has been changed to accommodate other new features of the integration.
   
   
6. You can now add comments to Jira issues by adding the 'Sync to Jira' field to an action and setting it to true to sync the note of the action to Jira.
   
   
7. You can now create halo tickets from Jira issues using webhooks by creating a webhook with event Issue - Created. This will also map across the status and custom fields mapped in the integration config.
   
   
8. The issue description can now be set when creating a issue. This field allows the use of dollar variables.
9. $-JIRAISSUES variable now available. This produces a table of all linked issues, including a clickable link to open each issue in Jira.

Hudu integration added

Added the ability to create Users in Azure and assign them to groups via system actions

A new action system use called "Azure Action" is now available.

When this option is selected, a new "Azure Action" tab will show on the action configuration. Here you can select which Azure action you would like to perform, and which Azure connection you would like to use for the action. Connections setup in the Azure Active Directory Integration and also the Microsoft CSP Integration (HaloPSA) will show here.

If the connection you have chosen does not yet contain the necessary permissions to complete your selected Azure action, the required permissions will be listed as shown below. You must first add one of these permissions to your application in Azure and re-authorize the connection before the rest of the configuration options are made available.

Once your connection has the required permissions, you can configure input and output mappings. Input mappings allow you to map ticket custom fields to Azure fields for the corresponding action. Output mappings are only available when using the Create User Azure action, which allow you to map the ID of the created user to a ticket custom field. 

By creating an output mapping for the id field, you can then use this in subsequent Azure actions. For example, an automation workflow can be created that first creates the Azure user, and then assigns them to a group.

More Azure actions will be made available in the coming months.

CRM improvements

Multiple improvements to the CRM area.

1. Client details screen tabs can now be customised

"Screen layout profiles" have been introduced. These can be configured from Config > Advanced Settings.

These allow you to customise the tab order, visibility and side menus on the client details screen similar to how you can customise this on the asset type details screen.

There is a global default setting for the layout profile to use for the client details screen, as well as an override in Agent preferences.

2. CRM notes drafts

When adding a new CRM note, the note and other fields will now be retained when switching tabs and coming back to the CRM notes tab or exiting the client details screen.

3. Extra details field added for CRM notes.

Enable "Show a field for extra details when adding CRM notes" from Config > Users.

This will show an extra rich field on the add CRM note screen to add additional information which you do not want to be visible by default on the CRM note history.

If populated, the CRM note history will show an expand button under the main note, which will reveal the additional details when pressed.