MAINTENANCE FOR INTAKE-CONFLICTS-TERMS-FLOW 2020.1 US/EU
Scheduled Maintenance Report for Intapp, Inc.
Completed
The scheduled maintenance has been completed.
Posted Feb 01, 2020 - 11:59 PST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Feb 01, 2020 - 09:18 PST
Scheduled
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.

2020.1 VERSION CONTENT

COMMON/API/DATA SETS ENHANCEMENTS:
- As the Microsoft Workflow Engine has reached end of support, all customers will use the new Intapp designed Workflow Engine. The new workflow engine created and supported by Intapp improves system stability and provides better logging and monitoring capabilities. This was released for all new customers in August 2019 and all existing customers will transition to the new workflow system in the next few months.

- Query integrations and data set parameters have been expanded for the party lookup form question.

- The data sets have been enhanced to retrieve the party and client alias names.

- Request attachments can be updated and deleted via the API to accommodate new or updated documents.

- Performance improvements have been made to custom fields.


CONFLICTS ENCHANCEMENTS:
- Synonym modifications made via the UI are applied to the search engine analyzer asynchronously.

- The aliases of component group members are displayed in the search results.

- Conflict analysts can select the corporate tree for search parties matched in the external provider during the intake process. A link appears next to the search party name for quick lookup.

- The corporate tree lookup in the party search profile has been enhanced to allow users to type in the search party, select the external provider and country, and select from a list of the top results.

- Performance optimizations have been made for loading the summary of sub-searches on a parent search.

- Performance optimizations have been made to better support archiving of large conflicts searches.

INTAKE ENCHANCEMENTS:
- Condition controls for party lookup form questions are supported to leverage party attributes - including content from external providers such as D&B or BvD - to be used in other form questions and to derive form behavior for kicking off the correct business processes.

- To accommodate an easy upload and organization of documents, attachments can be uploaded at a question level.

- Implementers can enable view permissions to specific users or groups per request type, so that users are able to view details of a request during the workflow process.

- When creating or editing a notification template in the notification designer the user will stay on the same page after saving the changes.

- The approval buttons in the notifications have been enhanced to mirror the approval buttons in the UI.

TERMS ENCHANCEMENTS:
- Performance improvements have been made to document processing for a faster and more consistent upload experience.

- The new Terms Portal permits users with Manage Terms Configuration capabilities to customize the Entity Profiles Overview section for clients, matters, and groups. User can add to or delete default fields and widgets and sort the information according to customer preferences.

- Implementers can specify exceptions such as excluding a group of matters from inheriting client terms when uploading documents via the API.

COMMON/API/DATA SETS FIXES:
- The Data Management page opening was slow for both Administrators and Non-Admin users.

- The position of the action buttons were misaligned when monitoring rules were tested.

- An error message displayed for tenants that did not have CDS (common data store) integration.

- An error message displayed when a company name was updated for the party lookup question via POST/api/intake/v1/requests/requestId/answers.

- Shared conflicts search reports included all results in the notification instead of those selected to be shared.

- Pages with long query strings in the URL could not be opened.

- The create party API threw an exception error when the unique constraint was not respected.

- The create party API threw an exception error when the unique constraint was not respected.

- Searches added via POST/api/conflicts/v1/searches were removed from the index while a full re-index was performed.

- The "api/common/v1/users{userID}/password" call in Swagger failed if a password field contained any special characters.

- An error message lacking clarity displayed when a search was created with a long name via POST/api/conflicts/v1/searches/_bulk API method.

- The activities tab did not display the search created activity when searches were added via POST/api/conflicts/v1/searches/_bulk.

- The Get Clients REST API filter failed to return results for custom fields in Data Management.

- Searches updated via the API did not update the Search Owner field.

- Created request parties were not deleted from the RequestParties table after the grid question was reset via the API.

- Pages with long query strings in the URL could not be opened.

- Non-permitted symbols (e.g. "=") and permitted characters (e.g. a period ".") that were added to data sets with external parameters did not specify the permitted character in the validation error message.

