Bugfixes:
When using the 'replace' option in the contract Overview tab to upload a new version of the contract document and then using the file selector to upload it from the list of documents in the Knowledge Base, the document list was empty.
An LSP user was unable to change the state of a matter to 'complete.'
The matter name and ID number didn't appear in the modal when the state of a matter was changed.
When contract extraction was disabled, the contract types previously enabled for extraction still appeared as 'enabled' in the Contract AI Data Extraction in Contract Management.
JSON files appeared in search results.
A newly uploaded file didn't appear in search results when they were sorted by 'most recent.'
When a user viewed their Planner, clicked on a due date, opened a matter, and clicked the 'back' arrow, the Planner was blank.
'Member assignment' notifications weren't generated when users were added as members to contracts.
A user who tried to delegate a disabled user's contracts received an 'internal error' message when they should have seen a message in the user's profile telling them that delegation can only be done from active user accounts.
When a matter was created with files attached, and an LSP user searched for the files, no results appeared in the 'Matter Files' area of their search results.
During internal testing, the Matter Manager assignment was recorded to the wrong user in a user's activity log.
When an invoice was marked as 'paid' and then marked as 'unpaid' in the Invoices area of the Engage module, the user received a 'the requested action is not authorised under system policy' error message.
When the Outlook Add-In was used to create a matter, a red line still appeared when a required multi-lookup was properly filled in, and users could proceed with the creation of matter.
Users in an org received a 'This add-in could not be started' message when using the Outlook add-in
When logged in as an LSP, a user could see the option to send a file from the 'Files' tab to Dropbox sign, but when they selected that option, they saw a 'file not found' error message in LawVu and an 'Unexpected error has occurred. Please try again later.' on the webpage.
During matter creation via the public API, when multi-lookup field values were incorrect, the error message the user received didn't explain what needed to be fixed.