Deleting an Asset
Assets (or system components) can be deleted by users that have write access and no workflow. For business users, a custom workflow can be assigned to the delete action so that the delete only occurs when the appropriate people have approved it.
To delete an asset, click on the Delete tab, or use the multi-asset drop down option when viewing the contents of a folder.
To protect assets that are dependent on certain types of assets within the system, some assets and components require extra steps before they may be deleted.
Templates:
Because templates are vital to page rendering, a template with active subscribers (i.e. configurations) cannot be deleted. To delete a template, first make sure that any dependencies have been reassigned.
Stylesheets and Blocks:
When attempting to delete a stylesheet or block, a warning message will appear whenever there are pages or other subscribing assets associated. This warning may be ignored, but it is recommended to resolve any dependencies before completing the delete action.
Folders:
When attempting to delete a folder or subfolder that is the base folder for an active target, a warning message will appear. This warning may be ignored, but it is recommended to reassign a new base folder before completing the delete action.
Targets:
Targets currently linked to templates cannot be deleted. To delete a target, first make sure that any dependencies have been reassigned.
Metadata Sets and Configuration Sets:
Metadata Sets and Configuration Sets with active subscribers cannot be deleted. To delete one of these components, first make sure that any dependencies have been reassigned.
Data Definitions:
Data Definitions that are currently selected on any page where the page is also set to USE that data definition cannot be deleted. To delete a data definition, first make sure that any dependencies have been reassigned.
Additional Notes
When deleting assets using the multi-asset delete function, dependencies will not be checked, and no warnings are given.