V-Spark Online Help

V‑Spark 3.4.1 Release Notes

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

  1. Call Tagging - makes it easy to identify specific transcriptions or the results of previous searches by enabling you to apply a tag (a logical label) to them and then subsequently search for transcriptions that are associated with that tag

  2. User management enhancements - more granular permissions and a substantially enhanced GUI simplify setting new and existing permissions and associated roles. These user management improvements are also reflected in the updated REST API, as described later in this section.

    If you are upgrading from a previous release of V‑Spark, existing user permissions will be converted into those that work with the new permissions model, as shown in the following table:

    Table 1. Mapping Between pre-3.4 and 3.4 Permissions

    Pre-3.4 Permission/Role

    3.4 Permission/Role

    Admin

    System admin

    Manager

    Create/Edit rights on all organizations that they had been given access to within the company under which their account was created (their home company). View rights on any other organization that they had access to

    User

    View rights on any organization that they had access to



  3. RESTful API - Phase 2 - significant API enhancements make it easier to deploy and manage V‑Spark programmatically:

    1. Enhanced user permissions provide easier delegation of administrative responsibilities within a V‑Spark deployment and increase data privacy by separating administrative roles from the ability to view data

    2. API access to daily overview and agent application statistics makes it easier to extract reports and use extracted data in third-party reporting applications

    3. Applications can now be created and modified programmatically, making it even easier to use, customize, and deploy applications from templates or simply from outside the V‑Spark environment

  4. Expanded email configuration for partners - Email templates and improved configuration files make it easy for partners to customize system email sender and content

  5. Trending support is disabled - terminology trend tracking and analysis is now disabled by default, based on its limited use, capabilities, and impact on system performance. We have decided that it needs additional development in order to perform as originally envisioned. At this point in time, this additional development is not a line item in our development plans. The current implementation and of tracking and analyzing terminology trends can be re-enabled by an administrator who has access to the V‑Spark installation, by modifying the V‑Spark configuration file. Re-enabling the current implementation of trending support is not recommended.

  6. End of day prediction for call volume (also referred to as "predicted overall volume") is no longer performed.

  7. Company modification via API requires root token - a company authentication token does not provide sufficient privileges to modify a company itself.