History of changes

2018-07-07 - Changes to tenant.fieldset_licensing attribute.

Per-tenant license configuration is improved. Previously, it was possible to set "First-come, first-served" licensing mode for "call recording" licenses only. Other licenses were fixed. In this release, all licenses can be be either dynamic or fixed. A configuration section is renamed to "License limits".

Before:

Now:

Changes to REST API:

Old version:

{
    "tenant":
    {
        "fieldset_licensing":
        {
            "license_mode": "dynamic",
            "recording_seats": -1,
            "screen_recording_seats": 0,
            "monitoring_seats": 10,
            "evaluation_seats": 20,
            "speech_analytics": 20
        },
        ...

New version:

{
    "tenant":
    {
        "fieldset_licensing":
        {
            "recording_seats": null,
            "screen_recording_seats": 0,
            "monitoring_seats": 10,
            "evaluation_seats": 20,
            "speech_analytics": 20
        },
        ...

A tenant's licensing configuration (attribute fieldset_licensing) has the following changes:

• Attribute license_mode is depreciated. It is ignored when supplied in PUT/POST requests. It is not returned in GET requests.
• null can be set to any of license types. null value means no limits.
• dynamic license (no limits) is supported to any of license types.

In previous versions, a license_mode attribute might have one of the following values:

• fixed - A particular number of licenses is pre-allocated to this tenant. Tenant cannot use more license then pre-allocated. If the tenant has more users, then licenses, then call recordings for some of users will be unlicensed.

• dynamic - First-come, first served (FCFS) strategy. Licenses are dynamically allocated to tenant from a global pool. Tenant is allocated dynamically as many licenses as it has users with appropriate license configuration.

New version still allows to use First-come, first served strategy for license distribution, but terminology is different. Instead of license mode, a term license limits is used. Value null or -1 (for backward compatibility) means no limits, values from 0 to N sets an upper limit for tenant for particular license type.

For backward compatibility, you can supply license_mode attribute in PUT/POST requests and set license counter to -1 when a dynamic mode is desired. The following example has the same effect on both old and new versions:

"fieldset_licensing":{ 
    "recording_seats": -1,
    "screen_recording_seats": 0,
    "monitoring_seats": 0,
    "evaluation_seats": 0,
    "speech_analytics": 10,
    "license_mode": "dynamic"
}