Object Manager Fundamentals

The Object Manager API supports CRUD and query operations on Relativity Dynamic Objects (RDOs). It also includes functionality for executing mass operations, exporting large numbers of objects, progress and cancellation tokens, and interacting with event handlers. Use the information on this page to quickly learn about using the Object Manager API through .NET and the Object Manager service through REST.

This page contains the following information:

See these related pages:

Sample use cases

You can use the Object Manager service to complete a variety of tasks with Relativity objects as follows:

Required references

The Relativity.ObjectManager.SDK is a NuGet package that contains the necessary references for running Object Manager API outside an extensibility point, such as an agent, custom page, or event handler. To use the Object Manager in Relativity with extensibility points, you need to add the appropriate extensibility point package.

The Object Manager API requires references to the following libraries:

  • Relativity.Services.ServiceProxy - contains classes used to connect to Object Manager API to outside extensibility points. Use this reference if you are running your program outside of Relativity.
  • kCura.<your extensibility point> - contains helper classes used to connect to the APIs inside extensibility points. Use one or more of the following references for your extensibility point if you are running your program in Relativity:
    • kCura.EventHandler.dll
    • Relativity.CustomPages.dll
    • kCura.Agent.dll
  • Relativity.Services.Objects.DataContracts - contains classes used for basic Object Manager API functionality, such as passing data to the APIs.
  • Relativity.Services.Objects - contains classes used to establish an instance of Object Manager service.

Creating a connection to the service

Before creating a connection to the Object Manager service, determine whether your program runs as an external application, or within Relativity extensibility point, such as an agent, custom page, or event handler. If your program runs in an extensibility point, connect to the Object Manager service using the helper class in the kCura library for your extensibility point. See Required references.

var serviceManager = ConnectionHelper.Helper().GetServicesManager();
using (IObjectManager objectManager = serviceManager.CreateProxy<IObjectManager>())
{
   // Do work with the objectManager instance.
}

If your program runs outside of a Relativity extensibility point, connect to the Object Manager service using a service factory as follows:

  • In the sample code, replace the URI, username, and password with values for your environment.
  • Use the appropriate authentication for the logging in. See Login Profile Manager (.NET).
  • Verify whether you are using HTTP or HTTPS.
Uri restUri = new Uri("https://example.url/Relativity.REST/api");
Credentials credentials = new UsernamePasswordCredentials("exampleusername@relativity.com", "examplepassword");
ServiceFactorySettings settings = new ServiceFactorySettings(restUri, credentials);
ServiceFactory factory = new ServiceFactory(settings);
using (IObjectManager objectManager = factory.CreateProxy<IObjectManager>())
{
    // Do work with the objectManager instance.
}

Object Manager service in .NET versus REST

You can use the Object Manager service exposes many of the same features through .NET and REST. Review the following considerations for using the Object Manager service:

  • Use the service through .NET if you are comfortable with this technology. You can use C# or VB.Net for coding your projects.
  • Use the service through .NET if you want to access tokens for controlling the progress of long operations. The REST service does not support this functionality.
  • Use the service through REST if you are developing applications for mobile environments or if you need platform or language independence.

CRUDQ operations in Object Manager service

The Object Manager service supports the following operations:

  • Create - use the CreateAsync() method for creating single objects. It supports creating single objects and firing PreSave and PostSave event handlers. The results contain the status of every fired event handler. The Object Manager API is the method for managing and aggregating the responses for all associated event handlers.
  • Read - ReadAsync() method returns the values for specified fields on an object. The result includes all PreLoad event handler statues and an ObjectVersionToken used in overwrite protection.
  • Update - UpdateAsync() method alters specified fields. The results of this method include all statuses of any PreSave and PostSave event handlers fired.
  • Delete - The DeleteAsync() method deletes an object and its child objects, and unlinks all associations created through single or multiple object fields. To preview the changes resulting from a delete operation, make a call using the GetDependencyListAsync() method. This method fires PreCascadeDelete event handlers before PreDelete handlers. See Retrieve a list of object dependencies.
  • Query - The QueryAsync() and QuerySlimAsync() methods both retrieve objects based on a set of conditions. For more information, see Calls to QueryAsync() versus QuerySlimAsync() methods.

Calls to QueryAsync() versus QuerySlimAsync() methods

The Object Manager service exposes the Query() and QuerySlim() methods through .NET and REST. These methods take identical inputs and return a set of objects from Relativity. They differ by the amount and formatting the data returned. Review these suggestions for determining when to use each method:

  • Query() method - returns detailed information about the field-value pairs in the results. You can understand each object in its entirety without any additional context, which results in the Field definitions being repeated across each element. Use this method under the following conditions:
    • You are processing the return objects.
    • You require the GUIDs associated with each object.
    • You are using the .NET proxy then the QueryAsync endpoint is preferable.
  • QuerySlim() method - returns less information about the returned field-value pairs. For performance reasons, it is often the preferred method for consumption via HTTP. Use this method under the following conditions:
    • Your application is sensitive to payload size.
    • You want to use the query in the UI.
    • You are making REST calls then the QuerySlimAsyc endpoint is preferable.

For more information, see Object Manager (.NET) and Object Manager (REST).

Sample .NET and REST calls

Review the sample code in this section to learn about making calls through .NET and REST to endpoints on the Object Manager service. These examples use the QueryAsync endpoint to return a list of RDOs that satisfy a compound condition. The query specifies three fields on the RDOs to return. The list is sorted in descending order by name.

For reference purposes, these examples pass the fields to the API by using their associated GUID, Artifact ID, and Name. While you can use any of these identifiers, we recommend using GUIDs for application development because they are constant across all Relativity instances and support exporting applications.

.NET coding sample

  1. Create a function to hold your asynchronous calls.
  2. Create a helper function to return a service factory used to connect to Object Manager service.
  3. Construct your query and pass it to the Object Manager service.

REST coding sample

  1. Set the endpoint to make a query request. Send a POST request with a URL in the following format:
  2. <host>/{your Relativity URI}/Relativity.REST/api/Relativity.Objects/workspace/{target WorkspaceID}/object/query
  3. Add the required headers to your request. For more information, see HTTP headers or Basic REST API concepts.
    • Authorization header - this header uses Base64 encoding of your username and password in the format, which requires a colon:
    • Username:Password
    • X-CSRF-header - Leave this header blank.
    • Content-Type header - set this header to application/json.
  4. Construct the request body using a JSON object that contains your parameters.
  5. Note: The sort direction represented by 1 is descending and 0 is ascending.