Change Logs

Enhancements

• Updated SSL Cipher Suite
• Implement Additional Differential Pressure Units
• Audible Calibration Alarm was replaced with a calibration alarm pop up
• Downloading data from TSB using DicksonWare 2.0 with USB cable
• Add Sensor Port to Readings Packet
• Added backup settings to prevent devices from resetting their own settings

Bugs

• Enterprise Connection attempts Authentication with Username GSN
• Alarms triggered at alarm set value
• Sensor swaps caused device reboot
• Logger would not report model SKU to DicksonOne
• Calibration warnings on the device displayed the wrong port number
• Clearing the Min/Max with a probe error caused high Min/Max values
• Device does not boot up from a low power state
• Parse Incoming Proxy Settings through API
• New channels are not created properly when swapping different sensor models
• Device does not send readings packets while still sending ping and configuration packets
• Units lock up and reboot

This release of marks the initial production release for the RFL’s 1.0.0 production firmware.

Security and Performance

• New account security defaults were released to provide proactive guidance to new accounts.
• Security improvements to the system were made.

Bug Fixes

• A bug regarding reference lines not displaying on the device graph was fixed.
• A bug regarding communication issues regarding RF loggers when using the audible notification as part of a low-battery alarm was fixed.
• A bug regarding the SSL fingerprint algorithm not updating properly via SSO will be fixed.
• A bug regarding export download-links in emails for accounts that have SSO enforced was fixed.

User Experience

• The delete user/contact confirmation pop-up was updated.
• A column was added to the manage gateways page to include firmware version details.
• Archived devices are now removed from alarm templates when they are archived.

Reports

• An alarm coverage report was introduced to allow users to get a system-wide view of their devices, which alarms are applied to a device, and schedules for those alarms

Calibration

• A 3-month calibration interval was added to device settings

User Experience

• The delete device confirmation pop-up was updated to provide explicit details that warn users before taking action
• An update to the back-to-normal email notification for device not-reporting alarms was made to eliminate the most recent reading from the email

Bug Fixes

• A bug that prevented users with manage access from registering RF loggers was fixed
• A bug that prevented RF loggers to be replaced via the replace functionality was addressed
• A bug that causes warnings to be captured in tabular reports was fixed
• A bug that interfered with manual device data uploads was fixed

RF Logger System

• The site’s wording was updated to support the RF logger
• A battery icon indicator for RF loggers was added
• A low-battery alarm was introduced for RF loggers
• RF logger firmware versions are captured in manage devices
• Support for RF logger firmware files was added to the changelogs
• RF gateways now support Over the Air (OTA) software updates

API

• The REST API was updated to display if devices were replaced
• The REST API now allows users to include or exclude replaced devices

Performance and Security

• Site performance was improved so that the users and contacts page can load efficiently for users
• An update was made to reporting to ensure continued performance
• Security improvements to the system were made

Twilio Integration

• An adjustment was made for the handling of Twilio account verification requirements to better support the integration

Alarm Schedules

• Alarm schedules are introduced to allow users to schedule alarms to monitor during specific timeframes (days and hours) or remain active 24/7
• An optional buffer for alarm hours was released so that alarms can be evaluated prior to an alarm schedule starting
• After-hours notifications feature was added to alarm schedules so that users can determine if they should be notified when alarms are resolved after an alarm schedule has ended
• An alarm coverage calendar was added so that users can view a snapshot of a device’s alarm configuration and corresponding schedule
• Events will be updated to support the rollout of alarm schedules

Note: All existing alarms are configured with a schedule set to 24/7 unless edited by a user.

Bugs

• A bug that caused inaccurate times to be displayed in Alert annotations was fixed. 

User Experience

• Back to normal alert notifications for alarms (to the same recipient) are now grouped together when escalations are in use.
• Events have been updated to include details when users opt-in and/or opt-out of subscription newsletters. The integrations page now allows users to select a recipient for when their Twilio rate limit for SMS/Text and Phone Call notifications has been reached. The integrations page now provides SMS/Text Message and Phone Call notification metrics.

Radio Frequency Logger (RFL)

• New code was released to support the expansion of the DicksonOne product line by introducing the Radio Frequency Logger (RFL). 
• The Unassigned Nodes page was added under Manage for users who will register RF Loggers.
• The Gateways page was added under Manage for users who will register RF Gateways to be used in combination with RF Loggers.

