

Relativity provides you with several different options for installing applications. You can:
You can add applications across multiple workspaces by installing them to the Application Library. You can do this by installing applications as external files or pushing them from a single workspace.
If you're a RelativityOne customer, and you wish to install an application from an external file to the Application Library, contact Support before doing so, as your application may require agent configuration or other infrastructure components.
When you want to add any application in a workspace to the Application Library, you can use Push To Library available on the detail view of an application. You can then install the application to workspaces throughout your Relativity environment. In Relativity, confirm that you have the appropriate system admin permissions to install an application. For more information, see Workspace security.
You override any existing applications with the same GUID when you push an application from a workspace to the library.
To install an application from the Application Library to one or more workspaces, perform the following steps:
Once installation is complete, navigate to any of the workspaces you selected, select the Relativity Applications tab, and verify that the application was installed.
You can install applications to workspaces from the Application Library tab or by importing an external application file.
When you install an application, all components are public regardless of the permissions that you assign to them in your application. The ADS framework ignores any permissions or security assigned to a component added to an application during deployment in a workspace.
If you added the application to the Application Library, you can install it to the current workspace without importing an external file to Relativity. In Relativity, confirm that you have the appropriate system admin permissions to install an application. For more information, see Workspace security.
Use the following procedure to install an application from the Application Library:
You can install an application to the current workspace by importing an external file if the application has not been added to the Application Library tab. Relativity automatically stores shared components the application uses in the Application Library and overwrites any lower versions. Shared components may include event handlers, scripts, custom pages, mass operations, or agents. In Relativity, confirm that you have the appropriate system admin permissions to install an application. For more information, see Workspace security.
You can also use the Application Install API to import an application programmatically.
Use the following procedure to install an application from an external file:
Relativity applications may contain saved searches that use keyword, dtSearch, and Analytics indexes. When you install the application, Relativity creates the folder structure used to organize the searches in the saved search browser of the workspace. It adds the saved search to the correct folder by matching the globally unique identifier (GUID). If it does not find a match, Relativity continues to traverse the folder structure to the root before creating the required folder. Otherwise, it adds any new or updated saved searches to the existing folder with the matching GUID, even if the user has moved the folder to a new location in the saved search browser. For more information, see Customizing locked applications.
While Relativity 9 and above assigns a GUID to any saved search added to an application, older versions of Relativity do not use GUIDs to identify saved searches. You can build an application using a saved search in a template workspace created before upgrading to Relativity 9 or above. However, deploying your application in a workspace created with this template results in duplicate copies of the saved search. Since Relativity identifies saved searches by GUID, it does not recognize that the legacy search in the workspace is the same as the search in the application, so it creates a new one with the matching GUID.
In general, you install these applications following the same steps used for other applications, but you may want to complete the verification steps before you install them in a workspace. If the workspace does not contain a dtSearch or an Analytics index with the same name as the one included in the application, Relativity creates it using the system defaults. The post-installation steps require you to build the index after Relativity completes this process.
When you install an application, all saved searches are public regardless of the permissions that you assigned to them in your application or folder structure. The ADS framework ignores any permissions or security assigned to a saved search added to an application during deployment in a workspace.
You may want to complete the following verification steps before you install an application containing saved searches using dtSearch and Analytics indexes to avoid possible errors:
To install the application, follow the instructions in Installing applications from the Application Library or Installing an application from an external file to a workspace.
If your workspace already contains a dtSearch or Analytics index, Relativity automatically maps it to the saved search using the index name and type. It ignores any spaces or case differences in the index name.
If your workspace does not contain an index with a matching name or type, Relativity creates a shell for a dtSearch or Analytics index. You need to complete one of the following steps to build the index:
When you import an application, you can optionally map the fields that are similar to those in an application currently installed on the workspace. You can use mapping to avoid having multiple copies of a field that stores similar information in your workspace.
For example, you might import a new application that contains a long text field on a Document object called Email Cc, but your workspace already contains another application with a similar field on the Document object called Email Cc Addresses. Instead of two fields storing similar information, you might want all applications to use the same field for this metadata. By mapping these fields, you can avoid renaming the new field and using two different fields to store this metadata in your workspace.
Use these guidelines when mapping an application to workspace fields:
Use the following procedure to map application fields to workspace fields:
After you install an application through the Relativity Application tab, you can view the status page, which appears immediately after this process completes. The Import Status section indicates whether your installation was successful.
The Artifact Name section displays a list of all the artifacts in your application, which includes its Artifact Type, Artifact ID, and installation status. For artifacts installed without errors, the Status column displays the message Updated successfully.
For unsuccessful installations, the Import Status section indicates that your application installation failed as illustrated in the following message. The message lists the number of errors encountered during the installation. In addition, the Status column describes each error that occurred during a failed installation. For more information, see Troubleshooting application installation errors.
To export the Status section report to a .csv file, you can click the Export Status Details. You can also view status information for the installation of an application from the Application Library tab. Click on an application to display a detail view, and then click its Installed link to display the status page.
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!