Delete pipeline

The Delete pipeline includes event handlers that control the process for removing objects from Relativity. It contains an event handler that retrieves a list of objects dependent on the item or items selected for deletion. In addition, it provides you with the option to implement an event handler with custom logic for deletion, or to use the standard event handler for this operation provided in Relativity. For example, you might want to implement a custom event handler that adds additional items to the delete dependency list of the selected items to be deleted.

Note: The Delete pipeline initiates when any of the following actions take place:

• When deleting from a form in the main window.
• When deleting from an item list in the form.
• When deleting from a form in a pop-up.

This page contains the following information:

Delete pipeline workflow

The Delete pipeline represents the process for removing objects from Relativity. The following diagram illustrates when specific event handlers in this workflow are executed. For more information about deleting objects, see Object Manager API.

Summary of Delete pipeline event handlers

The following table lists each of the event handlers used in the Delete pipeline.

Ambient variables

replaceReadDeleteDependencyList

The replaceReadDeleteDependencyList event handler executes after deletion is requested before the deletion confirmation dialog is shown. It is used to control what information is given to the confirmation dialog in place of the stock application for all deletions, both mass and single. All of the objects are expected to be of the same artifactTypeId, which may not be the same type as the active object in the layout.

Syntax

(function(eventNames, convenienceApi) {
     var eventHandlers = {};
 
     eventHandlers[eventNames.REPLACE_READ_DELETE_DEPENDENCY_LIST] = function(workspaceId, artifactTypeId, artifactIds) {
         console.log("Inside REPLACE_READ_DELETE_DEPENDENCY_LIST event handler");
 
         return [{
            ObjectType: "OBJECT TYPE 1",
            Action: "ACTION 1",
            Count: 1,
            Connection: "CONNECTION 1",
            SecuredItems: []
        }, {
            ObjectType: "OBJECT TYPE 2",
            Action: "ACTION 2",
            Count: 2,
            Connection: "CONNECTION 2",
            SecuredItems: []
        }];
     };
 
     return eventHandlers;
 }(eventNames, convenienceApi));

Parameters

   function(workspaceId, artifactTypeId, artifactIds)

The following table lists the input parameters:

Ambient variables

Return Type

Array<DependencyObject>

An error or warning is only displayed when more than one DependencyObject is returned.

DependencyObject

{     
     ObjectType: String,         // the object type of this dependency
     Action: String,             // the action of this dependency
     Count: Number,              // the count of this dependency type
     Connection: String,         // the connection of this dependency
     SecuredItems: Array<String> // optional, a list of secured items - if set with at least one item then an error is shown, otherwise a warning is shown
}

Example Warning Message Output - no secured items

The application displays this warning after clicking Delete when there are no secured items defined in any DependencyObject:

Example Error Message Output - at least one secured item

The application displays this error after clicking Delete when there is at least one secured item defined in a DependencyObject:

{
     // ...
     SecuredItems: ["This will trigger an error instead of a warning"]
}

preDelete

The preDelete event handler executes after a deletion modal for the selected objects is confirmed. This event handler is executed before, if defined, the replaceDelete event handler is executed. Otherwise, it is executed before the stock delete application is executed.

Syntax

(function(eventNames, convenienceApi) { 
     var eventHandlers = {};
     eventHandlers[eventNames.PRE_DELETE] = function(modelData) { 
          console.log( "Inside PRE_DELETE event handler" ); 
     };
     return eventHandlers;
}(eventNames, convenienceApi));

Parameters

   function(modelData)

modelData

An object containing the information about an object (or objects) to be deleted.

{
    artifactIds: Array<Number>|Number,        // artifact identifiers to delete
    artifactTypeId: Number,                  // artifact type identifier of object to be deleted
    workspaceId: Number                     // workspace identifier
}

replaceDelete

The replaceDelete event handler executes after the preDelete event handler has finished executing. This event handler is invoked in place of the event handler in the stock application for deleting an object instance. It is used to replace the behavior for the deletion of the current object or objects in an item list. This event handler expects a return value in the form of a Promise. The workspaceId, artifactTypeId, and artifactIds can be used to determine which items should be deleted. For more information on making deletion requests, see convenienceApi.relativityHttpClient.

Syntax

(function(eventNames, convenienceApi) { 
    var eventHandlers = {};
    eventHandlers[eventNames.REPLACE_DELETE] = function(workspaceId, artifactTypeId, artifactIds, progressCallback, cancellationToken) { 
        console.log( "Inside REPLACE_DELETE event handler." );
        return convenienceApi.relativityHttpClient.delete(/*  Your delete API's URL  */);
    };
    return eventHandlers;
}(eventNames, convenienceApi));

Parameters

   function(workspaceId, artifactTypeId, artifactIds, progressCallback, cancellationToken)

The following table lists the input parameters:

{
    Message: {
        OperationsCompleted: Number,        //Number indicating progress. Should normally be in between 0 and TotalOperations.
        CompletedSteps: Number,             //Number indicating progress. Not necessary if OperationsCompleted is provided. Should normally be in between 0 and TotalSteps.
        TotalOperations: Number,                //Number indicating total number of operations.
        TotalSteps: Number,                 //Number indicating total number of steps. Not necessary if TotalOperations is provided.
        Message: String                     //Message to display on the modal.
    }
}

{
	cancel: Function	//Function used to cancel the operation. This function can be overridden.
}

postDelete

The postDelete event handler executes after the delete event handler in the stock application, or the replaceDelete event handler finishes executing. This can be used for any clean-up work needed following the deletion of one or more objects. The postDelete event handler is used for both singular and mass events, and the type of object being may be different from the type of the active object.

Syntax

(function(eventNames, convenienceApi) { 
     var eventHandlers = {};
     eventHandlers[eventNames.POST_DELETE] = function(modelData) { 
          console.log( "Inside the POST_DELETE event handler." ); 
     };
     return eventHandlers;
}(eventNames, convenienceApi));

Parameters

  function(modelData)

modelData

An object containing the information about an object (or objects) to be deleted.

{
    artifactIds: Array<Number>|Number,        // artifact identifiers to delete
    artifactTypeId: Number,                  // artifact type identifier of object to be deleted
    workspaceId: Number                     // workspace identifier
}