Risk/Flow Release 2021.3 – US/CAN/EU
Scheduled for Aug 7, 08:00 - 12:00 PDT
- Customer action required: Please communicate to your users that some or all users will be unable to use the service for up to 60 minutes. Do not execute bulk data upload during the maintenance. We encourage you to review the following new features and defect fixes.
- Usage impact: The release will incur downtime. Some or all users will be unable to use the service for up to 60 minutes. The service unavailability can occur anytime after the maintenance start is announced via the status site.

- A new Corporate Tree page with enhanced usability is now used to view and edit corporate tree in Data Management.
- A warning message will be displayed if a company name entered in the Company Lookup lightbox is longer than 60 characters and the external provider is D&B Direct+.
- The S&P corporate tree integration has been enhanced to include additional relationships (e.g. Current Investment Arm, Merged Entity, Current Majority Investments, etc.) and shareholders (e.g. Majority, Minority, Unknown, etc.).

- When configured, corporate trees can be retrieved on the Request form via the Party Lookup question type. Users can review the corporate tree and further edit if they have the Edit Corporate Tree capability, and once their review is completed, the user is redirected to the Request so s/he can continue with their work.

- Request forms that include dependent question answers may take time to update, and if a user continues to complete the form before the dependent question answer loads the new data, the updated question answer may improperly reset. To avoid this behavior a spinner icon will display to indicate the form is updating to alert the user to allow the spinner to disappear before moving on to other questions.
- The UI warning message is now in alignment with number of rows to be deleted from a grid question.
- Performance improvements have been made to Request actions in the UI and API.
- Users setting up Out-of-Office delegation on another user's behalf can select themselves in the 'Delegate To' field of the 'Your Preferences' lightbox.
- The 'Create Documents in Terms' workflow state has been improved by becoming an approval state. The state includes the Approved/Declined transitions in addition to an auto-transition.
- The 'Create Documents in Terms' workflow state property mapping includes Responsible Lawyer and Standard Terms Exception in addition to the standard document properties such as Client, Matter, Expiration and Effective Dates.
- Reminder notifications can now be sent to pending approvers only, instead of all approvers to avoid spamming approvers who have already taken action on requests.
- Data sets can now select the user who overrides an approval rule.
- The fields for the Lookup type datasource have been added to the Sort By function in Data Sets.

- To streamline and expedite the upload of documents as part of the integration with Intake, the Request forms have been enhanced to allow users to define the entity the term document will be uploaded to, inheritance for the document, Suggest Terms, and if the document will replace an existing document. If the Request workflow includes the 'Create Documents in Terms' workflow state, a link called 'view Term document properties' is displayed and visible to users with the Edit and Categorize capabilities.
- The Conflicts specific term templates have been improved to allow the creation of client related parties for entities identified in documents such as Outside Counsel Guidelines. Custom templates (ex. Affiliates or Subsidiaries) with the answer type 'Parties' will have an integration with Conflicts to enable Blackbook entity integration and Create adverse client party relationships.
- A new page called Terms Documents has been added so users can view all documents uploaded to Terms and review the document properties. The same filter options and grid columns available in the entity profile, Terms Document tab are available on the new Terms Documents page.
- Users assigned the 'Create Request' capability can initiate a Terms Review and Approval request from the document gear menu for existing documents without having to initiate a request from Intake.
- Users responsible for categorizing terms documents can now add comments within the categorization lightbox. A tab for comments has been added, a maximum of 100 comments up to 500 characters can be added, and rich text formatting is supported. Users can also edit or remove their comments, and Admin users can remove or edit any comment.
- Users are able to search for information on the Terms Data page by filtering for the Term Effective Date or Term Expiration Date.
- Filtering options on the Terms Data page have been enhanced by adding Effective Date, Expiration Date, Created On and Finalized On dates. Users can search for documents using specific dates or by entering a date range (i.e. within the last week, month, year, etc.) to narrow the results.
- Filtering options on the Terms Data page have been enhanced by adding Term Status so that users can view documents based on Pending, In Effect, or Expired statuses, in addition to None or All.
- Users will receive an auto-categorization complete notification for the offline process of auto-categorizing multiple documents with new templates for existing documents at one time. When the auto-categorization process begins the exit overlay prompts the user to select a link to enter their email address to be notified when the process has been completed.
- When the document search results are exported to an Excel file, the search phrase will be included to give users insight into why the search results were returned.
- The Terms Document properties (i.e. Effective Date, Document Status, Issued By, etc.) can be added as placeholders in the notification templates.
- Client/Matter security is respected for Terms Inheritance and has been added to the Open Elasticube.

