Date of release
Summary
| Excerpt | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stale entry boundary for "single list" dial lists (Enhancements)
Enabled by default.
Agent changes
In version 22.116 unscheduled refreshes of dynamic "single list" dial lists were limited to allow only a single agent to initiate an unscheduled refresh at a time.
This change (22.117) introduces the concept of a stale dial entry boundary that prevents agents from working with dial entries that may no longer be valid.
This boundary is set at the time defined by the dial list's Max Cache Expire Time. Dial entries older than the boundary are considered stale while dial entries created or updated more recently are considered fresh.
While an unscheduled refresh performed by a single agent is underway, other agents working from the same list who request stale dial entries are affected in the following way:
- Prior to this change, stale dial entries would be accessed by agents
- After this change stale dial entries are no longer accessed by agents and instead, if available, they will access a fresh dial entry from a lower priority list
Salesforce administrator changes
A new custom field NVMConnect__FreshAt__c is added to both NVMConnect__PendingDialEntry__c and NVMConnect__ActiveDialEntry__c.
This is a required DateTime field and as such there is no need for this to be added to permission sets.