Delete Async (POST)

Delete multiple historic decision instances asynchronously (batch). At least historicDecisionInstanceIds or historicDecisionInstanceQuery has to be provided. If both are provided then all instances matching query criterion and instances from the list will be deleted.

Method

POST /history/decision-instance/delete

Parameters

Request Body

A JSON object with the following properties:

Name Description
historicDecisionInstanceIds A list historic decision instance ids to delete.
historicDecisionInstanceQuery A historic decision instance query like the request body described by POST /history/decision-instance .
deleteReason A string with delete reason.

Response Body

A JSON object corresponding to the Batch interface in the engine. Its properties are as follows:

Name Value Description
id String The id of the batch.
type String The type of the batch. See the User Guide for more information about batch types.
totalJobs Number The total jobs of a batch is the number of batch execution jobs required to complete the batch.
jobsCreated Number The number of batch execution jobs already created by the seed job.
batchJobsPerSeed Number The number of batch execution jobs created per seed job invocation. The batch seed job is invoked until it created all batch execution jobs required by the batch (see totalJobs property).
invocationsPerBatchJob Number Every batch execution job invokes the command executed by the batch invocationsPerBatchJob times. E.g., for a decision instance deletion batch this specifies the number of decision instances which are deleted per batch execution job.
seedJobDefinitionId String The job definition id for the seed jobs of this batch.
batchJobDefinitionId String The job definition id for the batch execution jobs of this batch.
suspended Boolean Indicates wheter this batch is suspened or not.
tenantId String The tenant id of the batch.

Response Codes

Code Media type Description
200 application/json Request successful.
400 application/json Returned if some of the query parameters are invalid, i.e. neither historicDecisionInstanceIds, nor historicDecisionInstanceQuery is present. See the Introduction for the error response format.

Example

Request

POST /history/decision-instance/delete

Request Body:

{
  "historicDecisionInstanceIds": ["aDecision","secondDecision"],
  "historicDecisionInstanceQuery": {
    "decisionDefinitionKey": "a-definition-key"
  },
  "deleteReason": "a delete reason"
}

Response

Status 200 OK

{
  "id": "aBatchId",
  "type": "aBatchType",
  "totalJobs": 10,
  "batchJobsPerSeed": 100,
  "jobsCreated": 10,
  "invocationsPerBatchJob": 1,
  "seedJobDefinitionId": "aSeedJobDefinitionId",
  "monitorJobDefinitionId": "aMonitorJobDefinitionId",
  "batchJobDefinitionId": "aBatchJobDefinitionId",
  "suspened": false,
  "tenantId": null
}

On this Page: