V‑Spark 3.3.1

This section provides release notes for V‑Spark 3.3.1, describing new features and capabilities that were introduced in the 3.3.0 and 3.3.1 versions of the product. This document also provides information about Known Issues in 3.3.1 with V‑Spark 3.3.1 that could affect your use of the product.

V‑Spark 3.3.1 Release Notes

V‑Spark Version 3.3.1 provides performance, usability, and stability improvements, and also provides significant API enhancements.

  1. Added new REST APIs to enable programmatic access to V‑Spark configuration and settings. The APIs added are /config , /list , /logs , /search , and /status . See the "Using the V‑Spark 3.5.0 API" for more information.

  2. Created an online, searchable version of all Voci documentation that can be used by Voci customers, prospects, and employees. PDF documentation can still be referenced or the online documentation can be linked to from the V‑Spark Help menu. The online documentation is built from the same content that is used to produce Voci's PDF documentation. Access to the online documentation requires the ability to access the documentation web site and an account in Voci's portion of Salesforce.com.

  3. The Elasticsearch software used by V‑Spark was upgraded, enabling easier integration of V‑Spark with external reporting tools.

  4. Improved definition and display of speaker turns generated from V‑Spark's Automatic Speech Recognition (ASR) utterances

  5. System-wide announcements can now be set by an administrator so that they are visible to anyone who is using V‑Spark

  6. V‑Spark now supports a read-only mode that enables maintenance and diagnostic tasks to take place while users can still view and explore existing data. No new audio can be added or processed while V‑Spark is in read-only mode.

  7. The Settings menu's Folders page now provides graphical controls that enable you to pause and continue processing. Pausing file processing enables current processing operations to complete, but no new processing can be done until the continue portion of the pause/continue control is selected.

  8. Improved folder processing status, enabling folder views to be sorted by time (most recently processed). V‑Spark now also provides access to the folder processing log queue, enabling users to see which folders are waiting to be processed, are currently being processed, are waiting for analysis, or have encountered errors during processing.

  9. Reporting has been enhanced to provide access to more data, such as a table that provides agent summary information

  10. The File Details page now:

    1. displays overtalk with blue edge highlighting in the transcript and correspondingly displays overtalk scores in blue text

    2. enables you to collapse client metadata so that the general details are easier to review

    3. provides information about the processing date of application scoring

  11. File metadata can now be displayed and used in Adhoc searches, rather than only being viewable on the File Details page

  12. Enhanced the Voci license server to improve robustness and responsiveness

Fixes in 3.3.1

This section identifies specific issues that have been resolved in the 3.3.1 release of V‑Spark:

  1. Fields within CSV reports that are exported from the dashboard are now quoted

  2. Improved reliability of application scoring and reprocessing

  3. RequestIDs are now correctly assigned and displayed when reloading existing Voci JSON files and associated MP3 audio

  4. Favicons are now correctly shown in V‑Spark pages in a web browser

  5. Configuration files enable partners to customize system email sender and content

  6. Highlighting on the File Details page now correctly considers word boundaries when interpreting regular expression phrases

Known Issues in 3.3.1

  1. Exporting large numbers of files (10K or larger) as CSV can take an extremely long time, and may not complete successfully. A suggested workaround when you want to export large file lists in CSV format is to subset those lists into smaller groups that you can subsequently combine in your target spreadsheet application.

  2. Calls to the /search API will only return custom metadata for matches if a folder has been specified. In other words, suppose that a call to the /search API matches files in folders under a company named Doc Test Co and an organization named Doc Testing, and that custom metadata is associated with a folder under that organization that is named Test01. Matching results in that folder that are returned by calling /search/DocTestCo-DocTesting will not contain any custom metadata, while matching results that are returned by calling /search/DocTestCo-DocTesting/Test01 will contain the custom metadata.

  3. Downloading JSON and MP3 data simultaneously for large numbers of files (5K or greater) can fail without that failure being displayed in the GUI. The size of the zip file created for downloading depends on the size of the files that are being included in the archive. A suggested workaround when you want to download transcripts and MP3 data for large numbers of files is to subset your download requests into smaller numbers of files.

  4. Issues with Dashboard Displays

    1. Stat summaries for dates in the past are not updated when files with historical timestamps older than the current day are loaded

    2. Files uploaded to a folder that is linked to a disabled application or that have not been reprocessed will still appear in the Files View on the application dashboard

  5. Issues with Search

    1. Time-based search

      1. Searches are turn-based and may return results for phrases that are outside of the requested timeframe, if they are within the same speaker turn

      2. Ad-hoc Search snippets in the Files View may display results outside the specified time interval

    2. Exceptions to standard File Details Highlighting (in order of severity)

      1. Searches using (~n) may highlight phrases with the specified number of words in between each of the search terms, rather than between all of the search terms. For example, "get help phone ~4" may highlight phrases with 4 words between "get" and "help" and another 4 words between "help" and "phone". Searches using (~t) and (~n) will only be highlighted if the words matched appear in the order specified in the search tag.

      2. Highlighting may be incomplete for matches marked with emotion

      3. Highlighting may be incomplete for matches with intervening silence tags greater than 2 seconds

      4. Matches for "@*" (such as when searching for email addresses) will only be highlighted until the first "." in the email address. Regular expression searches may be used to circumvent this issue.

      5. Excluded application search phrases may be highlighted on the File Details page. Note that these exceptions only affect highlighting, and that all search results using the above characters will still be accurate.

  6. Other

    1. The Trending View may take some time to fully load, especially for longer date ranges

    2. Users playing longer audio files via Firefox may encounter playback/syncing issues when jumping to different sections of the transcript. This is an external issue caused by the Firefox browser. Users who encounter this issue can simply wait for the browser to finish buffering the file before resuming their search.