Release 1.2.5
Information
These notes describe a historical release. For the most up-to-date information, see the latest release notes.
Version: 1.2.5
Build: Not recorded
Latest branch build: 1364
Build version: 1.2.5
Released: 20 June 2019
Release Summary
|
Item |
Details |
|---|---|
|
Release Status |
Released |
|
Upgrade Impact |
Follow the standard upgrade process. |
|
Supported Upgrade Path |
Standard upgrade process. |
|
Breaking Changes |
None. |
|
Compatibility |
No change. |
|
Licensing Impact |
None. |
|
Security |
None. |
|
Highlights |
Maintenance release with GPO and Tally trigger corrections. |
Upgrade Guidance
Follow the standard upgrade process for this release.
Supported Upgrade Path
Follow the standard upgrade process.
Before Upgrading
-
Create a full system Backup.
After Upgrading
-
Verify licensing, Node connectivity, routing, and Hardware Panels.
Compatibility
|
Area |
Change in This Release |
|---|---|
|
Server Operating System |
No change. |
|
Browser Clients |
No change. |
|
Hardware Panel Firmware |
No change. |
|
Integrations |
No change. |
Licensing Impact
None in this release.
Breaking Changes
None in this release.
New Integrations
None in this release.
Added
None in this release.
Changed
GPO Follow
-
Changed GPO outputs that follow a state to set the device back to the desired state when the device reports a different state.
-
This reapplies the requested output after a GPIO device restart or reconnection, even when the followed Tally has not changed.
Tally Triggers
-
Changed Tally triggers to run only when the state changes, and to publish the same state again if the last update was too long ago.
-
When switching between Sources, only Rules for Tallies whose state changed are triggered.
Fixed
None in this release.
Known Issues
None in this release.
Additional Information
For more information, see: Risk Context.
Trademarks
Note
All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.
RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with these third parties unless explicitly stated.