Change Logs

Bug Fixes

• Resolved a bug where ping packets did not update a configuration timestamp, potentially triggering Not Reporting alarms

Bug Fixes

• Resolved a bug where users with their time zones set to Puerto Rico time zone resulted in Error 500 
• Resolved a bug where Monitor Equipment tiles did not display with the appropriate temperature unit conversion
• Resolved a bug where the Alarm Coverage Report truncated the “paused” status when rendered as a PDF
• Resolved a bug where updating configuration settings to audible alarm templates were being delayed
• Resolved a bug where the Audit Trail captured Equipment exports as Account exports
• Resolved a bug where alert notifications (SMS / Phone Call / Email) did not include information about the connected equipment
• Updated Spanish and French translations of the application

Design Update

• Updated icons in the sidebar navigation menu from outlined icons to filled icons
• Updated the icons for Overview and Manage in the sidebar navigation menu

Bug Fixes

• Resolved a bug where creating a report returned an Error 500 if the account did not have any equipment created
• Resolved a bug where equipment relied on an unindexed database column resulting in a performance issue
• Resolved a bug where users experienced issues editing some of their alarm templates 

Sensor Support

• Updated support for universal 4-20mA sensor to include support for 0-10V
• Added ability to configure logging and displaying the universal sensor data in either voltage or current on DicksonOne

Mobile App Support

• Updated the REST API to enable mobile app support for Locations, localization, alert filters, and unit conversions

Bug Fixes

• Resolved a bug where Min/Max lines on DicksonOne were appearing in a solid color instead of lighter shade of the color
• Resolved a bug where temperature unit conversions on the mobile app were not appearing as expected
• Resolved a bug where Daily Temperature Check reports with more than 35 days were incorrectly truncated when exported to PDF
• Resolved a bug where Not Reporting alarms were being delayed in certain alarm configurations

Design Updates

• Renamed “Event Log” to “Audit Trail”
• Renamed “Device(s)” to “Data Logger(s)” throughout DicksonOne
• Renamed “Register New Hardware” to “Add Hardware”
• Renamed “Coverage of this device” to “Alarm Coverage”
• Updated order of items in the sidebar navigation so that “Calibration” is moved between “Reports” and “Audit Trail” (previously “Event Log”)
• Added the ability to edit a sublocation’s settings from the Monitoring Points > Location page
• Added the ability to choose displaying the Sublocations section of a Location in a compact, horizontal view or a list view
• Added the ability to add hardware from the Data Loggers page (previously “Devices”)
• Added a breadcrumb trail of a data logger’s location to the Data Loggers page
• Updated the “Add a New Alarm” button (which previously displayed two tabs) into two separate buttons “Add a New Alarm” and “Apply Alarm”
• Added additional attributes for filtering from the Manage Sensors page, such as sensor serial number, data logger, and location
• Updated design of applied alarms to a tabular format on the Alarms tab of the Data Loggers and Channels pages
• Updated the Pause button for applied alarms to a switch
• Refactored fonts and color scheme to adhere with DicksonOne’s updated design styles
• Updated Overview dashboard design
• The red and yellow highlighting that previously displayed on Manage > Sensors page when clicking the “Sensors due for Calibration” widget has now been replaced with a “Cal. Due Date” filter that filters the sensors by calibration due date

Equipment View

• Added Equipment as an additional (but optional) Monitoring Point model for organizing data logger channels. New functionality introduced as part of this include:
  • Ability to create a piece of equipment and connect data logger channels to the equipment
  • Ability to view a list of all equipment from the Monitoring Points page
  • Ability to sort, search, and filter sensors by equipment
  • Ability to monitor and annotate the current channel readings and alerts by equipment
  • Added the equipment type as a column in the Alert tables so that when alerts are triggered, any associated pieces of equipment are identifiable
  • Added events for equipment to the Audit Trail (previously “Event Log”)

Bug Fixes

• Improved the visibility of available networks for provisioning with the FollettConnect APP.

Bug Fixes

• Resolved a bug where additional channels were created after a sensor was swapped at the device (note: there are scenarios where new channels can be created due to older devices or firmware limitations)
• Resolved a bug where the Factory Calibration Date appeared as “Unknown” after a sensor was swapped
• Resolved a bug where a LoRa gateway couldn’t be re-registered after being deleted from an account
• Resolved a bug where reports were sending on a future date (if your report(s) still show the wrong starting date, we recommend deleting and recreating the report)
• Resolved a bug where invalid characters prevented report emails/attachments from delivering correctly

Bug Fixes

• Resolved a bug where additional channels were being created as part of a sensor swap and cleaned up legacy sensor mapping code for RF devices
• Resolved a bug where Twilio messages weren’t being initialized correctly
• Resolved a bug where reports were not respecting the configured start and end times and cleaned up report scheduling logic

Rest API

• Simplified login page for mobile app workflow
• Include more detail in API search results
• Include date/time format in REST API user serialization

Support for Component Replacements

• Added backwards compatible support for new flash memory chip
• Updated bootloader to support new flash chip

Bug Fixes

• Updated the wording around copying a calibration as part of user calibration
• Resolved a bug where the channels from an archived sensor were not retired correctly
• Resolved a bug where reports that hadn’t been started were showing in the results
• Resolved a bug with form submission when performing bulk updates
• Resolved a bug preventing locations from being dragged and dropped on the Manage > Locations page
• Resolved a bug where archived legacy loggers couldn’t be re-registered
• Resolved a bug where the email and chat links from the Support menu weren’t working
• Resolved a bug where the system was expiring passwords despite SSO being forced

REST API

Note: these changes do not affect the front-end application. If you validate the REST API as part of your processes, then there is a Low impact.

• Update warning and excursion naming conventions in the REST API to support differentiation between severity for alerts
• Updated the device route to include location information
• Added device count to locations relationship
• Added channel count to device’s relationships
• Rest API User routes now include locale info2

Bug Fixes

• Resolved a bug where recipients couldn’t be added to reports
• Resolved a bug where the graph wasn’t properly displaying values equal to 0
• Resolved a bug where the sensors page was displaying replaced loggers name instead of new logger
• Resolved a bug where the list of devices shown on the Locations view weren’t saving their order
• Resolved a bug where a swapped sensor was still shown as current sensor and updating last reported at time
• Resolved a bug where the background of some reports was red
• Resolved a bug where claimed RFLs wouldn’t appear as registered until after the page was refreshed
• Resolved a bug where flags for annotations and alarms on the graph were not displaying their contents when hovered over
• Resolved an issue where some reports were failing to generate
• Resolved an issue where data was loading on the graph but the the graph indicated it was still loading
• Resolved an issue where users who utilize SSO were only seeing raw HTML and not seeing styled pages
• Corrected the styling of the filter on Manage > Sensors
• Made graph generation more resilient when connecting to the database

Security Enhancements

• Increase version of UI component
• Increase version of backend monitoring component
• Increase version of component that aids in displaying information that had been previously sanitized