Bugfixes:
While performing functional testing of the yet-to-be-released contract syncing feature:
We noted that the sync's "paused" status was not visually indicated when a contract was in draft status, even though the sync was paused in the backend. This led to updates not being uploaded to LawVu.
When contract document synchronization was paused due to approval workflows or edits, activity logs didn't record this.
Notifications weren't created for sync 'paused' events.
We noticed that some buttons used throughout LawVu needed to be updated to the newest style.
The text underneath the 'stage' button for contracts and the Client's name when logged in as an LSP user were underlined, and the text on the 'Article tags' tile in the Knowledge Management settings needed to be corrected.
During testing of contract approval routing:
A conditional workflow incorrectly treated special fields as absent even when they were present in the contract creation form. This caused it to follow the "condition not found" path instead of triggering the expected workflow actions.
When the user clicked into a column to filter the workflow, some options in the dropdown box were cut off.
When a user viewed the list of contract types on the 'Contract Types' tab after navigating to Approval workflows > Contract approvals, some of them didn't appear unless they zoomed out on the page.
A user performing regression testing couldn't assign an invoice workflow to a matter type, because the assignment modal was stuck in the loading process.
When the name of a team was changed, the 'work assignment' button was toggled off, so users couldn't see the teams to add them to contracts or matters.
Users were unable to save 'To Do' items.
When a user with a legal service provider tried uploading invoices, none of the data could be extracted.
A user performing regression testing of fields saw an 'error creating field' message, even though the field had been created, and then saw an incorrect error message when trying to create a field with the same name.
466.1
An approved invoice forwarding process initially experienced a query timeout issue, which was resolved in a previous fix. However, a second query within the same process started timing out and causing failures, affecting a specific US organization.