You can delete any elements to which you have Write access for the element and its parent folder. When deleting a folder, you must also have Write access to all elements within the folder. For more information about Write access and ACLs assigned to elements, see Assigning and Managing Permissions for Elements

When you delete a folder or the last Java service in a folder, Designer also deletes the shared source for that folder. If you cancel the delete action, no elements (including non-Java service elements) are deleted.

You can only delete an adapter notification’s publishable document type if you delete its associated adapter notification.

When you delete an adapter notification, Designer also deletes its associated publishable document type and prompts you to indicate whether to delete the associated Broker document type.

You cannot delete a listener or connection element.

If you delete a dictionary, the dependency manager will list all flat file schemas and dictionaries that will be impacted by the deletion, and prompts you to confirm the deletion. However, it does not identify the names of the records, fields, or composites that reference the dictionary; that is your responsibility.

If you delete a publishable document type, Designer prompts you to keep or delete the associated Broker document type.

If you delete a publishable document type and Broker document type associated with a trigger or a flow service, you might break any integration solution that uses the document type.

If you delete the Broker document type, you might negatively impact any publishable document types created from that Broker document type on other Integration Servers. When the developers synchronize document types with Broker and they choose to Pull from Broker, publishable document types associated with the deleted Broker document type will be removed from their Integration Servers.