Nightly Changelog: 8.1.4-b20210304
1876: EAM: Remote upgrade of a 7.9 gateway to 7.9.x doesn’t upgrade all modules
Resolved the issue where the 8.x EAM controller did not upgrade all modules when upgrading a 7.9 gateway to a later 7.9 version.
900: Page Configuration Primary View Dropdown Displays Empty Directories As Views
Fixed minor rendering issue in Page selection tree which rendered empty directories as views.
1840: Column Container component SELECTION OVERLAY does not update when clicking between the various breakpoints
Perspective Designer - Component Selection highlighting correctly updates when switching between Column Breakpoints.
1870: Checkbox: onClick event fires twice on single click
Perspective Checkbox Component: onClick event will now fire once per click instead of twice.
1541: Need to be able to translate the login failure message for Vision clients
Classic login panel and IDP login panel in Vision client are now translatable.
1921: Alarms not Triggering on Tags when Modifying the Alarm Mode
Changes to a tag’s alarm configuration aren’t always evaluated immediately upon save- the value must change by more than the deadband before the correct state will be established. This has been changed so that the current state is evaluated immediately.
1950: Tag Backfill can prevent Tag Event scripts from showing immediately changed values when Timestamps aren’t in sync between Gateway and Vision/Designer
Writes to memory tags were using the timestamp of the source JVM, causing issues when the remote system’s clock was different than the gateway’s (future timestamp could block value changes until that time, past timestamp could potentially not be used as the current value). Writes to tags will now use the gateway’s timestamp. Advanced writing that seeks to manipulate the timestamp (by writing QualifiedValues through scripting) will need to be executed on the local gateway in order to continue working.
355: Gateway unable to deserialize arguments from a client-scoped system.db.runPrepUpdate call
An InvalidClassException was thrown when system.db.runPrepUpdate was called with parameters that resolved to BigDecimal objects.