MAINTENANCE FOR INTAKE-CONFLICTS-TERMS-FLOW 5.0.110 US/EU
Scheduled Maintenance Report for Intapp, Inc.
Completed
The scheduled maintenance has been completed.
Posted Sep 07, 2019 - 11:34 PDT
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Sep 07, 2019 - 08:09 PDT
Scheduled
SERVICE IMPACT
This release is a zero downtime release; some users may be logged out, but those users will be able to log back in immediately.

5.0.110 VERSION CONTENT

DATA SET IMPROVEMENTS
- Business acceptance implementers can store date, time, and date/time type attributes in virtual tables to support date type custom data.
- Implementors or form designers are able to display all answer types or a combination of types as a result of the Get Terms Templates dataset operation.
- Operation filters can be set to display only those answers that correspond to the selected data set; for example the Get Term Value Matter Details operation will return only Matter type answers, or the Get Term Value Party Details operation will return only Party type answers.

UX IMPROVEMENTS
- Periods and hyphens are now treated as separators when searching throughout the application.

INTAKE/FLOW IMPROVEMENTS
- The required indicator for form questions are visible when printing a form.

TERMS IMPROVEMENTS
- No updates to Terms functionality.


COMMON/API/DATA SETS DEFECT FIXES
- Deleted parties could be retrieved using the GetParties API.
- 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 conflicts clearance summary property was missing from the Create and Update API methods.
- A validation error displayed after creating a data set and adding '0' to the external parameter name field.
- There were inconsistencies between SSRS and Sisense reports, such as total request counts, completion times, term frequency, and term statuses.
- EscapedCharacters and DisableAdditionalSynonymsAnalyzers were missing from both the POST and Get APIs and could not be updated.
- The data source fields were misaligned when the data source fields swapped places.

CONFLICTS DEFECT FIXES
- Users were unable to filter and sort searches based on the duration of the search.
- The conflicts search results count displayed incorrectly when using a Google Chrome browser.
- Line break tags were inserted incorrectly in the Compose mail lightbox when a user clicked the 'create report' action.
- Synonyms with separated special characters threw an error message when the search engine reindexed.
- Attachments included on the Conflicts search page were not visible to users with conflicts capabilities permissions; the attachments were visible to the creator only.
- The conflicts report did not include client/matter fields for search results found via the alias name.

INTAKE/FLOW DEFECT FIXES
- When filters were applied or updated, the Requests page scrolled to the top of the screen rather than remaining in position.
- Required fields in a grid type question were not respected and the form could be submitted with empty values.
- The lookup party link was not visible after typing in the party name on the request form.
- Modifications made to fields in Data Management caused a warning banner to display on the profile page.
- The read-only condition was not respected for form questions, or the hyperlinks and dialogue boxes associated with the form questions.

TERMS DEFECT FIXES
- No updates to Terms functionality.
Posted Aug 26, 2019 - 12:08 PDT
This scheduled maintenance affected: EU (Risk/Flow EU) and US (Risk/Flow US).