- There was no indication that a data set was used to create a scoring profile.

CONFLICTS DEFECT FIXES
- Text in the search results did not wrap and format properly when either a PDF or interactive conflict report was generated.

- An exception error was thrown when the search page was opened after a custom field and its related party/external source/component group type were removed from the database.

- Exact match was incorrectly applied when users created search terms using proximity searching.

- An exception error was thrown after an attempt to add a date filter for conflicts search results after removing party/external source/component group type with an existing custom field.

- An error was returned after an attempt to perform a search of the corporate tree for a term using a single configured provider after the user opened the party search profile for a resolved term with a custom tree.

- When minimum share criteria were set for company searches in BvD incorrect results were returned for shareholders.

- When companies were searched in BvD the owned subsidiaries were not always listed in the returned search results.

- The activities page displayed incorrect datetime for fields with applied timezone conversion (e.g. blackbook expiration date, creation date, etc).

- When filtering by status in Data Management, the status of clients and/or matters with long status names did not display correctly.

- Notifications and Interactive Conflict Reports that included the search results grid placeholder with timezone conversion did not display the correct timezone information.

- After a Quick Search was deleted users were directed away from the Quick Search page to the Conflicts Searches page.

- The return to conflicts search link did not display for users with edit rights who were reviewing the conflict report.


INTAKE DEFECT FIXES
- Firms using the Edge browser experienced grid questions not accepting values unless users entered the value more than once.

- Firms using Internet Explorer 11 experienced missing values for sub-questions that had been completed.

- An error message displayed on a printed blank request that included a party lookup grid and was printed after the create conflicts search state.

- Although the client was located and added, when the matter name was added to Create Request Lightbox, a search was conducted on the client instead of the matter.

- The cancel action was not respected after a created request was canceled.

- Requests set to auto-transition from one state to the next failed due to the sub-requests transitions locking.

- When a related party question used more than one data source to add a value, an exception error was thrown.

- Workflows that included automatic transition states, such as run conflicts search, caused the activities list to be out of order on the requests activities tab.

- The warning banner failed to display and requests could be approved or moved to the next workflow state without required questions with checkbox answer types being completed.

- An error message displayed after a user claimed a request, and then shared a request after assigning it to another user.

- Company names added via the party lookup type question in a grid displayed incorrectly after the conflicts search was created.

- The pull down menu under Administration was not listed in alphabetical order.

- Improvements made to push notifications for pending approvals being updated automatically resulted in the desktop application locking.

- Notifications were not sent for out-of-office delegation when the recipient's email was added to a text field on a form that was added to the recipient field for notification templates.

- Attachments were not included in notifications when the attachment question answer was added to the notification template.

- A validation error was thrown when a workflow was imported to the workflow designer.

- An exception error resulted when a workflow that contained a sub-request inside a parallel thread was saved.

- The page redirects to an empty URL after the create state lightbox was canceled in a parallel workflow.

- A validation message did not display when a workflow was saved after conditions were removed from a workflow state.

- Notification templates that were imported to a workflow resulted in an error message being displayed.

- Users were unable to remove conditions added to sub-question in a Grid type question.

- When adding relationship type options to the Create Conflicts state, inactive relationships were shown in the list.

- An error displayed when a grid question was copied from another grid question with conditions, and users were unable to make edits to the copied question.


TERMS DEFECT FIXES
- When a user changed the document status and clicked the escape button the status confirmation lightbox did not close.

- An error message displayed the browser console when navigating to the Terms page.

- Terms documents would not open and an error message displayed if Intapp Terms was installed using the http protocol.

- The 'Key Terms' and 'Atypical Terms' filters were not respected when terms were exported from the Term Data page. The excel file displayed all terms.

- The grid column selection menu displayed incorrectly if users clicked the column selector icon multiple times in the IE or Edge browsers.
Posted Dec 20, 2019 - 07:02 PST
This scheduled maintenance affected: EU (Risk/Flow EU) and US (Risk/Flow US).