SERVICE IMPACT
The maintenance is a zero downtime maintenance; Some users may be logged out, but those users will be able to log back in immediately.
Do not execute bulk data upload during the maintenance. The service disconnection can occur anytime after the maintenance start is announced via the status site.
5.1 RELEASE CONTENT
COMMON/API/DATA SETS NEW FEATURES/IMPROVEMENTS
- The Intapp application fonts have been updated to accommodate different browser types for better user experience.
- Periods and hyphens are now treated as separators when searching throughout various lookups in the application.
- Schema definitions for virtual tables can be retrieved from the sandbox via the API and used in production.
- The API has been enhanced to support Terms document upload for any type of group.
- REST APIs have been improved to retrieve system IDs to default addresses on lookups and drop-down lists.
- POST and GET APIs have been improved for the Party Lookup type question.
- Business acceptance implementers can store date, time, and date/time type attributes in virtual tables to support date type custom data.
- Functionality has been improved for retrieving related parties of clients and matters using multiple data sources.
- Functionality has been improved for retrieving addresses of clients, matters, and parties using multiple data sources.
- Request data source is now added to datasets so that implementers can present requests meeting certain criteria to users on a request form. It allows filtering on clients, matters, parties, and other fields to quickly retrieve requests.
- Business acceptance implementers can select fields to retrieve, sort, or filter using smart lookup to minimize the need to scroll through search results.
- Data sets have been improved to retrieve remote IDs to easily match addresses with external systems.
CONFLICTS NEW FEATURES/IMPROVEMENTS
- A new configuration called "Enable User Types for Conflicts Report Recipients" has been added to the Administration -> Settings -> Conflicts UI. This configuration allows firms to disable or enable user types for Conflicts Report recipients.
- Corporate trees can be sorted in alphabetical order throughout the application permitting Conflicts Analyst faster location of search names and easier review of search results.
- Conflicts Analysts are able to view the matter count for clients that appear in a corporate tree. All matters or only active/inactive matters can also be displayed for clients in a corporate tree for improved analysis.
- Firms can convert a conflicts search to a request and retain all attributes of the completed conflicts search (e.g. search results, resolutions, etc.).
- A new configuration called ‘Show time in user’s timezone’ is available for capturing the datetime of custom fields on searches and reports and presenting datetime in the user’s timezone. This allows users to more readily identify tasks and due dates in the user’s time zone.
- Updated the BvD integration to use the newest version of the Orbis API, and added the ability to leverage the corporate group definition for the corporate tree.
INTAKE NEW FEATURES/IMPROVEMENTS
- The party lookup type question can be added as a sub-question in a custom grid. It allows for selecting an existing party in the system or entering a new one. The configuration also permits matching the party against an external provider and can be passed to Conflicts as a confirmed party to expedite the conflicts search process.
- The company details (e.g. address, country, etc.) for parties matched against an external provider are visible in the grid question and can be passed to Conflicts as a confirmed party.
- Various question types (e.g. drop-down lists, smart lookup, or word/phrase) can be used in a grid to capture party, affiliation, relationship, etc and the data captured is passed to Conflicts to expedite the conflicts search process.
- A new configuration called 'Show time in user's timezone' is available for capturing the datetime on form questions and presenting datetime in the user's timezone. Also supported are the DateTime custom fields allowing users to more readily identify tasks and due dates in the user's time zone.
- Users are able to show or hide questions groups from the printed version of a form.
- Firms can convert a conflicts search to a request and retain all attributes of the completed conflicts search (e.g. search results, resolutions, etc.).
- An indicator for new or updated parties in a custom grid that are passed to Conflicts is visible to conflicts team members permitting quick identification of the parties that require a new search.
- For requests that have been converted the Activity log has been expanded to include more descriptive details such as the request ID numbers, activity type, and user comments.
- The required indicator for form questions is visible when printing a form.
- 'Assigned by User' placeholder has been added to the assign, share, and delegate notifications permitting the recipient to easily follow up with questions as needed.
- In the form designer, you are able to show or hide grid columns. A configuration called 'Display in notification' allows administrators to determine if grid columns will be displayed in the notifications.
- Party details matched in a party lookup question (e.g. party name, company name, address, country, external identifier) can be included in notifications.
TERMS NEW FEATURES/IMPROVEMENTS
- Document type can be selected when uploading a document and assigning to a Placeholder.
- A word or phrase search can be completed across all documents uploaded to the Terms application rather than searching each document. A new menu option under Terms called Document Search allows a user to initiate a search across the Terms application.
- On the Document Search page users can filter and sort documents by type, status, or linked entity in order to simultaneously work on several documents of the same type.
- Users can view all results, open, and categorize documents returned upon completion of word or phase search in the Terms application. When opening the document the user is taken directly to the section of text found in the search so that s/he can complete categorization without scrolling through the document.
- The results of the search can be sorted by Relevance, Upload Date (oldest first or newest first), and Number of matches in ascending or descending order.
- Operators are supported in Terms ensuring search syntax such as AND, NOT, OR, and exact match (double quotes) can be used when searching documents. Note: Technical Requirements Change: The Intapp Search Service is now a required component of Intapp Terms. The Search Service, which is already a required component for Intapp Conflicts, needs to be installed to support the new Intapp Terms Document Search feature introduced in version 5.1. Please refer to the Intapp Terms - Technical Requirements and Intapp Terms - Installation documentation for further details.
- A confirmation warning message displays when a user selects the 'Accept all' action in Terms.
- A Responsible Lawyer property has been added to the documents permitting partners and other reviewers to identify the lawyer responsible for the terms defined in the documents.
- Terms users can identify matters that will be excluded from inheriting client terms when attaching documents to the client profile.
- All 'find in' field drop-down lists are now alpha sorted.
- Terms users can export Terms from the specific entity profile.
- Terms administrators can search through Terms Templates and Categories without expanding each category.
COMMON/API/DATA SETS DEFECT FIXES
- User names were incorrectly treated as case sensitive when adding users to groups via API.
- Users deactivated via the API were not removed from all groups.
- Removing the primary address type via the api/common/v1/addresstype API method failed to display an error message.
- EscapedCharacters and DisableAdditionalSynonymsAnalyzers were missing from both the POST and Get APIs and could not be updated.
- The clearance summary was missing from Create and Update API methods.
- System integrations saved in the cloud threw an exception error message.
- Deleted parties could be retrieved using the GetParties API.
- The Get Request API threw an error message if a request included a financial ratings question.
- The POST/api/intake/v1/requests/{requestId}/_approve in Swagger did not behave normally and requests submitted to an ad hoc state in the workflow stalled and did not move.
- The data source fields were misaligned when the data source fields swapped places.
- A validation error displayed after creating a data set and adding '0' to the external parameter name field.
- When a data set was created using the User datasource, the data set did not recognize the User object type and resulted in an empty value the form question.
- The removal of a data source from a created data set resulted in an error.
- The GetQueryIntegrationAction validated single form definitions rather than completing a bulk validation.
- Terminology translations were not applied to the answer type when configuring a data set using the 'Get Term Templates' operation.
CONFLICTS DEFECT FIXES
- The conflicts search results count displayed incorrectly when using a Google Chrome browser.
- After certain client and matter user types had been removed, those user type columns were still displayed in the search result grid.
- Party creation and modification threw an exception error.
- For parties passed to Conflicts from a request party lookup question, the search term would only display in the Party Search Profile lightbox after clicking on an empty space.
- Users were unable to filter and sort searches based on the duration of the search.
- Attachments to a Conflicts Search were only rendered for the search creator.
- When filters were applied or updated, the Conflicts Search List, Conflicts Report List, and Quick Search pages scrolled to the top of the screen rather than remaining in position.
- Errors occurred during reindexing if synonyms contained separated special symbols.
- Line break tags were inserted incorrectly in the Compose mail lightbox when a user clicked the 'create report' action.
- For a request with a Related Parties question, the Create Conflicts Search workflow state failed if a referenced relationship type was renamed.
- An expression invalid error displayed when an advanced expression was created for a search term using escaping characters such as "/".
INTAKE DEFECT FIXES
- Elements of a read-only party lookup question could be edited.
- Form questions included in the overview section on sub-requests displayed empty values.
- An error message displayed when a user saved a form that included a score profile and more than 400 questions.
- The lookup party link was not visible after typing in the party name on the request form.
- Required fields in a grid type question were not respected and the form could be submitted with empty values.
- Users with view only permissions were able to claim and edit requests.
- A user's assigned assistant was not transferred along with the user when a request was converted.
- Duplicate search terms were created when requests were converted.
- If parallel states followed a decision in a workflow design, the user was taken from the decision to an incorrect transition.
- A row added to a grid question resulted in the question detail being hidden.
- Form questions with dependencies could be deleted and a warning message failed to display.
- When using the Internet Explorer browser for Intapp Intake, the page scrolled to the top of the screen rather than remaining in position after answer types loaded and were selected for a smart lookup question.
- The relationship field label was misaligned when the Edge browser was used.
- When filters were applied or updated, the Requests page scrolled to the top of the screen rather than remaining in position.
- Attachments from requests were not included in test notifications.
- Modifications made to fields in Data Management caused a warning banner to display on the profile page.
TERMS DEFECT FIXES
- The 'add files' hyperlink did not work on the document upload screen.
- When the browser window resized, the column selector would open and then immediately close.
- The user was not redirected to the login page when the Terms session timed out and the back button was selected.
- Changes made to documents such as Standard Terms Exception were not displayed in the Activities tab.
- A validation error was thrown if a user's timezone is set to UTC-smth (ex. UTC-4) and the review report due date is set to "Now".
Posted Sep 27, 2019 - 13:33 PDT