Good day, Hikers! The first thing you might notice is that the build number is a bit larger than the previous build number! This was done to ensure that the Standard and Enterprise versions of the package have the same number for the same release.
Another thing clients who have been with us for a while might have noticed is tab changes. We introduced the DS Admin and DS User tabs back in Release 3.4, but continued to support the legacy tabs of DS Dispositions, DS Campaigns, DS Recordings, and DS Queues. However, the time has finally to discontinue support for the legacy tabs. DS Recordings and DS Queues are now housed within the DS User tab; DS Campaigns and DS Dispositions are now housed within the DS Admin tab.
This release includes two substantial features for Denali 2.0 for Salesforce, and some exciting news for our Denali for Dynamics clients.
Denali for Salesforce
You asked, we delivered: several clients have requested the ability to create a follow-up task for themselves without having to leave the call they're on. With version 7.1, we now offer seamless Task creation with the click of a button.
For more detail on how this feature works, check out our Denali 2.0 for Salesforce User Guide!
Package Update: Yes
DS Backend Setting: No
Paid Feature: No
Disposition Unlinked Calls
We now support the ability to disposition unlinked inbound calls. Previously, all calls needed to be linked to a record in order for the user to select a Disposition. However, there are some use cases where a user won't want to link the call to a record, such as a wrong number.
To facilitate this, we've added a checkbox to the Disposition Options menu, which allows individual Dispositions to be available on unlinked calls. If "Disable when linked" is selected, the Disposition will no longer be available once a call has been linked to a record.
An unlinked call with a Disposition will log an activity like any other logged by Denali, it simply won't be associated with a record.
Package Update: Yes
DS Backend Setting: Yes
Paid Feature: No
Denali for Microsoft Dynamics
COMING SOON: Denali 2.0 and Web Based Application for Dynamics
We've received a lot of positive feedback on Denali 2.0 for Salesforce, and are excited to announce that soon this will be available to our Microsoft Dynamics clients as well. In addition, Denali 2.0 will be native in the Microsoft Dynamics web application.
This provides a variety of benefits:
- It is no longer necessary to download and maintain the latest version of a separate DialSource Denali app. Most updates will not require any customer intervention. The small subset of updates will be package updates, which will apply at the org level.
- Configurations are now supported at the org level and the updates cascade down to users from the org.
- A notably improved user experience with navigation, go to active record and campaigns features.
- New features:
a. Call Waiting (See Call Waiting Guide).
b. Create Task (as above in the Denali for Salesforce section).
c. Place a call from the Call History by clicking on the phone number.
We're in the process of migrating our client base to Denali 2.0, an exciting undertaking. Your Customer Success Manager will be reaching out to you soon to schedule some time to upgrade you. But if you just can't wait, drop them a line to schedule your upgrade appointment!
The following tickets are resolved in this release:
|DEV-3368||inaccurate call result|
|DEV-3399||Dynamics UI Bug: Pop-Up Blocker Error Box But Still Displays Requested Info|
|DEV-3424||Inbound Ready to be respected only for the Record Owner - Otherwise Exclude Offline Agents|
|DEV-3426||Telephony Carrier Issue: Disconnecting Sessions Prematurely After 3 Hours (180 Min)|
|DEV-3432||Agent unable to call out via click2dial|
|DEV-3445||Add # of call Answer Column to Dashboard.|
|DEV-3494||Add closers to Call Waiting|
|DEV-3620||DTMF Error & Example of Voice Not Detected When Leaving Voicemail|
|DEV-3631||Inbound Call Delivered Out of Order|
|DEV-3637||Another stuck in inbound-locked issue post|
|DEV-3757||Delays in Leg B Audio on outbound calls|
|DEV-3769||Calls not logging|
|DEV-3776||TSO Drop Down Update|
|DEV-3830||Call Back - Follow up Task|
|DEV-3839||Migrate Inbound DIDs|
|DEV-3856||Ring No Answers logging Call Duration blank|
|DEV-3864||Dispos performed on converted leads should traverse to the new object|
|DEV-3930||Add logging to process dispo for inbound statistics|
|DEV-3931||Call rings once and hangs up immediately.|
|DEV-3937||Allow call logging against Salesforce "Account Contact Relationship" junction object *NEW UI|
|DEV-3939||Update SF DNC in Denali 2.0 Lightning|
|DEV-3940||Dynamics - Calls Not Logging|
|DEV-3956||Fix the Cursor Options Error From The Dial In Token|
|DEV-3957||Make The Dial In Token Persistent Across User Setting Rather Than Agent Status|
|DEV-4004||Clean up prepend of Sales Notes field|
|DEV-4063||fix agent ended when agent state history logging is enabled|
|DEV-4064||Support Linking multiple object on 1.0 (backend)|
|DEV-4070||Fix Inbound Ready with DLD on Denali 2.0 softphone|
|DEV-4076||Disposition unlinked records|
|DEV-4122||Intermittent delays in call/notes logging|
|DEV-4165||Dynamics App: Cannot Load Any Records (Loading business logic message)|
|DEV-4168||Make CSS files in new Softphone dynamic|
|DEV-4169||Completed calls are getting Canceled status|
|DEV-4185||Agent vanished from Agent List|
|DEV-4218||Follow up time issue|
|DEV-4226||Support Datadog Dashboard|
|DEV-4231||Campaign Creation issue|
|DEV-4237||Follow up tasks for Dynamics|
|DEV-4238||Add Connecting State while agent is connecting|
|DEV-4263||Inbound Ready object record wrong|
|DEV-4271||Campaign Memory Issue|