- The Data Sets UI has been enhanced to allow implementers to join standard entities with Virtual Table columns. An '+ add' button is displayed under the Objects label and when selected a list of datasources is displayed, which contain tables from multiple datasources, lookup datasource operations, and virtual tables. Implementers can then define the table to join to the standard entity by clicking the '+ join' button.
- To improve the join function in Virtual Tables, double quotes are no longer required for Primary Key values.
- The Get function in Data Sets have been enhanced to retrieve request, searches, and/or entity URLs to allow users to access the entity for further review.
- The Terms Multisource Data Set now returns the Parties, Users, and Matters answer types.

- Notifications that had a total message size exceeding 10MB were not previously delivered due to their size. Now messages exceeding 10MB in size will drop the files that caused the size breach and display file name(s) noting that the file(s) was too large to include.
- Implementers can export/import system configuration settings between environments. Action buttons are available on the system configuration page under Administration.
- The Terms API has been enhanced to allow filtering by term templates.
- Implementers can define Party Type (i.e. Company, Person, Cartel, etc.) via the CDS APIs.

- Confidential searches linked to a Request resulted in an exception error when a user without permission to the confidential search accessed the Interactive Conflict Report.
- In some cases duplicates were displayed in the Search Group Profile after search parties were added.
- Edits applied to a saved search term resulted in a new search term being created in addition to updates to the original term being saved.
- Confidential search hits included on a report and shared with a restricted user more than once were visible on the PDF report.
- Edited corporate tree search terms were not searched when Conflicts was upgraded to the latest version.
- In some cases Conflict Rules were created with invalid condition operators.
- Individual names were duplicated in the Management section of corporate trees from the BvD provider when the Corporate Group Definition configuration was enabled.

- Completed requests were marked as deleted after the completion of a Cloud migration.
- Performance issues occurred when users selected unassigned requests.
- When a request was converted using the 'Convert Request - Created By User' setting via the API, the Created By User name was not displayed.
- Requests were corrupted if a user deleted a question answer in a Repeatable Question Group or when the RQG was cloned.
- An error message was thrown and users were unable to select a name from the Share Request Lightbox if the request included several hundred reviewers.
- Requests that included a table question with a 'This question is always hidden' display condition, and where 'Memorialize question answers upon request completion' configuration was selected, resulted in an error when submitted to the final state.
- Requests that included a custom field updated via the API did not transition to the next state after the request was approved.
- Requests did not move to the end state when declined within a parallel state.
- Request workflows that had two Create Documents in Terms states, incorrectly indicated the Term document name from the first workflow state in the Activities tab as part of the second workflow state.
- A unique key constraint error message was thrown when a Request was transitioned to the next workflow state and the transition table locked.
- The file attachment checkboxes in the 'Attach a file to this Request' lightbox displayed inconsistently.
- The display conditions for grid form questions were not respected and displayed a column with hidden values.
- After a user clicked the 'generate document' on a request form, a new browser window for Contract Express opened but did not close when the user logged in.
- Columns, when sorted by Status or Approver, did not sort correctly on the Approval Rules tab.
- The ApprovalRuleApproverEmail notification placeholder was duplicated within the To/CC/BCC drop down menus.
- Customers on the new workflow engine observed that reminder notifications were sent after a request was converted to a new request type.
- Workflows that included the GAL and RBA approval states did not respect the required conditions for added ad-hoc rules.
- An exception error occurred when a lookup question was updated via the API.
- Comments added as part of an approval override displayed the wrong user name in the activities tab.
- Exported workflows that included sub-requests failed when imported into a new environment.
- IB integrations were not displayed in the score profile integration drop-down when query integrations were disabled.

- Users were unable to view the entity link in the Corporate Tree Lightbox when viewed from the Client or Matter profile in Terms.
- Users were unable to update a linked document status from the Document Relationship dialog box gear menu, as the Confirmation lightbox was hidden.
- Display settings applied to the term template were ignored after the template was updated and searched.
- The Document Search page displayed incorrect pagination if more than 50 results were returned.
An incorrect error message was logged if a user sent a Terms Summary Notification to an inactive user.
- When a user ran a search from the Terms administration page, accepted the results and moved to the next step, the suggested terms were not displayed.
- Users searching a documents content were unable to view the search result after the document type was changed to an unrestricted type.
- An error message is thrown and the inheritance summary cannot be calculated if restricted entities were included in the list of inheritors.

- Virtual tables updated using an ID as the reference key threw a validation error when customers upgraded to the latest version of OnePlace for Risk.
- Data sets that included boolean custom fields failed to sort in the correct order.
- Data Set substring functions would not accept computed expressions for parameters.
- Changes to custom character limits on custom fields for the Intapp Reporting Service made via the API were not saved.
- The Client sync failed if duplicated client users exist in CDS.

- If you have any question, please contact Support@intapp.com.
Posted Jul 07, 2021 - 14:11 PDT
This scheduled maintenance affects: CA (CA Risk/Flow), EU (EU Risk/Flow), and US (US Risk/Flow).