All Systems Operational
Admin Portal - US Operational
90 days ago
100.0 % uptime
Today
Admin Portal - EU Operational
Admin Portal - APAC Operational
Risk/Flow - US Operational
Risk/Flow - US - Sandbox Operational
Risk/Flow - EU Operational
Risk/Flow - EU - Sandbox Operational
Risk/Flow - APAC Operational
Risk/Flow - APAC - Sandbox Operational
Experience - US Operational
90 days ago
100.0 % uptime
Today
Experience - EU Operational
90 days ago
100.0 % uptime
Today
Time Cloud - UK Operational
90 days ago
100.0 % uptime
Today
Time Cloud - EU - Sandbox Operational
90 days ago
100.0 % uptime
Today
Rekoop - UK Operational
90 days ago
100.0 % uptime
Today
Rekoop UK - Sandbox Operational
Time Cloud - APAC Operational
90 days ago
100.0 % uptime
Today
Time Cloud - EU Operational
90 days ago
100.0 % uptime
Today
Time Cloud - UK - Sandbox Operational
Pricing - APAC Operational
Pricing - EU Operational
Pricing - US Operational
90 days ago
99.64 % uptime
Today
DealCloud - US Operational
DealCloud - EU Operational
Time - EU Operational
90 days ago
100.0 % uptime
Today
Time - EU - Sandbox Operational
90 days ago
100.0 % uptime
Today
Time - US - Sandbox Operational
90 days ago
100.0 % uptime
Today
Time - US Operational
Intapp OnePlace Operational
Time - CAN - Sandbox Operational
Admin Portal - CAN Operational
Time - APAC - Sandbox Operational
Admin Portal - CAN Operational
Time - CAN Operational
CRM - US Operational
CRM - US - Sandbox Operational
CRM - EU Operational
CRM - EU - Sandbox Operational
CRM - APAC Operational
CRM - APAC - Sandbox Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Scheduled Maintenance
SERVICE IMPACT
This maintenance may incur downtime; 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.
Posted on Mar 30, 17:03 PDT
The DealCloud-EU Infrastructure will undergo a scheduled maintenance on Friday, April 3rd, from 11:00 PM GMT - 1:00 AM GMT.

During this time, there may be some interruptions in connectivity to the DealCloud Platform. We recommend that you do not perform any large data imports or changes until the maintenance window is closed.

For questions, or if you require technical support please contact us at support@dealcloud.com.

Thank you!
The DealCloud Support Team
Posted on Apr 2, 08:41 PDT
The DealCloud-US Infrastructure will undergo a scheduled maintenance on Friday, April 3rd, from 11:00 PM EDT - 2:00 AM EDT (-05:00 UTC).

During this time, there may be some interruptions in connectivity to the DealCloud Platform. We recommend that you do not perform any large data imports or changes until the maintenance window is closed.

For questions, or if you require technical support please contact us at support@dealcloud.com.

Thank you!
The DealCloud Support Team
Posted on Apr 2, 08:36 PDT
The maintenance will incur downtime. Some or all users will be unable to use the service for up to 30 minutes. Downtime can occur anytime after the maintenance start is announced via the status site.
Posted on Mar 30, 00:47 PDT
SERVICE IMPACT
This maintenance may incur downtime; 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.
Posted on Mar 30, 17:00 PDT
SERVICE IMPACT
This release may incur downtime; 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.2 VERSION CONTENT

CONFLICTS ENHANCEMENTS:
- New Assisted Conflicts module that leverages AI for enhanced search results analysis.

INTAKE/FLOW ENHANCEMENTS:
- When users match a client on the request form using BvD content provider, additional content such as the global ultimate parent, stock ticker symbol, legal form (private vs public), is retrieved from BvD and displayed on the request form. This content can be leveraged for auto-populating information on the form, kicking off new approvals, or showing additional questions.
This information gets passed to conflicts, and when a party gets created or updated at the end of the search process, this content is persisted on the profile for future use.
- A new module called "Rules Based Approvals" has been added to this release. For firms with complex approval requirements, the new module allows firms to better manage and standardize the approval process firm-wide, and minimize the number of approval notifications sent by the system. The intuitive interface allows users to define and maintain rules in a central place. These rules can then be triggered at an appropriate point in the request workflow. In addition, the NBI team can manually apply new rules or override existing rules per request basis to account for any exceptions to the process. Overall, the rules based approval functionality allows firms to standardize their approval process, while providing the right level of visibility to the stakeholders involved.
- A user who converts a request will be designated as the request creator, granting all request permissions to the user who completed the conversion.
- To better manage attachment type migration across systems during a form import or export, attachment types are mapped based on names rather than internal identifiers.
- To allow users greater flexibility and control over document generation, the document template name can be defined by form question answer variables which are passed to the Document Assembly Service (DAS). This allows users to quickly search and find the correct template and document, and send the generated document to their DMS system or client without having to rename it.
- Previously when a custom field was deleted, user preferences and profile pages were corrupted if the custom field was displayed on either of those pages. As of this release, when custom fields are deleted, the system removes those fields from the user preferences and data management properties maintaining data integrity. If a custom field is used in form designers, data sets, etc., then users cannot drop it until they remove references to the custom field.
- Performance improvements have been made to optimize request creation.

