Velocify Pulse 22.1 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:
-
Configuration Management: After importing new Priority Rules some existing Priority Rules would become disabled. This has been fixed.
-
Priority View Workflow: An error was shown on the Priority View when the Matches operator was utilized for any Priority Rule filter. This has been fixed. For reference: The Matches operator behaves exactly the same as the equal to operator except that it does not check for blank field values. This results in more efficient rules processing.
Equal To will continue to operate like earlier versions.
-
Workflow: Fixed an issue where successful text messages were not consistently logging the "Send Text" action on the record automatically. Like any action, the Send Text action can be used as part of a workflow to trigger status changes if desired.
-
Salesforce Shield: Removed test code that prevent Velocify Pulse install if Encryption was set on Contact and Account Name.
-
Matches Operator: Priority view fails to load if the Matches operator is used. This is resolved.
-
Time Zone Protect (TZP) Validation: For awareness, a real-time check will be added to the State TZP logic before an outbound call is made. This will be available in a future Pulse release
-
Pulse Sandbox Upgrade: A NO TOKEN Found issue occurred when upgrading sandbox environments. This has been fixed.
Next Section: Known Issues | ||
Previous Section: Feature Enhancements |