Release notes for 14 April, 2022

A list of all the new content added to LawVu in release 201

Ben Kidd avatar
Written by Ben Kidd
Updated over a week ago

Product Items:

  • We released the ability to change the contract type after contract creation. Sometimes after the creation of a contract, it became apparent that the contract should be categorized differently using fields available in another contract type. Users expected to be able to change the contract type, the same way they could with matters. Oh, how they laughed when they realized they couldn't. Hilarity ensued as the contracts had to be deleted and recreated from scratch under the correct type. Being the complete buzz-kills that we are, we have knocked this fun on the head. Now you can easily change the contract type, even after creation.

  • We introduced a recent items dropdown menu in the Global search. For those of us who use the Search function as a navigation tool to quickly access our recent work, life just got even easier.

  • We improved the global search for matters by LawVu ID. The Merriam-Webster dictionary defines a stickler as "One who insists on exactness or completeness in the observance of something.' In this respect, the LawVu search was the quintessential stickler, demanding the full LawVu matter or contract ID before it would return any results. Our engineering team has encouraged the search to take some deep breaths and relax a little. It will now happily return results for the last few digits of an ID.


  • Adjustments made to fees didn't update the tax values in the grid view. Who hates paying taxes? Hopefully not you, as any increase in fees will now also produce an increase in tax values.

  • The Department field was no longer editable from the grid view. Even the closest relationships can suffer a falling out sometimes. This was a case where the backend stopped speaking to the frontend. Thankfully, reconciliation has been achieved, and changes to the department field will now be reflected in the grid view.

  • Corrected issue with alignment in the Knowledge base and home articles. In the Knowledge base, for organizations that have Restrict access enabled, the people icon was overwriting the text. This made for some interesting hieroglyphics but was almost useless for those of us that read English.

Did this answer your question?