Aurora On-prem Release Notes v5.11
Aurora On-prem
Alarm History Report
Aurora Runtime
Defect Fixes
|
Functional Area |
Description of Defect |
|
Trending |
The 2nd end date for trending
period over period was getting set when the screen was opened and when a new
date was selected it was not honored. As a result, the scale on the
trending graph was incorrect. |
|
Trending |
Trending data was getting blended
when there are multiple devices associated to an entity and some of the
devices have the same tag name. This has been corrected by displaying
the data element by its tagname_entityname_devicename. |
|
Trending |
When trending a duration less than
15 minutes the application was not defaulting to the minute data interval and
the seconds data interval was not an option. |
|
API |
API communication stopped
gathering data. |
|
Live View |
Meters in an alarm state not
connected to a bus bar in the live view were missing the alarm indicator. |
|
Live View |
Each time the Live View zoom
in/out was selected the application would do an additional zoom in or out by
5% on its own. Which looked like the screen was flickering. |
|
Live View |
Pan/Centering was occurring each
time the Live View was moved by the User. Changed the Pan/Centering to
only occur when the Live View is opened for the first time during each
session. |
|
Alarms |
Alarm email notifications were
delayed when the service had a lot of data to process. |
|
Demand Response Alarm |
Demand Response Stop Command Alarms
were staying active even though the command was successfully processed. |
|
Operational Report |
When an ATS did not have the Time
to Available tag then the ATSs were not being displayed on the report. |
|
EPMS System Error |
When the emergency power supply
system has a generator with a ENGINE_NOT_IN_AUTO tag as null and the
Control Manager detects the test bit as high, then the application displays
an ERROR on the EPMS page (rotating with TEST status). The test completes
normally. |
|
Login/Default Home Page |
After logging into the application
displayed a blank screen when the configured default home page should have
rendered. |
|
Runtime Formulas |
Runtime Formulas that Cross
Multiple Devices were Not Updating with Correct Device Reference. |
|
Installer |
Updated the Installer to
drop/remove tables and stored procedures that no longer are needed. |
|
Project Frog Integration |
Project Frog External Integration
was missing data for mapped tags for a period. The Integration Request
Data has been changed to use Hawaii Standard Time to fix the issue. |
|
Alarm History Stored Procedure |
The Alarm History stored procedure
was not filtering out inactive tags. As a result, a 500 error was
produced in the API Log. |
Related Articles
Aurora On-prem Release Notes v5.12
Aurora On-prem Supported Web Browser Notification Upon accessing the Aurora Platform the application will check the internet browser being used and will display a warning message if the browser used is unsupported. The official supported web browser ...Aurora Application Programming Interface (API)
API Filter The API exists as an endpoint on the Aurora Server and allows for the retrieval of live and historical data by filter or individual tag. A filter can be created in Aurora by grouping a set of tags together for retrieval through the API. ...Aurora On-prem Release Notes v6.1
Aurora On-Prem Web Browser Since the retirement of IE 11 our new supported web browser is Google Chrome. Generator Monitoring via Camera The embedded frame for the web camera in the EPMS screen and the Generator details has been replaced with ...Aurora On-prem User Guide v6.1
To view the Aurora On-prem User Guide select the download option below.How to run an Alarm History Report
Alarm History Report Historical Alarm information is available in the Alarm History report. It can provide Active and Inactive Alarms and Acknowledged Alarm Dates and Cleared Alarm Dates How to generate an alarm history report: Select the reporting ...