Just a few months ago saw the long-awaited release of Unifi 3.0 which introduced a series of exciting new features including Unifi Test Assistant and a full documentation revamp. Since then, we've continued to work on additional improvements including automatic heartbeat messages and significant performance improvements to the Designer portal, which were quietly released as version 3.1. Today, we're releasing patch 3.1.2 which contains several extra bug fixes and improvements to Unifi.
Automatic Heartbeat
Unifi now supports heartbeat messages from 3.1, which can be setup to periodically test the endpoints Unifi is connected to. Heartbeat automatically monitors and manages the integration, with the integration status being updated to "Up" or "Down" depending on whether the heartbeat was successful or not. When "Down", all integration messages will be queued, and when "Up", all queued messages will be sent in order.
Portal Performance
With the extra features added to Unifi Designer in v3.0, we realised there was a need to improve the performance of the Portal as well. In 3.1, the Portal lists and forms now benefit from being up to 10x faster, which drastically improves the usability and experience of integration configuration.
Patch release 3.1.2
Unifi 3.1.2 fixes two significant bugs:
1) Multiple bonds could be created when working with multiple target records (e.g. Incidents) in one thread.
2) Multiple bonded attachment records could be created when ServiceNow Antivirus was enabled.
There are also a few more minor fixes as well as a change to the format of the Created ms and Updated ms fields.
Read more
If you missed the v3.0 release, you can read more in our blog and Unifi 3.0 release notes.
You can also find more about what's included in the 3.1 release, including this latest patch, in our Unifi 3.1 release notes.