Skip to main content
All CollectionsDecember 2023
Release notes for 27 December, 2023

Release notes for 27 December, 2023

A list of all new content added to LawVu in release 369

Christy Cortez avatar
Written by Christy Cortez
Updated over a year ago

Bugfixes:

  • When a matter viewed in 'preview' mode had an extremely long name, the breadcrumb label was too long and spilled into other content in the preview window.

  • During functional testing, when a user extracted data from a contract and the suggestion for a field didn't match, the 'AI Suggestions' button appeared and was blank when it shouldn't have appeared.

  • When a user performed functional testing and tried to extract data for two fields labeled 'other party' in their contract, the information for one of the fields appeared twice when they clicked the 'AI Suggestions' button.

  • During internal testing, when a user tried to change the access level for an LSP from "No Access" to "Billing Only," they couldn't without enabling a feature flag.

  • During internal testing, a user saw an "internal error" message when accessing the Directory. When a user had the "status update" column in their contract grid view, the 'request update' button appeared even though users can't currently request updates on contracts, only add them.

  • The Business/Standard users in one organization were not able to see messages in general conversation until they were @mentioned or added as members.

  • During regression testing, when a user tried to replace a contract β†’ selected the option to upload a new version β†’ then chose an existing contract file from "recent" contracts β†’ the previous version was uploaded and the file version remained the same.

  • When a regression testing user uploaded a file that existed within a matter or contract and then clicked the "skip" button, the "retry" button wasn't centered properly.

  • During regression testing, when a user tried to update the status of a matter via "UpdateMatter Fields' in Power Automate, the request failed because the Rest Sharp tool that PA uses lost track of words and codes, so the request ended up "invalid."

369.3

  • A user at one org was removed from 2 restricted contracts.

Did this answer your question?