Bugfixes:
In Outlook, users could not re-save an email thread to a matter using the Outlook add-in if the corresponding email file had been previously deleted in LawVu.
The invoice modal incorrectly calculated budget excess for invoices with foreign currencies. When an LSP user uploaded an invoice with a fee in an international currency against a fixed fee budget with currency conversions set up, the system initially failed to recognize that the converted fee value exceeded the budget. Despite this, a tooltip warning about budget exceeding appeared, preventing the batch from being posted, indicating a discrepancy in how the modal handled currency conversions for budget calculations.
A user trying to create a contract saw an 'internal error' message because of an error in the contract template.
The Matter export summary page displayed dates in the dd/mm/yyyy format, which did not align with the US users' preferred mm/dd/yyyy format.
The email notification sent when an LSP submitted an invoice incorrectly displayed the client organization's name in the "Added By" field instead of the LSP's.
When a user synced their LawVu Planner with their Google calendar, the task was removed because of an error in the endpoint window for the due date.
The Slack add-in's token management mishandled refresh token failures. When a refresh token exchange failed, the system did not clear the invalid token from storage. Consequently, requests made before manual signout repeatedly failed due to unsuccessful refresh attempts. Instead of the expected behavior of automatically logging the user out and forcing a re-login, the system silently failed, leading to issues like an empty matter type list for the user.
When creating a new contract via the Outlook add-in, if the "contract owner" field was present in the creation form, the owner's name appeared twice.
When creating a matter or contract, a value in the LawVu default "Priority" field, specifically "non-urgent," was displayed incorrectly as "non-urgent (ASAP)" within the Outlook add-in.