Release Notes for version 18.246 of Connect 2018-08-16 (Enhancement & Bugfix)
Date of release
Summary
Dial List Locking Improvements (Enhancement)
Your System Admin must complete some manual steps to enable this change. For information about these steps, see Upgrading to latest version of Connect.
Salesforce administrator changes
This package completes a data migration process to move away from a Master-Detail relationship between Dial List Agent and Dial List to prevent unnecessary locking issues that may affect larger customers. Customers will be provided with manual steps to perform following this upgrade. For more information, see Upgrading to latest version of Connect.
When creating a Dial List, specify the phone fields the Progressive Dialler will automatically dial (Enhancement)
Enabled by default
Availability
The change to Dial List creation affects both Vonage Contact Center for Sales Select & Premium
Automatically progressing to the next call is only available with the Progressive Dialler.
Agent changes
When an agent uses Connect to dial, for example, a Contact then Connect previously used a phone number copied from the Contact at the time the Dial List was created or refreshed.
Now, Connect dials using phone numbers taken directly from the record related to the dial entry.
If the Progressive Dialler is enabled, after a call is dispositioned with a disposition code configured with the Next Call progression mode, Connect automatically dials the next number using order defined for the dial list.
Supervisor changes
When creating or editing a dial list a supervisor no longer chooses the primary and secondary phone fields. Instead the supervisor can now specify several phone fields in the order they should be dialled.
When creating a dial list from a filter the phone fields are selected on the second screen of the dial list builder rather than the first screen.
You can also chose phone fields from objects related to the chosen Dial List object type, for example, when creating a list of Contacts, you can select phone fields from Account.
Handling records without phone numbers, deleted and inaccessible records
When an agent activates a dial entry, in the following two cases the dial entry will be automatically skipped and an unassigned processed dial entry will be created with an explanation appended to the description.
- The dial entry is for a record that has no phone numbers in the fields specified by the Dial List
- The dial entry is for a record that has been deleted or that the agent doesn't have access to.
Salesforce administrator changes
There is no longer any need to configure the picklist dependencies between the VCCConnect__DialList.VCCConnect__Type__c field and VCCConnect__DialList.VCCConnect__Primary_Phone_Field__c amd VCCConnect__DialList.VCCConnect__Secondary_Phone_Field__c.
When installing this package an upgrade script runs to migrate Dial Lists from the old to the new way of defining Dial List phone fields.
Connect Component UX/UI Enhancements
Your System Admin must add the Connect component or adjust its height
Agent changes
New look and feel in Salesforce Classic
In Sales Cloud and the Service Cloud console the Connect component has been updated inline with the current Vonage Contact Center branding.
Stop button user experience
Previously clicking Stop during a call would have no effect.
Now, if Stop is clicked during a call, the Dialler displays "stopping after current call" and stops automatically when the call ends.
This enhancement make it easier for Progressive Dialler users to finish their work.
Bug fixes
We resolved the following issues:
- The Connect component is designed to automatically skip a dial entry without phone numbers. An error occurred when updating dial list stats that caused the dial entry, with no numbers to dial, to be presented to the agent.
- An error that occurred when updating Next Contact Time for a dial entry for which the focus object was no longer available.
- Under some circumstances the Connect component would display an error "Record Currently Unavailable" due to locking the record used to assign an agent to a dial list, we have reduced the frequency with which Connect locks this record.
- An error that occurred when Connect attempted to activate a dial entry for a record that the agent has no access to.
- When clicking the 'Next' button in the Dialler while an agent is logging the call, the Dialler will handle a race condition which previously could result in an error.
Salesforce administrator changes
Your administrator must complete the following configuration tasks
Salesforce Classic
Configure the Connect console component to a height of 185 pixels (see Adding Connect to a console app in Salesforce Classic).
Lightning Experience
Configure the Lightning Utility Bar for the Dialler to a height of 220px (see Adding Connect to the utility bar in Salesforce Lightning Experience).
Enabling Features (Enhancement)
The following pilot and optional features have been simplified in this version
Progressive Dialler
This functionality must now be enabled for your Vonage Contact Center account. Please speak to Vonage Contact Center to enable this feature.
Custom Settings Flags
The following flags can be safely removed after upgrading to this version:
Flag | Description |
---|---|
USE_PRE_CALL_INTERACTION_EVENTS | This flag no longer has any effect and can be removed |
MULTI_LIST_CLIENT_CONTROL | This flag enabled a performance enhancement for the Connect component that is now the default behaviour |
DISABLE_SYNCHRONOUS_REFRESHES | This experimental feature has been removed |
DYNAMIC_PHONE_FIELDS | Previously enabled pilot functionality which is now the default behaviour |
ENABLE_PROGRESSIVE_DIALLER | This flag no longer has any affect and can be removed |
For general assistance, please contact Customer Support.
For help using this documentation, please send an email to docs_feedback@vonage.com. We're happy to hear from you. Your contribution helps everyone at Vonage! Please include the name of the page in your email.