Relativity ECA and Investigation is a solution designed to help legal and investigative teams assess risk and make decisions at the earliest stage of a case or investigation. With analytics and data visualizations built in, you can understand the context of your data and start uncovering the facts while culling what's irrelevant. Use the centralized dashboard to gain real-time insight as to how your analysis is progressing and a pre-built template to guide your workflow. Relativity ECA and Investigation lets you spend more time on a focused set of data, reducing costs, gaining insights sooner, and ultimately honing your strategy.
This page contains the following information:
You have the option of using the ECA and Investigation application to create an ECA case template.
To create an ECA case template:
- Create a blank workspace using the New Case Template.
For more information, see Workspaces.
- Install the Processing, Analytics, and Relativity Integration Points applications already required for ECA.
- Import the ECA and Investigation application.
Doing this creates an ECA case template, which means that you no longer have to use the application unless there are any updates to it, as provided to you in monthly product update or major release.
Beginning in Relativity 184.108.40.206, the ECA and Investigation application has been simplified to no longer include fields, views, layouts, or choices. It now only includes those items that are relevant to the ECA dashboard.
This prevents the conflicts you previously encountered when you wanted to edit any locked application components, which vastly limited your ability to use the application in workspaces on which it was already installed. Now, you can more easily use the ECA application with your ECA or custom workspace template, as there are few or no conflicts.
To use ECA and Investigation in your Relativity environment, you need the following:
- RelativityOne OR Relativity 9.4 and above
- The Processing application installed
- The Worker Manager Server configured on the Resource Pool associated with your workspace.
- The Analytics application installed
- The Integration Points application installed
- The WebAPIPath instance setting in the kCura.IntegrationPoints section configured correctly
- The ECA and Investigation Agent and Integration Points Agent(s) added and enabled
Note: Data Grid is not required to run ECA and Investigation.
The following table provides the minimum workspace security permissions required to use ECA and Investigation in both the source and destination workspaces.
Note: You also need to configure the minimum workspace security permissions for all other applications required for ECA, specifically Analytics, Integration Points, and Processing.
|Workspace||Object Security||Tab Visibility||Browsers||Admin Operations|
||Advanced & Saved Searches||
Note: Integration points is tenant-aware. This means that workspace admins within a tenancy receive an error if they attempt to push to a workspace they don't have permissions to. This error occurs when they click Run Now on the integration point they create to push documents to review.
Permission conflict scenarios
Note the following integration point permission conflicts and subsequent behavior:
Any of the following permissions are removed while you're on the Integration Point layout:
|You get an error stating, "Failed to submit integration job. Unable to retrieve Integration Point."|
|A saved search is secured from the user who last created or edited the integration point's scheduled job||The scheduled job fails and a job-level Job History Error is created with a message stating, "Job failed to due to insufficient permissions. Please ensure that you have valid export and saved search permissions."|
|A saved search is made private and the user who last created or edited the integration point's scheduled job is not the owner of the save search||The job fails and a job-level Job History Error is created with a message that states, "Job failed due to insufficient permissions. Please ensure that you have valid export and saved search permissions."|
|A saved search is made private and the user who last created or edited the integration point's scheduled job is the owner||There is no conflict, and the integration point job proceeds as normal.|
|The export permission in the source workspace is removed from the last user who last created or edited the integration point's scheduled job||The job fails and a job-level Job History Error is created with a message that states, "Job failed due to insufficient permissions. Please ensure that you have valid export and saved search permissions."|
You save an Integration Point with the Enable Scheduler field set to Yes, and before Relativity starts the scheduled Integration Point job, your Edit permission on the Document object is accidentally revoked by a system admin.
During the job, the documents being pushed aren't tagged with the Destination Workspace/Job History in the ECA (source) workspace. In this case, if you need an audit trail of the documents being pushed, you need to go to the destination workspace, filter the Documents list, and identify the scheduled job from which those documents came.
The following steps depict a standard ECA and Investigation workflow:
- Import the ECA and Investigation application into an ECA workspace.
- Discover and publish data into the ECA workspace.
- Run deduplication on your processed data through the Update Duplicate Status script.
- Include and/or exclude pieces of your data in the Documents tab based on any of the following common parameters:
- File type
- Date range
- Entity keywords
- Entity emails
- Use the ECA Dashboard to see what your data looks like with files tagged for inclusion and exclusion.
- Use Integration Points to push your refined data to review workspaces and a load file via the RDC.
The following graphic depicts the basic cycle of an ECA and Investigation project.
Note: It's recommended that you not delete your ECA (source) workspace, as doing so could cause data syncing issues.
To gain access to the ECA dashboard, you need to first import the ECA and Investigation application into a new workspace that you've created specifically for this workflow.
Note: If you are a current RelativityOne user, and you want to install or upgrade this application, you must contact the
Before importing the ECA and Investigation application, you need to also install the following applications:
- Integration Points
To import the ECA and Investigation application, perform the following steps:
- Navigate to the Relativity Applications tab.
- Click New Relativity Application in the upper left corner of the All Relativity Applications view.
- In the Application Type field, select the radio button for Select from Application Library.
- In the Choose from Application Library field, click .
- Select the ECA and Investigation application from the list of available applications, and then click Ok.
- Once Relativity loads the application, click Import to install it to your workspace.
Note: It's recommended that you don't uninstall the ECA and Investigation application from your workspace, as doing so also permanently removes all of the metadata fields that were installed with it.
Once the import is complete, you're able to access the following ECA and Investigation components:
- The ECA home dashboard
- Document dashboards
- Destination and Source workspaces
- Pivot profiles
- The Update Duplicate Status script
- An ECA-optimized processing profile
Special considerations - ECA and Field Catalog app syncing
Note the following details:
- A number of processing fields were renamed in the Field Catalog. Renamed fields will cause naming conflicts.You can address these conflicts through the standard application framework, which is to either rename the fields or modify their mapping. If you previously processed data into a field that was renamed, you will have the same data in two different fields. You can address this through a Mass Replace operation on the affected fields.
- The All Custodians field was renamed to All Custodians_Script in the ECA and Investigation application. The All Custodians_Script field is a long text field and acts as a another piece of metadata for de-duplicated documents. You should select the new All Custodians_Script field when running the Update Duplicate Status script, as this will ensure that no de-duplicated documents make it into review.