Delete Instances of a Work Type

This function should only be performed by technical administrators.
 
You cannot delete an individual matter, the correct method of ‘removing’ a matter is to set the phase to aborted/rejected depending on how the configuration has been set up. You could also create a System Closed phase and jump those matters to that phase instead.
 

Enable the Work Type Nuke Feature

To delete all work type instances, you must first enable the work type nuke feature.

  1. Select Launchpad > Admin > Features > Destructive Features.
  2. Click Enabled on the Sharedo instance nuke tool screen.

Delete All Work Type Instances

You delete work type instances in Modeller

  1. Select Launchpad > Modeller > Work types.
  2. Find the work type whose instances you wish to delete, click the burger menu and select Delete all instances.   
  3. In the warning box - enter the work type name to confirm these are the correct work type instances you are deleting. Pay attention to the warning; this action is unrecoverable.    
    This will hard delete any instances of this work type and any child instances such as tasks, instructions etc. This action is unrecoverable, and should only be done after verifying a full backup, and the system MUST NOT BE IN USE when this is executed or deadlocks will likely occur, which may result in the system being unusable.
  4. Click Confirm Deletion.
  5. In Admin, disable the Sharedo instance nuke tool feature again so that work types and their instances are not accidentally deleted.

Rebuild ShareDo indexes

After using the nuke tool, you need to rebuild the indexes to remove any ‘ghost’ rows on list views, etc., for the deleted instances. For more information, see the article Diagnostics: Manage Search Indexes.

 

Review

You have learned how to enable and disable the ShareDo instance nuke tool feature and delete work type instances.

Caution

This will hard delete any instances of this work type and any child instances such as tasks, instructions etc.
This action is unrecoverable, and should only be done after verifying a full backup, and the system MUST NOT BE IN USE when this is executed or deadlocks will likely occur, which may result in the system being unusable.