The previous delete operation entailed a user to wait until it gets completed. For a large number of objects, this can result in users waiting for a long period of time before being able to continue their work on the UI. Now we are pushing the deletion operation to a server job, thereby allowing the deletion to execute asynchronously and without keeping the user waiting until completion. Once deletion has been scheduled as a job, this allows the user to either navigate to a different page or close the UI altogether and come back later.

They can check the related summary information for delete jobs in the Process Overview (under Data Maintenance) in the Desktop UI after completion and the information is retained for seven days.

The current default threshold for delete jobs has been set as 100 which is configurable within the following setting:

plugin_customization.ini

#Override the default preference for the deletion job threshold
#If number of objects to be deleted are greater or equal than this threshold number then a server job would be scheduled for deletion
# ---------------------------------------------------------------------------
com.heiler.ppm.delete.core/entity.deletion.threshold=100

It is also possible to set the delete job threshold parameter at an entity level by creating an Entity Param (

entity.delete.jobThreshold

) in the repository and specifying a non-zero value. The current thresholds for Supplier Catalog and Structure Group have been set to 1 and 10 respectively.