Run Disposition Sweep for an Auto Destroy action

Disposition Sweep for an auto destroy action will immediately delete those records marked for Auto Destroy.

NOTE  When running a disposition sweep for an auto destroy action on a multi-filed record, the record will be unfiled from the container targeted by the sweep but will remain in other containers not associated with the sweep.

In order for this type of sweep to complete successfully, you must have already tagged records with an Auto Destroy action. For more information, see Add an action.

You must have also updated the legacy disposition schedule to use Auto Destroy by changing the Phase properties. See Modify a disposition schedule.

To run Disposition Sweep

Run Disposition Sweep with the -autodelete parameter from the RecordsManagerSweep folder on the machine where you installed the Disposition Sweep component. Use the following methods to run Disposition Sweep, depending on your operating system type:

You can verify whether Disposition Sweep ran successfully by viewing the error log file created in the RecordsManagerSweep folder. If the error file is empty, the Disposition Sweep process ran successfully. Otherwise, the file will contain errors that you can use to troubleshoot the problem.

To stop Disposition Sweep

To stop Disposition Sweep, add the -stop parameter:

A message displays when the Disposition Sweep processes have stopped.

Checking the log file

After Disposition Sweep runs, you might want to check the activity log you configured. The log file shows when various types of processes start and end and lists entities processed and updated. If there are errors, a trace is included. What is not included though is a list of records that failed, since Content Engine is unable to supply the information.