Skip to end of banner
Go to start of banner

Bulk Entity Action API

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Background

In portal file browsers, to delete or otherwise update an entity, you must first select the target entity,. From inside a project or folder, there is no quick and convenient way to delete/update multiple files and subfolders, so the aim is to provide a way to bulk select files from within the files browser then select a bulk action to perform on those selected.  We introduce a new set of services to provide the mechanism for performing and tracking these jobs. We intend to interface with the already present job tracking widget, which may then be extended for other uses on the portal such as table query tracking.

Object Model

The new classes are:

Request

BulkRequest.uxf

Response

BulkResponse.uxf

Web Services

ActionURIMethodRequest BodyResponse BodyAuthorization
Bulk Update/entity/bulk/update/async/startPOSTBulkUpdateRequestAsyncJobIdACCESS_TYPE.UPDATE on each entity in the passed entityList
Get Update Results/entity/bulk/update/async/get/{asyncToken}GET BulkUpdateResponse

Asynchronously get the results of an updateEntities request started with POST /updateEntities/async/start

Note: When the result is not ready yet, this method will return a status code of 202 (ACCEPTED) and the response body will be a AsynchronousJobStatus object.

Bulk Delete/entity/bulk/delete/async/startPOSTBulkDeleteRequestAsyncJobId ACCESS_TYPE.DELETE on each entity in the passed entityList
Get Delete Results/entity/bulk/delete/async/get/{asyncToken}GET BulkDeleteResponse

Asynchronously get the results of a deleteEntities request started with POST /deleteEntities/async/start

Note: When the result is not ready yet, this method will return a status code of 202 (ACCEPTED) and the response body will be a AsynchronousJobStatus object.

Discussion

  • The web services follow the pattern established by many async table functions in their http method and their URI.
  • The name and structure of the response has had comparably less review than the response.
  • It is currently under investigation whether whoever requests the move operation also requires ACCESS_TYPE.UPDATE or other on the parentId in question.

 

  • No labels