What’s New?
We’ve improved Quick Dispatch by making it where you set your budgeted hours per line item instead of as a whole on the visit. This allows for budgeted hours to be accurately shown on line items when the visit is created.
How It Works:
Issue: When receiving notifications for different actions in the software, the timestamps were not displaying in the correct timezone.
Resolution: Switched the notification timestamp conversion from to UTC to user timezone instead of CDT to user timezone.
Issue: The "Use Property Location for Tax Rate" setting was not populating correct tax rates in certain circumstances.
Resolution: Included the city name in the lookup call to create a more precise tax rate lookup.
Issue: The merge tag "Use Property Location for Tax Rate" did not pull the correct text when a visit is skipped.
Resolution: Pointed the correct database values to the merge tag to display the skip reason.
Issue: Opening the notification page did not default to showing todays date which forces the user to need to update the filter in order to see the most recent notifications.
Resolution: Updated the default view to show messages from the last 7 days, and enhanced the sorting order to show newest notifications at the top.
Issue: Sometimes visit schedules are not following the recurring dates given.
Resolution: Updated the time zone conversion on the back end to ensure visits are created on the correct time zone of the user.
Issue: Sometimes the Sequence Automation stop trigger would re-trigger the automation.
Resolution: Refactored our stop trigger handling to ensure that any associated jobs are removed from the automation queue immediately, and won't retrigger the automation.