Please note line items in releases only apply to standardized reporting, Insight documentation, or Insight itself at large. Updates made to custom reporting are not covered here nor made public. Your NocTel Insight Support Engineer or Developer should be providing normal communication on changes made to custom reporting.
The current release version is v1.0.20200630 and contains the following:
- Overall backend upgrade of NocTel Insight, which allows us to develop more effectively and with more stability. This change overall significantly modifies the NocTel Insight web app GUI - the layout has changed, but all prior functionality (icons, links, etc.) are still present. Updated documentation will follow shortly.
Previous Releases:
NocTel Flow - Fixed an issue in which multiple field filters were being applied to the same reports causing disjoint filter results in certain reports. This was most commonly manifest as selecting valid field values then seeing no matching data even though the filters applied were valid and matching data does exist. This release effectively rolls back v1.0.20200527.
|
NocTel Flow - Added fields to Agent Calls reporting that indicates how many calls that originated Inbound and/or Outbound (dependent on the Call Direction filtering setting) were transferred by the Agent. This was added to better inform supervisory users of agents who may potentially be mishandling calls. This implementation also lays the groundwork for future potential reporting uses.
|
NocTel Flow - Refactoring of reporting fields for NocTel Talk.
- Improvements to NocTel Flow standard reports to provide subtotals and totals in tabular reports where appropriate.
|
NocTel Flow - Found the calculations for Average Talk Time and ACD (Sec) in Talk Time Flow reports are inaccurate as the two columns were using different criteria to evaluate the metric. A slight change was made to the logic of the fields and replaced the incorrectly and inconsistent logic causing the issue.
|
NocTel Talk - Modified Numbers on Account to add info on what the Confirmed column indicates.
- Added informational tooltip fields to Accounts on Extension to inform on when extensions where added/deleted.
|
NocTel Insight - Rough designing of standardized reporting dashboards intended to be oriented toward different varieties of users to simplify reporting navigation. e.g.: an operations user who is concerned with whether extensions are online doesn't necessarily care how many calls occurred on the account.
NocTel Talk & Flow - Added support for major US domestic time zones. This currently does not specifically address states like Arizona which do not observe DST or other domestic regions that may be the exception in an otherwise well-defined geographic region/time zone.
|
NocTel Talk - Removed the data selectors for Phone Numbers on Account as in many cases you would need to set a very distant Start Date to get results. Because Start Date and End Date parameters are universally used in the reporting workbook, this can cause undesirable navigation between reports. For Phone Numbers on Account the default behavior is to list all numbers on the account (owned by the account)
|
NocTel Talk - Added additional dual axis chart variations of reports. Dual axis reports will not include subtotals or overall totals.
NocTel Insight Knowledge Base |
NocTel Insight Knowledge Base - Many additional documentation sections added for this KB.
NocTel Flow - Heat mapping has been implemented for several tabular NocTel Flow reports. Each column/field is evaluated overall in the full rendered data range separately. That is, the heat mapping applied isn't directly comparing and shading Inbound Calls relative to Outbound Calls. Some things to be aware of for this:
- While several columns/fields use the same legend color banding, they are not being compared to one another. This was done to prevent chromatic overload making the heat mappings unpleasant to look at and may be unfriendly to colorblind users.
- Reports that provide both an Average Talk Time as a time-format and in seconds necessarily need both columns present. In time-format Insight cannot interpret the values in the context of "time as a number" and therefore can't be measured.
- Adjusted the view sizing perspective to always adhere to Fit to Width. Several reports were defaulting to a standard perspective, which does not make consistent good use of screen real estate.
NocTel Talk - Adjusted the view sizing perspective to always adhere to Fit to Width. Several reports were defaulting to a standard perspective, which does not make consistent good use of screen real estate.
|