Documentation to assist with the setup and configuration of the HaloPSA platform
Transfer Configuration Between Development and Production Environments
Released in Version: 2.104.1
To begin using the 'Config Change Tracking' functionality you will need to first enable the setting in Configuration > Advanced Settings:
With this setting enabled, for supported entities, a snapshot of each config change that is made is captured, along with a roll-back script (where possible). These config changes can be viewed by clicking the 'View Config Changes' button.
Change tracking applies to the following entities;
- Global settings
- Enabled modules
- Ticket Types
- Action config
- Service Categories
- Custom Fields
- Custom Tabs
- Custom Tables
- Field Groups
This list will be expanded in future.
This icon will display in the top right of details screens where change tracking is active;
The Config Changes list serves as a way of auditing config. Config changes are listed from newest to oldest.
From the list, you can bulk-select commits and export them to a JSON file using the selectable tick box on the left side of the screen. Commits can be imported from this screen as well using the import button in the top right, serving as an easy way to move config into another instance of Halo.
Commit details can be viewed by clicking on the list. This shows details of the API request that was made and the rollback API call. DELETE's cannot be rolled back.
Config changes involving password fields and sensitive information will be encrypted and details will not show.
On this screen, you can "Roll back before this change". This will revert each change made after the selected change sequentially, along with the change you have selected, restoring the config to the point it was at before the change was made.
Customers with Linked UAT and Production Environments:
Customers with both UAT and Production Halo environments will now see a new Config option for "Instances".
Configuration > Instances will list each of your linked Halo instances, along with configuration differences between the current instance.
An instance will be classified as 'in-sync' once it matches the version of the current instance, and a UAT restore has been performed from the production environment for the first time after the production environment is on v2.104.
For instances that are in sync, you can view the config differences between the current instance and the selected instance from the instance details screen. Changes can be Pushed to the selected instance, or Pulled onto the current instance from the "Changes Behind" and "Changes Ahead" tabs. This replicates the same API request that was made for the changes in the other instance for each commit sequentially from the oldest first.
For non-production instances, a "Restore from Production" button will also show on this screen. Use this button to log a request with Halo Support to update the UAT instance with the latest production data.
- Asset Import - CSV/XLS/Spreadsheet Method
- Call Management in Halo
- Creating a New Application for API Connections
- Creating Agents and Editing Agent Details
- Departments, Teams and Roles
- Halo Integrator
- Importing Data
- Multiple New Portals with different branding for one customer [Hosted]
- Organisation Basics
- Organising Teams of Agents
- Step-by-Step Configuration Walk Through