Creating a Custom Delete Job

Customers will notice that when loading records into a batch, the delete step is still triggered even if there are no records to delete. Although no records are being deleted, the Delete step does take a few minutes to complete. If you are experiencing slow performance because of the delete task, you can disable the delete task from the integration batch jobs. Once the Delete task is disabled from the integration batch, you can then create a dedicated delete job that handles deletes in the UI or through external batches. This KB article will show you how to remove the delete task from your current batch, and how to create a separate delete job to handle deleted records.

Disable Delete Task from the Job

You will first want to disable the delete task from the job that handles your loads. To do this you will want to add the PARAM_ENABLE_DELETE_PHASE to your Job Parameter. To skip the delete phase, set this parameter value to 0.

You will need to deploy the model after adding the job parameter.

Now you have removed the delete task from your load job.

Create a new Delete Job

Now in your model, you will create a new delete job.

Name the job

Assign the entities that you want to process in this job

Select Finish.

Trigger Delete Job in the UI (in the Action Set)

In your model design, navigate to the action set for the entities defined above in your job tasks.
In the Action Set, select the delete step.
Then navigate to the Action Configuration. You will want to assign the newly create delete job to the On Finish Job.

Save your model and then deploy.

How to delete via SQL

Check out this guide: https://www.semarchy.com/doc/semarchy-xdm/semig.html#publishing-record-deletions

How to delete via REST API

Check out this guide: https://www.semarchy.com/doc/semarchy-xdm/semig.html#publishing-deletions-using-rest