Bugfixes:
During internal testing, when a client sent a request to an LSP to add a new user and the request was pending, they couldn't send another request.
When performing internal testing of the conditional invoice approval feature:
The software displayed a generic "Request not valid" error message when the model state was invalid, failing to provide specific feedback on why the request failed validation.
A workflow's 'No' phase was deleted when the phase following it was deleted.
When a P.O. number and a cost centre number were required on an invoice and then populated, the 'approve' button failed to appear.
A user who tried to use the 'Edit with Word Online' feature without a Microsoft 365 business account saw an' internal error' message that didn't explain why the feature wasn't available when using a personal account.
When one LSP user tried to add members to a conversation, they couldn't select an organization or add members and saw a "you've been removed from private conversation" message.
During functional testing, the wrong user appeared in an invoice history.
For a user in one organization, the 'approval status' column in Spend>Invoices wasn't filtering properly.
When the execution date for a contract was selected, the date picker field displayed the previous day's date.
Users were prompted to enter the execution date when a contract was sent for signing.
A client at one organization saw a 'profile not found' message when they tried to access an LSP's profile info.
When the 'newmatter' email address was used to create matters, the 'Objectives' field was truncated.
During regression testing, when a document was signed in DocuSign, the signature didn't appear.
During functional testing of the Workspace Intelligence feature:
It didn't accurately retrieve or display contract details, preventing the user from getting correct responses to their queries.
When a contract had no team assigned to it, and the user asked about the team assigned to it, WI responded with a hallucinated team name. It did the same when asked about the contract's owner and provided the contract group when asked about the contract type.
Conversation ID numbers appeared in response messages.
There was no response when the user opened a contract and asked, "Are there any related items?" in their prompt.
During functional testing of the email grid view, moving email threads between folders did not function correctly due to a discrepancy between file IDs. This caused the move operation to fail silently, without any error message or conflict resolution prompt. As a temporary workaround, the ability to move emails from the Email view was disabled until a permanent fix could be implemented.
The conditional logic applied to the "Matter due date" date picker field in LawVu's Outlook V3 add-in was not functioning as intended.
438.1
Core pipeline failure prevented deployment of WI search alerts.