Bugs

• A bug that caused reseller codes to be excluded during the account creation phase was fixed.
• A bug regarding locations not loading due a excessive (200+) active alarm events was resolved.
• A bug that caused the wrong time stamp to be displayed on the graph for not reporting alarms was fixed.

User Experience

• A Monitoring Points section was created within the locations view to better represent the devices that live within each location.
• A manage locations button was added to the locations view for easy access to editing, adding and reviewing locations.
• New code was released to support future developments.

Twilio Integration

• A Twilio integration was released to support global accounts that send SMS and Phone Call notifications to the following country codes and accounts will be flagged on DicksonOne if the integration is required.
• Users have the option to connect their own Twilio account to DicksonOne if they wish continue to send SMS and Phone Call notifications.

Note: If you do not have any users or contacts in a region that requires a Twilio integration, you do not have to do anything with your account and full functionality will continue as normal.

Bug Fixes

• A bug that caused alarm notification emails to include the wrong unit for the current value was resolved. 
• A bug that caused odd characters to be displayed in event logs when making changes to the account datetime format was resolved. 
• A bug that caused the wrong device value to appear in expiring subscription email reminders was resolved. 
• A bug that caused poor resolution of certain channel colors on the graph was resolved. 

User Experience

• An adjustment was made to excursion events that appear on reports so that the events follow the account’s datetime format.
• The settings pages were updated to include only the save, archive, and delete buttons where appropriate.
• Alarm template events are now grouped together when users apply and/or remove multiple devices from the template at once. 
• Alarm template events were updated so that they capture details regarding notification policy updates.
• New code was released to support future integrations and developments. 

Bugs

• A bug in which datapoint values in Fahrenheit are incorrectly converted to the Celsius value as part of the Email subject line in notification alerts was resolved
• A bug in which email addresses are not updated for monthly credit card subscription invoicing was resolved
• A bug that prevents account managers from being able to edit existing users on their account was resolved
• A bug regarding password verification through system checks was resolved
• A bug that caused erratic dates/times in device exports was resolved

Performance

• Manual data uploads to devices was improved
• Site performance regarding user and contact records was improved

User Experience

• Sorting users and contacts by Name, Last Name, Role and Location via the search bar is now available
• A warning message to inform managers when an email address for a user that is being added is already taken was implemented
• Additional context for events that pertain to user lockouts in the Events page was added
• Details regarding the permanent effect archiving has within the archive device confirmation modal were updated
• New code was released to support a future integration for Text Message/SMS and Phone call notifications to all global regions
• The Delete Device functionality has been moved to the Device Settings page where users can either Archive a device or Delete a device
• Compare Devices functionality has been removed from the Device Overview page

Bugs

• A bug in which the system did not require a password when a user updated their current password was fixed
• A bug that caused an error page to populate when a user updated their password was fixed

Performance Upgrade

• Changes to the codebase were made to address performance issues pertaining to Users & Contacts

Bug Fixes

• Fixed a bug that prevented event logs to not be displayed when using filters in the events page via Internet Explorer
• Fixed a bug that caused Google Chrome to use HTTP instead on HTTPS for DicksonOne.com
• Fixed a bug that caused inaccurate details to be displayed in the event logs when users make changes to account security settings

User Experience

• Customer account ID’s are now provided in My Profile on DicksonOne
• The summary data timestamp in reports was adjusted so that the timestamp reflects the account timestamp format, e.g., MM/DD/YYYY versus YYYY/MM/DD
• The calibration date found in the device settings page via sensors has been adjusted so that it respects central time
• An update to Single Sign On (SSO) has been made to redirect users to their respective IDP URL when clicking log out
• Event logs for when automated reports become inactive by the system has been added to the events page

Users and Contacts

• The Users and Contact Book pages have been merged together to live as one page called Users & Contacts
• The user and contact creation card has been merged into a single card
• When adding an individual to DicksonOne, you will first input the individual’s contact information and then determine if the individual will be a contact or a user of the system
• Helper text has been added to the user/contact creation card to provide better guidance to users
• Users with manage access permissions are now able to add and edit contacts
• The suspend functionality available to account owners only was removed as user access can be removed by disabling location permissions for users