New Features:
Approvers can now decline contract approval:
Approvers can now decline approval requests and add a comment explaining their reasons. This comment is clearly visible to all members.
The same Approver who declined the contract can later approve it once the noted issues have been addressed.
Bugfixes:
Scrolling on matter preview in the soon-to-be-released related records feature resulted in a distorted view.
The "Related As" filter options included the term "none," which could confuse users. The term "none" was changed to "no relationship" to improve clarity.
The "Link Parent or Child" button remained visible and interactable for Intake Managers on matters they weren't members of, even though they lacked the necessary permissions to relate records, ultimately leading to an error message.
The "Link Existing" functionality in the "Amendments" area erroneously included the current contract in search results, leading to a failed attempt to link it to itself.
Adding a parent contract to a contract with an existing SOW category caused the SOW category to incorrectly disappear from the UI, even though the database relationship remained intact.
Slow connections caused the "Related Records" panel to momentarily display the previous item's data instead of the current one, potentially confusing users about which item's related records they were viewing.
During functional testing of the contract decline feature, a delegate could not see the 'change to approve' option after declining a contract.
When a user left a long comment regarding a contract, there was no 'view more' link so that other users could read the entire message. It could only be seen by checking the 'Activity' log.
When a contract was declined, a user could still see the 'action required' text under the names of the other approvers in an approval phase.
The 'send reminders' button remained active when contract approval was declined.
When approval was declined in a phase, and it was set to 'Everyone must approve,' changing it to 'Anyone can approve' completed the phase.
When a user performed functional testing in the Knowledge Base, the read-only version of an article incorrectly displayed the editing toolbar, even though the user should not have had editing ability.
During regression testing of the soon-to-be-released invoice approval workflow feature, the user saw an internal error message when enabled, and the 'Actions' widget disappeared. Internal error messages also occurred during contract creation or while working on a contract record.
A matter displayed too many actions for a single approval phase, even if they were the approver for only one phase.
When the invoice approval feature was turned on for a user performing functional testing, the 'Actions' widget failed to load for an LSP user and the Client's users.
A user who assigned a matter type to an approval workflow saw a message saying it was successful when it had failed.
Users who were approvers on a restricted matter's workflow but not members of the matter itself could still see the restricted matter's name in invoice previews, notifications, and actions.
The LSP invoice preview was incorrectly updated to the new format, even when the feature flag "modernapprovals" was off or the invoice was in draft status.
A user saw messages indicating their updates/assignments were successful when updates to workflow templates were blocked instead of seeing the appropriate error messages.
While performing functional testing of Outlook v. 3, a tester logged in as their Standard/Business user could see that an email had been tracked to a matter they couldn't access.
When a contract name was updated, it wasn't automatically updated in the Planner.
Knowledge Base article tiles truncated long sentences or paragraphs when they were inserted or edited, preventing the full text from being displayed.
Contributor users in one org couldn't see contracts assigned to "All Teams" despite having the necessary visibility permissions.
The "Parent Contract" column in the contract grid failed to display textual information indicating that the parent contract was restricted when a user lacked access. They only saw a lock icon.