New Features:
We brought the well-loved grid editing experience that exists in Matters to Contracts, so our customers can update their contracts directly from the grid. This means no longer having to open a record to update the data.
Product enhancements:
When users click the pencil icon to edit matter and contract grids, a loading symbol appears to let them know the process is underway.
Bugfixes:
When contract grid views with a large number of items were exported during internal testing, the export didn't begin instantly and the view count was incorrect.
The dialogue boxes that allow users to renew an expired contract that had been executed didn't appear when a user tried to edit the 'expiry' date field from the Contracts grid during internal testing.
During internal testing, the "invoice description" field didn't appear when an invoice was opened from the actions grid.
The notification telling an LSP's user their organization had been given 'billing only' access' by the Client, didn't contain that information and only advised they'd been 'invited to LawVu.'
During internal testing, the in-app and email notifications a user received when they were invited to LawVu didn't contain the name of the organization that invited them.
The 'description' column in Account Activity only indicated that billing details were updated instead of providing specific information about the change (e.g., 'all invoices can be approved with edits, etc.')
When a matter was permanently deleted, the in-app RFP-related notifications weren't removed for the Client or the LSP's users during internal testing.
When users in two organizations created matters containing multi-lookup fields, the field information didn't pull through to the associated contract record once it was created.
Users in one org received an "error creating entity" message when they tried to select an option (Add new entity) in the "Other Party" drop-down field.
Files in a synced folder in Sharepoint didn't appear in the LawVu matter when users in one org tried syncing.
The users in one org were logged out of the desktop and web versions of the Outlook Add-In multiple times per day.
Users in one org couldn't create matters using the Outlook Add-In because it failed to load correctly.
When a matter synced to Sharepoint contained a private folder and a file in the root folder, when a file in the root folder was deleted, and the folder was made public, the deleted file was re-synced and appeared in LawVu during internal testing.
When a document was sent out for signing using Dropbox Sign and then signed, three organizations reported that the signing panel in LawVu never updated.