Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Dec 15, 2018 - 10:52 PST
Scheduled
Expected downtime: less than 5 minutes Production will be upgraded to 4.5.120 on January 5th, 2019.
Version 4.5.120 includes the following changes:
COMMON: Data Sets * Fields are now alphabetically sorted in data set drop-downs.
Security/ UX * Security updates have been applied application-wide.
INTAKE/FLOW: * Users can now bulk assign requests to themselves from the request list page. * When requests are converted or cloned, the new requests show a link to the originals. * The GetRequests API now supports filtering on environment, rows to get, and rows to skip.
CONFLICTS: No Conflicts-specific enhancements for 4.5.120.
TERMS * During Terms document upload, users can only associate parties to a selected term if the parties have been linked to the matters associated with the client. * Users cannot remove data that is related to a Terms-Conflicts integration using an API. * When the Terms-Conflicts integration is triggered, an error message now displays if any required data is missing.
DEFECT FIXES Common/API * When adding a matter to a group, after a user specified the client, the matter lookup did not apply the added client ID as a filter.
Conflicts * The Conflicts report URL in notification messages was invalid (missing the server name). * External data hits caused errors in standard conflicts reports. * Conflicts users preparing reports for others were able to see secured clients or matters in the report preview. * Certain actions in conflicts search results were not thread safe, resulting in infrequent errors. * An error occurred when sending e-mails with attachments after changing the e-mail recipient.
Intake/Flow * A multi-select smart lookup could not be used as the value source for a data set parameter. * Condition variables were not evaluated correctly by Intapp Document Automation Service. * Mobile: Request Action links in notifications did not lead to the Request Details screen if both Comment Required and Bypass Confirmation were enabled.
Terms * When the Competitors term template was enabled, the UpdateTermsDocumentStatuses job failed.
Posted Dec 04, 2018 - 17:14 PST
This scheduled maintenance affected: AP: Non-Production (Risk/Flow AP - Sandbox), EU: Non-Production (Risk/Flow EU - Sandbox), and US: Non-Production (Risk/Flow US - Sandbox).