TERMS ENHANCEMENTS:
- Administrators can configure the overview sections for clients, matters, groups, and placeholders based on specific group preferences via the Administration-Terms-Entity interface.
- Administrators and implementers can customize client, matter, and group fields on the Terms Entity Profile configuration page.
- Firm specific custom fields for clients and matters (i.e. currency, timezone, etc.) can be displayed on the Terms client matter profile page.
- For those users assigned to multiple groups, a precedence order sort feature is available in the Terms Entity Profile interface to determine the configuration to show users.
- The Clients and Matters page includes an explorer view which permits users to search Terms entities such as Clients, Matters, Groups, and Placeholders.
- Users can switch between the explorer view and the default Client and Matters page in order to filter and sort items as needed.
- In the client matter lookup, the client and/or matter status is displayed following the client and/or matter name.
- Terms users can view and filter by client matter status on all Terms pages by selecting the Status column.
- Summary notes for documents can be enabled in Administration-System-Terms for the purpose of displaying the notes in the document viewer sidebar. In addition to viewing existing summary notes, users can add a note for a term.
- Users can add a new summary note by selecting the add new note link in the Notes tab which opens a lightbox for selection of the Term Category, adding a title, adding user groups, and adding the text of the note.
- To prevent potential errors, a warning is displayed when users upload a document and associate it to a closed client or matter.
- Client Status and Matter Status can be selected as filters on the Client and Matters, Term Data, and Terms Review grids.
- Users can filter for 'Term Document' on the Terms tab of the entity profile to easily identify the document from which a term is sourced.
- The categorization dialogue lightbox can be moved to the sides of the document to help users keep context of the highlighted text to be categorized.

COMMON/API/DATA SETS ENHANCEMENTS:
- Generic data sets have an entity called Party's Related Parties which can retrieve associated entities (i.e. subsidiaries, beneficial owners, etc.) of an existing party, which allows firms the flexibility of retrieving related parties based on firm requirements.
- Attachments can now be managed via APIs. Request level attachments can also be associated with questions. This makes the API functionality consistent with the UIs.
- Lookup type grid questions can be easily defaulted from data sets using the new lookup function added to the data set.
- In the case of nested conditions or conditions with multiple operators (such as and/or), the template variables were not getting loaded correctly in the form designer. We have enhanced the functionality so that the template variables get loaded accurately.

CONFLICTS DEFECT FIXES:
- The lookup company link was displayed in the party search profile for search term types that do not support corporate trees (i.e. person, lateral hire, etc.).
- Search terms autogenerated by company matching via the party lookup from an Intake request did not display the Tree tab in the party search profile, only Detail was visible.
- In very rare cases a conflicts search could run indefinitely and cause memory issues.
- Users with view conflict search permissions were able to update non-confidential attachments.
- In rare cases when the search engine index was populating and an entity in the system was updated at the same time the index was closed, the indexing process could fail.
- In some cases parties were created from updating a conflicts search, but a corresponding activity was not created.
- Using fuzziness of more than two (e.g. SearchTerm~3) is not supported, but displayed an uninformative error message.
- In very rare cases the search results grid could be empty after results were loaded.
- An exception error was thrown when users attempted to create new parties from the update search state and the search was not linked to a matter.
- Conflict searches associated with a converted request did not retain importance flags when re-run.
- When passing a party lookup question from a request to a conflicts search, and opting to retrieve the tree automatically, the system used the existing tree on already created parties rather than retrieving the new tree from the party lookup question.
- Custom fields added to the grid columns could not be removed from the quick search configuration.
- The conversation tracking emails were truncated when opened and viewed in the Conflicts-Conversation tab.
- The corporate tree is cut off in the Party Search Profile lightbox for users with view only capabilities.
- An error occurred when users created a party with an inactive relationship from the party search profile.
- The scroll bar was not displayed after a user selected a hit type for any search term.
- An error message displayed in the mobile app when a Quick Search was run with affiliation and relationship required.
- Issues with Data Management occurred when a custom field filter was added.
- Custom field data was empty in Data Management lists.

