<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/d34074ecb67045f9bec9d17ee9d6ac3f&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d34074ecb67045f9bec9d17ee9d6ac3f-3a976933ebc308b2.gif</thumbnail_url><duration>335.361</duration><title>Prism 2227: Deleting Preventive Procedures</title><description>Today I shared a small demo on Prism 2227 and an epic to delete the M procedures. I walked through both single delete and drop level deletion, and explained that procedure deletion is tied to schedules, so you cannot delete a procedure if a schedule depends on it. I also showed that once you delete a schedule or unlink it, the delete is permanent and the procedure cannot be restored. This can be done only if you have manage permission and the checkbox for managing preventive procedures and schedules is enabled. Please review the delete behavior and permissions in your workspace.</description></oembed>