Viakoo Release Notes 2.2
(November 19th, 2015)
Viakoo Release 2.2 is an incremental step forward for the Viakoo Service. Most of the improvements are in the form of bug fixes or performance improvements.
Status Report Summaries
The Status Report, which many of our users subscribe to on a daily basis, now has a summary section at the top which enumerates the user’s number of tickets, servers, cameras and switches by site and by status.
The summary section will quickly highlight the number of tickets you have, including how many of those are currently unassigned, as well as the current state of your servers, cameras, streams and switches. These are all separated on a per-site basis to help you quickly diagnose where your problem areas are.
From the navigation pane you can see HBF (aka “Heart-Beat Freshness”) for each Site or Server, which represents how long it’s been since we last received data from your site or server. Historically, this number only changed when the current page in the WebUI was loaded. This had the possibility of confusing people within a few minutes of looking at the display. In Release 2.2, HBF will now dynamically and continuously reflect the time since the last collection of data for the associated Site or Server..
Session Extension Changed to 30 Minutes
In prior releases a session would start out with a length of 30 minutes, and then would extend by 10 minutes each time you used a part of the service. In the new release sessions will now extend by 30 minutes, giving you a bit more breathing room while still logging you out automatically in a reasonable time frame.
Problems Corrected in Release 2.2
- In prior releases, Operation Reports would fail to complete if launched from a region of a company. This problem has now been corrected.
- Since the 2.0 release, if you were logged out due to inactivity, logging back in would take you to the ‘Home’ page, which required users to re-navigate to a location they were investigating. In release 2.2, if you come back to your browser to find that your session has timed out, entering your credentials on that same page will take you back to the last page you were working on.
- In prior releases, some camera streams would incorrectly calculate a value of 2 for days-of-retention when actually there was much more data accumulated. This was often a characteristic of streams that, due to lack of motion or other reasons, didn’t generate enough data to fully write an open buffer file in a single 48-hour cycle. This problem has now been corrected.
If you have any questions, comments, bug reports, or suggestions, please reach out to us through the live-chat feature or contact us at email@example.com.
We love hearing from you!
1 (855) 585-3400