INTAKE/FLOW DEFECT FIXES:
- If a port was specified in the Contract Express Server URL on the system configuration page (for example, http://cexpress54.domain1.local:8001/), an error message was thrown while displaying the contract express questionnaire on document generation. The system now accepts all ports specified in the server URL.
- Requests did not reload and move to the final state after passing through the client matter creation state if followed by a decision state.
- Fixed a request creation failure by non-admins for workflows that invoked an integration in the first state.
- Grid questions that included Party Lookup questions did not populate with the correct default values.
- Requests that included a required comment when canceled did not display the comment field and the request was not canceled when redirected to the Request List page.
- Entities with long names confirmed via the party lookup question on a request form did not populate into the Party Search Profile in Conflicts after passing through the create conflicts search state. Party lookup question response answers are limited to 255 characters in accordance with character limit in the Party Search Profile in Conflicts.
- Intapp Intake 2020.1 introduced a breaking change to the grid label question formatting. In previous versions, text formatted using either the formatting toolbar or the HTML source editor did not retain formatting when label questions were added to a custom grid. Now formatted text added through the formatting toolbar, or as HTML code added through the HTML source editor, will retain formatting when added, edited, or viewed in a grid. Customers who added label questions to a grid using HTML code in the toolbar will want to revise the label question in order to avoid formatting issues in new requests. The new behavior will be applied to all new lines in both new and existing requests.
- A validation error message failed to display when an invalid expression was added during workflow state creation.
- An error occurred when saving a form that included document creation due to expired document provider credentials or an incorrect server URL.
- An error message was thrown when importing a form and workflow with datasets from on-premises to cloud.
- When using either the IE or Edge browsers, forms that included several integrations were slow to load.
- Form import failed and an error message was thrown when a form included a score profile.
- The import of forms failed if attachment types on the source system were not valid to start with.
- User groups assigned to the configuration for delegation and sharing were missing when a workflow was imported into a new environment.
- When creating a request form an error message was displayed in the console if the user tried to add a condition to a question that had double quotes in the name.
- Form question answers that included a question mark were not recognized when the form question was added to the overview section.
- An error message was thrown when a workflow was imported to replace an existing workflow.
- An error message was thrown when an address type was changed for an entity in Data Management.
- New entities created after passing through the generate client matter workflow state displayed blank names in Data Management.
- Notifications that included a grid answer placeholder with a grand total and hidden columns was not sent and resulted in an error message.
- In cases where the scheduler job was running longer than the anticipated duration, users received two digest emails. The duplication issue has been resolved, but there may be a delay in receiving the daily digest email.
- Action button labels (i.e. approve, decline, etc.) in notifications were cut off for Office 365 users.
- The horizontal scrollbar did not work when users added question answers to the notification templates.
- For notifications that include several action buttons in respect to request transitions, the commas have been removed for a better user experience.

TERMS DEFECT FIXES:
- The categorization dialog displayed incorrect control options for adding term values.
- Uploaded documents that contained HTML markup did not display text correctly.
- When documents with text in two columns were categorized, the term position began outside of the text and was misaligned within the document.
- Documents uploaded and categorized using the IE 11 or Edge browser did not display the correct values in the Terms categorization dialog.

COMMON/API/DATA SET FIXES:
- When searching in lookups for numbers with leading or trailing zeros, such as Client or Matter IDs, the specific number searched was not always in the top matches retrieved.
- An error message was thrown when a workflow was imported to replace an existing workflow.
- Users that have not been given 'convert' capabilities were able to convert a request using the swagger API.
- Entity security could be assigned to inactive users via the API.
- A timeout exception error was thrown when executing a bulk matter update via the API.
- The Get Searches API returned an incorrect number of search results.
- Divided conflict searches were not deleted when running a bulk delete via the API.
- An error message was displayed when users attempted to open Swagger and login via IDM.
- An error message was thrown when an address type was changed for an entity in Data Management.
- Virtual table metadata that included unknown field filters resulted in an exception error.
Posted on Mar 30, 13:13 PDT
SERVICE IMPACT
This release may incur downtime; some users may be logged out, but those users will be able to log in back 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.2 VERSION CONTENT

CONFLICTS ENHANCEMENTS:
- New Assisted Conflicts module that leverages AI for enhanced search results analysis.

INTAKE/FLOW ENHANCEMENTS:
- When users match a client on the request form using BvD content provider, additional content such as the global ultimate parent, stock ticker symbol, legal form (private vs public), is retrieved from BvD and displayed on the request form. This content can be leveraged for auto-populating information on the form, kicking off new approvals, or showing additional questions.
This information gets passed to conflicts, and when a party gets created or updated at the end of the search process, this content is persisted on the profile for future use.
- A new module called "Rules Based Approvals" has been added to this release. For firms with complex approval requirements, the new module allows firms to better manage and standardize the approval process firm-wide, and minimize the number of approval notifications sent by the system. The intuitive interface allows users to define and maintain rules in a central place. These rules can then be triggered at an appropriate point in the request workflow. In addition, the NBI team can manually apply new rules or override existing rules per request basis to account for any exceptions to the process. Overall, the rules based approval functionality allows firms to standardize their approval process, while providing the right level of visibility to the stakeholders involved.
- A user who converts a request will be designated as the request creator, granting all request permissions to the user who completed the conversion.
- To better manage attachment type migration across systems during a form import or export, attachment types are mapped based on names rather than internal identifiers.
- To allow users greater flexibility and control over document generation, the document template name can be defined by form question answer variables which are passed to the Document Assembly Service (DAS). This allows users to quickly search and find the correct template and document, and send the generated document to their DMS system or client without having to rename it.
- Previously when a custom field was deleted, user preferences and profile pages were corrupted if the custom field was displayed on either of those pages. As of this release, when custom fields are deleted, the system removes those fields from the user preferences and data management properties maintaining data integrity. If a custom field is used in form designers, data sets, etc., then users cannot drop it until they remove references to the custom field.
- Performance improvements have been made to optimize request creation.

TERMS ENHANCEMENTS:
- Administrators can configure the overview sections for clients, matters, groups, and placeholders based on specific group preferences via the Administration-Terms-Entity interface.
- Administrators and implementers can customize client, matter, and group fields on the Terms Entity Profile configuration page.
- Firm specific custom fields for clients and matters (i.e. currency, timezone, etc.) can be displayed on the Terms client matter profile page.
- For those users assigned to multiple groups, a precedence order sort feature is available in the Terms Entity Profile interface to determine the configuration to show users.
- The Clients and Matters page includes an explorer view which permits users to search Terms entities such as Clients, Matters, Groups, and Placeholders.
- Users can switch between the explorer view and the default Client and Matters page in order to filter and sort items as needed.
- In the client matter lookup, the client and/or matter status is displayed following the client and/or matter name.
- Terms users can view and filter by client matter status on all Terms pages by selecting the Status column.
- Summary notes for documents can be enabled in Administration-System-Terms for the purpose of displaying the notes in the document viewer sidebar. In addition to viewing existing summary notes, users can add a note for a term.
- Users can add a new summary note by selecting the add new note link in the Notes tab which opens a lightbox for selection of the Term Category, adding a title, adding user groups, and adding the text of the note.
- To prevent potential errors, a warning is displayed when users upload a document and associate it to a closed client or matter.
- Client Status and Matter Status can be selected as filters on the Client and Matters, Term Data, and Terms Review grids.
- Users can filter for 'Term Document' on the Terms tab of the entity profile to easily identify the document from which a term is sourced.
- The categorization dialogue lightbox can be moved to the sides of the document to help users keep context of the highlighted text to be categorized.

COMMON/API/DATA SETS ENHANCEMENTS:
- Generic data sets have an entity called Party's Related Parties which can retrieve associated entities (i.e. subsidiaries, beneficial owners, etc.) of an existing party, which allows firms the flexibility of retrieving related parties based on firm requirements.
- Attachments can now be managed via APIs. Request level attachments can also be associated with questions. This makes the API functionality consistent with the UIs.
- Lookup type grid questions can be easily defaulted from data sets using the new lookup function added to the data set.
- In the case of nested conditions or conditions with multiple operators (such as and/or), the template variables were not getting loaded correctly in the form designer. We have enhanced the functionality so that the template variables get loaded accurately.

CONFLICTS DEFECT FIXES:
- The lookup company link was displayed in the party search profile for search term types that do not support corporate trees (i.e. person, lateral hire, etc.).
- Search terms auto generated by company matching via the party lookup from an Intake request did not display the Tree tab in the party search profile, only Detail was visible.
- In very rare cases a conflicts search could run indefinitely and cause memory issues.
- Users with view conflict search permissions were able to update non-confidential attachments.
- In rare cases when the search engine index was populating and an entity in the system was updated at the same time the index was closed, the indexing process could fail.
- In some cases parties were created from updating a conflicts search, but a corresponding activity was not created.
- Using fuzziness of more than two (e.g. SearchTerm~3) is not supported, but displayed an uninformative error message.
- In very rare cases the search results grid could be empty after results were loaded.
- An exception error was thrown when users attempted to create new parties from the update search state and the search was not linked to a matter.
- Conflict searches associated with a converted request did not retain importance flags when re-run.
- When passing a party lookup question from a request to a conflicts search, and opting to retrieve the tree automatically, the system used the existing tree on already created parties rather than retrieving the new tree from the party lookup question.
- Custom fields added to the grid columns could not be removed from the quick search configuration.
- The conversation tracking emails were truncated when opened and viewed in the Conflicts-Conversation tab.
- The corporate tree is cut off in the Party Search Profile lightbox for users with view only capabilities.
- An error occurred when users created a party with an inactive relationship from the party search profile.
- The scroll bar was not displayed after a user selected a hit type for any search term.
- An error message displayed in the mobile app when a Quick Search was run with affiliation and relationship required.
- Issues with Data Management occurred when a custom field filter was added.
- Custom field data was empty in Data Management lists.

INTAKE/FLOW DEFECT FIXES:
- If a port was specified in the Contract Express Server URL on the system configuration page (for example, http://cexpress54.domain1.local:8001/), an error message was thrown while displaying the contract express questionnaire on document generation. The system now accepts all ports specified in the server URL.
- Requests did not reload and move to the final state after passing through the client matter creation state if followed by a decision state.
- Fixed a request creation failure by non-admins for workflows that invoked an integration in the first state.
- Grid questions that included Party Lookup questions did not populate with the correct default values.
- Requests that included a required comment when canceled did not display the comment field and the request was not canceled when redirected to the Request List page.
- Entities with long names confirmed via the party lookup question on a request form did not populate into the Party Search Profile in Conflicts after passing through the create conflicts search state. Party lookup question response answers are limited to 255 characters in accordance with character limit in the Party Search Profile in Conflicts.
- Intapp Intake 2020.1 introduced a breaking change to the grid label question formatting. In previous versions, text formatted using either the formatting toolbar or the HTML source editor did not retain formatting when label questions were added to a custom grid. Now formatted text added through the formatting toolbar, or as HTML code added through the HTML source editor, will retain formatting when added, edited, or viewed in a grid. Customers who added label questions to a grid using HTML code in the toolbar will want to revise the label question in order to avoid formatting issues in new requests. The new behavior will be applied to all new lines in both new and existing requests.
- A validation error message failed to display when an invalid expression was added during workflow state creation.
- An error occurred when saving a form that included document creation due to expired document provider credentials or an incorrect server URL.
- An error message was thrown when importing a form and workflow with datasets from on-premises to cloud.
- When using either the IE or Edge browsers, forms that included several integrations were slow to load.
- Form import failed and an error message was thrown when a form included a score profile.
- The import of forms failed if attachment types on the source system were not valid to start with.
- User groups assigned to the configuration for delegation and sharing were missing when a workflow was imported into a new environment.
- When creating a request form an error message was displayed in the console if the user tried to add a condition to a question that had double quotes in the name.
- Form question answers that included a question mark were not recognized when the form question was added to the overview section.
- An error message was thrown when a workflow was imported to replace an existing workflow.
- An error message was thrown when an address type was changed for an entity in Data Management.
- New entities created after passing through the generate client matter workflow state displayed blank names in Data Management.
- Notifications that included a grid answer placeholder with a grand total and hidden columns was not sent and resulted in an error message.
- In cases where the scheduler job was running longer than the anticipated duration, users received two digest emails. The duplication issue has been resolved, but there may be a delay in receiving the daily digest email.
- Action button labels (i.e. approve, decline, etc.) in notifications were cut off for Office 365 users.
- The horizontal scrollbar did not work when users added question answers to the notification templates.
- For notifications that include several action buttons in respect to request transitions, the commas have been removed for a better user experience.

TERMS DEFECT FIXES:
- The categorization dialog displayed incorrect control options for adding term values.
- Uploaded documents that contained HTML markup did not display text correctly.
- When documents with text in two columns were categorized, the term position began outside of the text and was misaligned within the document.
- Documents uploaded and categorized using the IE 11 or Edge browser did not display the correct values in the Terms categorization dialog.

COMMON/API/DATA SET FIXES:
- When searching in lookups for numbers with leading or trailing zeros, such as Client or Matter IDs, the specific number searched was not always in the top matches retrieved.
- An error message was thrown when a workflow was imported to replace an existing workflow.
- Users that have not been given 'convert' capabilities were able to convert a request using the swagger API.
- Entity security could be assigned to inactive users via the API.
- A timeout exception error was thrown when executing a bulk matter update via the API.
- The Get Searches API returned an incorrect number of search results.
- Divided conflict searches were not deleted when running a bulk delete via the API.
- An error message was displayed when users attempted to open Swagger and login via IDM.
- An error message was thrown when an address type was changed for an entity in Data Management.
- Virtual table metadata that included unknown field filters resulted in an exception error.
Posted on Mar 30, 12:45 PDT
SERVICE IMPACT
This release may incur downtime; 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.2 VERSION CONTENT

CONFLICTS ENHANCEMENTS:
- New Assisted Conflicts module that leverages AI for enhanced search results analysis.

INTAKE/FLOW ENHANCEMENTS:
- When users match a client on the request form using BvD content provider, additional content such as the global ultimate parent, stock ticker symbol, legal form (private vs public), is retrieved from BvD and displayed on the request form. This content can be leveraged for auto-populating information on the form, kicking off new approvals, or showing additional questions.
This information gets passed to conflicts, and when a party gets created or updated at the end of the search process, this content is persisted on the profile for future use.
- A new module called "Rules Based Approvals" has been added to this release. For firms with complex approval requirements, the new module allows firms to better manage and standardize the approval process firm-wide, and minimize the number of approval notifications sent by the system. The intuitive interface allows users to define and maintain rules in a central place. These rules can then be triggered at an appropriate point in the request workflow. In addition, the NBI team can manually apply new rules or override existing rules per request basis to account for any exceptions to the process. Overall, the rules based approval functionality allows firms to standardize their approval process, while providing the right level of visibility to the stakeholders involved.
- A user who converts a request will be designated as the request creator, granting all request permissions to the user who completed the conversion.
- To better manage attachment type migration across systems during a form import or export, attachment types are mapped based on names rather than internal identifiers.
- To allow users greater flexibility and control over document generation, the document template name can be defined by form question answer variables which are passed to the Document Assembly Service (DAS). This allows users to quickly search and find the correct template and document, and send the generated document to their DMS system or client without having to rename it.
- Previously when a custom field was deleted, user preferences and profile pages were corrupted if the custom field was displayed on either of those pages. As of this release, when custom fields are deleted, the system removes those fields from the user preferences and data management properties maintaining data integrity. If a custom field is used in form designers, data sets, etc., then users cannot drop it until they remove references to the custom field.
- Performance improvements have been made to optimize request creation.

TERMS ENHANCEMENTS:
- Administrators can configure the overview sections for clients, matters, groups, and placeholders based on specific group preferences via the Administration-Terms-Entity interface.
- Administrators and implementers can customize client, matter, and group fields on the Terms Entity Profile configuration page.
- Firm specific custom fields for clients and matters (i.e. currency, timezone, etc.) can be displayed on the Terms client matter profile page.
- For those users assigned to multiple groups, a precedence order sort feature is available in the Terms Entity Profile interface to determine the configuration to show users.
- The Clients and Matters page includes an explorer view which permits users to search Terms entities such as Clients, Matters, Groups, and Placeholders.
- Users can switch between the explorer view and the default Client and Matters page in order to filter and sort items as needed.
- In the client matter lookup, the client and/or matter status is displayed following the client and/or matter name.
- Terms users can view and filter by client matter status on all Terms pages by selecting the Status column.
- Summary notes for documents can be enabled in Administration-System-Terms for the purpose of displaying the notes in the document viewer sidebar. In addition to viewing existing summary notes, users can add a note for a term.
- Users can add a new summary note by selecting the add new note link in the Notes tab which opens a lightbox for selection of the Term Category, adding a title, adding user groups, and adding the text of the note.
- To prevent potential errors, a warning is displayed when users upload a document and associate it to a closed client or matter.
- Client Status and Matter Status can be selected as filters on the Client and Matters, Term Data, and Terms Review grids.
- Users can filter for 'Term Document' on the Terms tab of the entity profile to easily identify the document from which a term is sourced.
- The categorization dialogue lightbox can be moved to the sides of the document to help users keep context of the highlighted text to be categorized.

COMMON/API/DATA SETS ENHANCEMENTS:
- Generic data sets have an entity called Party's Related Parties which can retrieve associated entities (i.e. subsidiaries, beneficial owners, etc.) of an existing party, which allows firms the flexibility of retrieving related parties based on firm requirements.
- Attachments can now be managed via APIs. Request level attachments can also be associated with questions. This makes the API functionality consistent with the UIs.
- Lookup type grid questions can be easily defaulted from data sets using the new lookup function added to the data set.
- In the case of nested conditions or conditions with multiple operators (such as and/or), the template variables were not getting loaded correctly in the form designer. We have enhanced the functionality so that the template variables get loaded accurately.

CONFLICTS DEFECT FIXES:
- The lookup company link was displayed in the party search profile for search term types that do not support corporate trees (i.e. person, lateral hire, etc.).
- Search terms autogenerated by company matching via the party lookup from an Intake request did not display the Tree tab in the party search profile, only Detail was visible.
- In very rare cases a conflicts search could run indefinitely and cause memory issues.
- Users with view conflict search permissions were able to update non-confidential attachments.
- In rare cases when the search engine index was populating and an entity in the system was updated at the same time the index was closed, the indexing process could fail.
- In some cases parties were created from updating a conflicts search, but a corresponding activity was not created.
- Using fuzziness of more than two (e.g. SearchTerm~3) is not supported, but displayed an uninformative error message.
- In very rare cases the search results grid could be empty after results were loaded.
- An exception error was thrown when users attempted to create new parties from the update search state and the search was not linked to a matter.
- Conflict searches associated with a converted request did not retain importance flags when re-run.
- When passing a party lookup question from a request to a conflicts search, and opting to retrieve the tree automatically, the system used the existing tree on already created parties rather than retrieving the new tree from the party lookup question.
- Custom fields added to the grid columns could not be removed from the quick search configuration.
- The conversation tracking emails were truncated when opened and viewed in the Conflicts-Conversation tab.
- The corporate tree is cut off in the Party Search Profile lightbox for users with view only capabilities.
- An error occurred when users created a party with an inactive relationship from the party search profile.
- The scroll bar was not displayed after a user selected a hit type for any search term.
- An error message displayed in the mobile app when a Quick Search was run with affiliation and relationship required.
- Issues with Data Management occurred when a custom field filter was added.
- Custom field data was empty in Data Management lists.

INTAKE/FLOW DEFECT FIXES:
- If a port was specified in the Contract Express Server URL on the system configuration page (for example, http://cexpress54.domain1.local:8001/), an error message was thrown while displaying the contract express questionnaire on document generation. The system now accepts all ports specified in the server URL.
- Requests did not reload and move to the final state after passing through the client matter creation state if followed by a decision state.
- Fixed a request creation failure by non-admins for workflows that invoked an integration in the first state.
- Grid questions that included Party Lookup questions did not populate with the correct default values.
- Requests that included a required comment when canceled did not display the comment field and the request was not canceled when redirected to the Request List page.
- Entities with long names confirmed via the party lookup question on a request form did not populate into the Party Search Profile in Conflicts after passing through the create conflicts search state. Party lookup question response answers are limited to 255 characters in accordance with character limit in the Party Search Profile in Conflicts.
- Intapp Intake 2020.1 introduced a breaking change to the grid label question formatting. In previous versions, text formatted using either the formatting toolbar or the HTML source editor did not retain formatting when label questions were added to a custom grid. Now formatted text added through the formatting toolbar, or as HTML code added through the HTML source editor, will retain formatting when added, edited, or viewed in a grid. Customers who added label questions to a grid using HTML code in the toolbar will want to revise the label question in order to avoid formatting issues in new requests. The new behavior will be applied to all new lines in both new and existing requests.
- A validation error message failed to display when an invalid expression was added during workflow state creation.
- An error occurred when saving a form that included document creation due to expired document provider credentials or an incorrect server URL.
- An error message was thrown when importing a form and workflow with datasets from on-premises to cloud.
- When using either the IE or Edge browsers, forms that included several integrations were slow to load.
- Form import failed and an error message was thrown when a form included a score profile.
- The import of forms failed if attachment types on the source system were not valid to start with.
- User groups assigned to the configuration for delegation and sharing were missing when a workflow was imported into a new environment.
- When creating a request form an error message was displayed in the console if the user tried to add a condition to a question that had double quotes in the name.
- Form question answers that included a question mark were not recognized when the form question was added to the overview section.
- An error message was thrown when a workflow was imported to replace an existing workflow.
- An error message was thrown when an address type was changed for an entity in Data Management.
- New entities created after passing through the generate client matter workflow state displayed blank names in Data Management.
- Notifications that included a grid answer placeholder with a grand total and hidden columns was not sent and resulted in an error message.
- In cases where the scheduler job was running longer than the anticipated duration, users received two digest emails. The duplication issue has been resolved, but there may be a delay in receiving the daily digest email.
- Action button labels (i.e. approve, decline, etc.) in notifications were cut off for Office 365 users.
- The horizontal scrollbar did not work when users added question answers to the notification templates.
- For notifications that include several action buttons in respect to request transitions, the commas have been removed for a better user experience.

TERMS DEFECT FIXES:
- The categorization dialog displayed incorrect control options for adding term values.
- Uploaded documents that contained HTML markup did not display text correctly.
- When documents with text in two columns were categorized, the term position began outside of the text and was misaligned within the document.
- Documents uploaded and categorized using the IE 11 or Edge browser did not display the correct values in the Terms categorization dialog.

COMMON/API/DATA SET FIXES:
- When searching in lookups for numbers with leading or trailing zeros, such as Client or Matter IDs, the specific number searched was not always in the top matches retrieved.
- An error message was thrown when a workflow was imported to replace an existing workflow.
- Users that have not been given 'convert' capabilities were able to convert a request using the swagger API.
- Entity security could be assigned to inactive users via the API.
- A timeout exception error was thrown when executing a bulk matter update via the API.
- The Get Searches API returned an incorrect number of search results.
- Divided conflict searches were not deleted when running a bulk delete via the API.
- An error message was displayed when users attempted to open Swagger and login via IDM.
- An error message was thrown when an address type was changed for an entity in Data Management.
- Virtual table metadata that included unknown field filters resulted in an exception error.
Posted on Mar 30, 13:17 PDT
Update - We will be undergoing scheduled maintenance during this time.
Mar 14, 14:38 PDT
Scheduled - The maintenance is a zero downtime maintenance; Some users may be logged out, but those users will be able to log back in immediately while desktop users can work in offline mode. 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.
Mar 14, 12:06 PDT
SERVICE IMPACT
The maintenance will incur downtime. Some or all users will be unable to use the service for up to 4 hours.
Downtime can occur anytime after the maintenance start is announced via the status site.

IMPROVEMENTS
- Enhancements to Parties View including ability to add new Party with (+) button
Posted on Mar 19, 13:49 PDT
Past Incidents
Apr 2, 2020

No incidents reported today.

Apr 1, 2020

No incidents reported.

Mar 31, 2020
Completed - The scheduled maintenance has been completed.
Mar 31, 01:06 PDT
Scheduled - The OnePlace Platform will undergo a scheduled update.

During this time, there may be brief interruptions in connectivity to the OnePlace Platform. We recommend that you do not perform any large data imports or changes until the maintenance window is closed.

Release notes are available through the customer portal.

Components updated in the release:
Platform
Reports, Pages, Widgets
Engine - Audit
Data Entry - Bulk Entry
Outlook Office Addin
API - eMarketing
Tools - Migration

For questions, or if you require technical support please contact us at support@intapp.com.

Thanks and enjoy
OnePlace Team
Mar 26, 12:14 PDT
Completed - The scheduled maintenance has been completed.
Mar 31, 01:06 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 30, 22:12 PDT
Scheduled - The OnePlace Platform will undergo a scheduled update.

During this time, there may be brief interruptions in connectivity to the OnePlace Platform. We recommend that you do not perform any large data imports or changes until the maintenance window is closed.

Release notes are available through the customer portal.

Components updated in the release:
Platform
Reports, Pages, Widgets
Engine - Audit
Data Entry - Bulk Entry
Outlook Office Addin
API - eMarketing
Tools - Migration

For questions, or if you require technical support please contact us at support@intapp.com.

Thanks and enjoy
OnePlace Team
Mar 26, 12:14 PDT
Mar 29, 2020

No incidents reported.

Mar 28, 2020
Completed - The scheduled maintenance has been completed.
Mar 28, 15:18 PDT
Scheduled - The Intapp Infrastructure will undergo a scheduled maintenance.

During this time, processing of CDS data may be delayed by up to 4 hours. No data will be lost during this maintenance.

For questions, or if you require technical support please contact us at support@intapp.com.

Thank you!
Mar 26, 12:02 PDT
Completed - The scheduled maintenance has been completed.
Mar 28, 14:51 PDT
Scheduled - SERVICE IMPACT:
We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 25, 15:31 PDT
Completed - The scheduled maintenance has been completed.
Mar 28, 14:51 PDT
Scheduled - SERVICE IMPACT:
We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 25, 15:28 PDT
Completed - The scheduled maintenance has been completed.
Mar 28, 14:51 PDT
Scheduled - SERVICE IMPACT:
We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 25, 15:26 PDT
Completed - The scheduled maintenance has been completed.
Mar 28, 12:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 28, 08:00 PDT
Scheduled - The maintenance will incur downtime. Some or all users will be unable to use the service for up to 30 minutes. Downtime can occur anytime after the maintenance start is announced via the status site.
Mar 23, 00:51 PDT
Mar 27, 2020
Completed - The scheduled maintenance has been completed.
Mar 27, 17:49 PDT
Scheduled - SERVICE IMPACT:
We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 25, 15:24 PDT
Completed - The scheduled maintenance has been completed.
Mar 27, 17:48 PDT
Scheduled - The Intapp Infrastructure will undergo a scheduled maintenance.

During this time, processing of CDS data may be delayed by up to 4 hours. No data will be lost during this maintenance.

For questions, or if you require technical support please contact us at support@intapp.com.

Thank you!
Mar 26, 11:59 PDT
Completed - The scheduled maintenance has been completed.
Mar 27, 01:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 26, 23:00 PDT
Scheduled - The DealCloud Platform will undergo a scheduled update on Friday, March 27th, from 2:00 AM EDT - 4:00 AM EDT (6:00 AM – 8:00 AM GMT).

During this time, there may be brief interruptions in connectivity to the DealCloud Platform. We recommend that you do not perform any large data imports or changes until the maintenance window is closed.

For questions, or if you require technical support please contact us at support@dealcloud.com.

Thank you!
The DealCloud Support Team
Mar 25, 14:15 PDT
Mar 25, 2020

No incidents reported.

Mar 24, 2020
Resolved - We have resolved the incident.
Mar 24, 11:55 PDT
Monitoring - We have resolved the incident but we are watching to make sure the resolution is complete
Mar 24, 10:39 PDT
Investigating - We are currently experiencing a degradation of service. Our teams are currently investigating.
Mar 24, 08:25 PDT
Mar 23, 2020
Completed - The scheduled maintenance has been completed.
Mar 23, 08:09 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 23, 02:03 PDT
Scheduled - The maintenance is a zero downtime maintenance; Some users may be logged out, but those users will be able to log back in immediately while desktop users can work in offline mode. 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.
Mar 14, 11:58 PDT
Completed - The scheduled maintenance has been completed.
Mar 23, 00:05 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 22, 23:00 PDT
Scheduled - SERVICE IMPACT
The maintenance will incur downtime. Some or all users will be unable to use the service for up to 4 hours.
Downtime can occur anytime after the maintenance start is announced via the status site.
Mar 22, 12:11 PDT
Mar 22, 2020
Completed - The scheduled maintenance has been completed.
Mar 22, 06:02 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 22, 05:00 PDT
Scheduled - SERVICE IMPACT
This maintenance may incur downtime; 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.
Mar 20, 16:48 PDT
Completed - The scheduled maintenance has been completed.
Mar 22, 06:02 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 22, 05:00 PDT
Scheduled - SERVICE IMPACT
This maintenance may incur downtime; 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.
Mar 20, 16:51 PDT
Completed - The scheduled maintenance has been completed.
Mar 22, 00:48 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 21, 23:00 PDT
Scheduled - SERVICE IMPACT
The maintenance will incur downtime. Some or all users will be unable to use the service for up to 4 hours.
Downtime can occur anytime after the maintenance start is announced via the status site.
Mar 21, 17:17 PDT
Completed - The scheduled maintenance has been completed.
Mar 22, 00:10 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 21, 23:00 PDT
Update - We will be undergoing scheduled maintenance during this time.
Mar 20, 16:45 PDT
Scheduled - Please note that the release content has changed to:

SERVICE IMPACT
This release may incur downtime; 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.
Mar 21, 23:00 PDT
Mar 21, 2020
Completed - The scheduled maintenance has been completed.
Mar 21, 10:01 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 21, 08:01 PDT
Scheduled - The maintenance will incur downtime. Some or all users will be unable to use the service for up to 30 minutes. Downtime can occur anytime after the maintenance start is announced via the status site.
Mar 17, 05:47 PDT
Completed - The scheduled maintenance has been completed.
Mar 21, 09:56 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 21, 08:30 PDT
Scheduled - SERVICE IMPACT
This release may incur downtime; 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.120 VERSION CONTENT

CONFLICTS IMPROVEMENTS
- Client descriptions can be included in the conflicts report.

INTAKE/FLOW IMPROVEMENTS
- No updates to Intake functionality.

TERMS IMPROVEMENTS
- No updates to Terms functionality.

COMMON/API/DATA SETS DEFECT FIXES
- No updates to functionality.

CONFLICTS DEFECT FIXES
- Conflict searches associated with a converted request did not retain importance flags when re-run.
- An error occurred when users created a party with an inactive relationship from the party search profile.

INTAKE/FLOW DEFECT FIXES
- The import of forms failed if attachment types on the source system were not valid to start with.
- Action button labels (i.e. approve, decline, etc.) in notifications got cut off for Office 365 users.

TERMS DEFECT FIXES
- No updates to Terms functionality.
Mar 16, 09:46 PDT
Completed - The scheduled maintenance has been completed.
Mar 21, 08:24 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 21, 08:03 PDT
Scheduled - SERVICE IMPACT: We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 18, 16:57 PDT
Completed - The scheduled maintenance has been completed.
Mar 21, 08:24 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 21, 08:01 PDT
Scheduled - SERVICE IMPACT: We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 18, 16:52 PDT
Completed - The scheduled maintenance has been completed.
Mar 21, 08:24 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 21, 08:00 PDT
Scheduled - SERVICE IMPACT: We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 18, 16:55 PDT
Mar 20, 2020
Completed - The scheduled maintenance has been completed.
Mar 20, 06:23 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 20, 05:35 PDT
Scheduled - SERVICE IMPACT
This release may incur downtime; some users may be logged out, but those users will be able to log in back 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.120 VERSION CONTENT

CONFLICTS IMPROVEMENTS
- Client descriptions can be included in the conflicts report.

INTAKE/FLOW IMPROVEMENTS
- No updates to Intake functionality.

TERMS IMPROVEMENTS
- No updates to Terms functionality.

COMMON/API/DATA SETS DEFECT FIXES
- No updates to functionality.

CONFLICTS DEFECT FIXES
- Conflict searches associated with a converted request did not retain importance flags when re-run.
- An error occurred when users created a party with an inactive relationship from the party search profile.

INTAKE/FLOW DEFECT FIXES
- The import of forms failed if attachment types on the source system were not valid to start with.
- Action button labels (i.e. approve, decline, etc.) in notifications got cut off for Office 365 users.

TERMS DEFECT FIXES
- No updates to Terms functionality.
Mar 16, 09:42 PDT
Completed - The scheduled maintenance has been completed.
Mar 20, 05:33 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 20, 04:59 PDT
Scheduled - SERVICE IMPACT:
We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
Mar 18, 16:48 PDT
Mar 19, 2020
Completed - The scheduled maintenance has been completed.
Mar 19, 12:18 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 19, 12:00 PDT
Scheduled - SERVICE IMPACT:
We will be undergoing scheduled maintenance during this time. The maintenance will not affect any user.
2020.03.19 RELEASE CONTENT:
Defect Fix:
Watchlist: Removed contextual alias data from alias field for EU list
Mar 16, 16:41 PDT