Run Disposition

The Run Disposition tool permanently removes records that have been marked for destruction and, when you choose, recreates a shortcut to a surviving copy in supported repositories so staff can still reach the retained document.

Before you begin

• Confirm every record you expect to purge is already flagged for destruction (for example with the “Mark for Destruction” metadata). Only flagged items are brought into the queue.
• If you plan to leave shortcuts behind, make sure the records carry a Document Stream Hash value; the tool relies on that field to locate the retained duplicate.

Open the tool

From the main window, go to Records Management → Run Disposition. The panel opens near the bottom of the workspace with the current queue loaded automatically.

Review the queue

• The panel immediately loads all eligible records and shows a total count at the top. The Run button stays disabled until the list finishes loading so you don’t start a run prematurely.
• Items without a source location or file path are skipped during processing, so check the underlying records if you notice the total shrinking unexpectedly.

Start the disposition run

1. Tick Leave shortcut to retained duplicate object if you want the system to re-create shortcuts for any surviving copies (supported for SharePoint and shared-drive connections).
2. Click Run. The button asks for confirmation before it begins, then switches to a cancel icon to show the process is underway.
3. Each record is removed from its external repository and from the AgileIM catalogue. Shortcuts are created only when a matching, non-disposed duplicate exists.

Monitor progress or cancel

• A progress bar tracks how many items have been completed out of the total, updating automatically as the run advances.
• To stop the run, click the cancel icon. The remaining tasks halt, the list reloads, and you can review or restart later.
• When everything finishes successfully, the panel closes on its own, signaling the cycle is complete.

Troubleshooting

• No items appear: Confirm the records are still flagged for destruction; only those metadata values trigger inclusion in the queue.
• Shortcuts weren’t created: Verify the originals had a Document Stream Hash and that a matching retained copy exists; without those details, the shortcut option is skipped.
• Some records remain undeleted: Check that each record’s source and path are populated. Items missing this information are bypassed during the run.