Velocify Pulse 24.2 Major Release: Fixed Issues
This section describes the issues that have been fixed in this release.
Why we fixed these issues: These issues were fixed to improve usability and to help ensure Velocify Pulse is operating as expected. The issues that are chosen to be fixed are based on the severity of their impact to clients and client feedback.
Issues Resolved With This Release
The following issues were fixed with this release:
-
Dial-IQ [PULS-5833]: When inbound calls were re-distributed to new users, they were unable to view the record in their Dialer HUD due to private sharing settings. This has been fixed.
-
Sales Manager [PULS-6770]: Rep Activity Priority View Count sorted alphanumerically instead of numerically
-
Priority Views - User Assignment [PULS-1931]: During Sandbox refresh, priority view (default) assignments were not copied over to its sandbox orgs
-
Distribution Details Report [PULS-6349]: Following displayed when Sales Managers attempted to view call history reports of N/A or Deleted Lead IDs
Error
HTTP Request failed (400).
-
Admin Permission Set [PULS-6400]: The following error displayed in Pulse instances where the primary admin was connected to a non-System Administrator account, and partially impacted Inbound Hunt Group Distribution functionality:
You do not have access to the Apex class named: VelocifyRecordInfoRest.
-
To fix the issue, a missing Apex class named VelocifyRecordInfoRest was added to the Velocify Admin profile.
-
-
5000+ VRHI on a Single VRH [PULS-6658] : Errors displayed on the Dialer HUD or timeline could not be accessed for 5000+ VRHI on a single VRH. To fix the issue, the following have been implemented:
-
Loading VRHI with CallIds limited to 5000 items. If there are more than 5000 items, a warning will be displayed but the timeline history will be displayed
-
For record with excessive Timeline history, we will limit the number of Call Type activities that display in the timeline
-
Next Section: Known Issues | ||
Previous Section: Feature Enhancements |