<?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/da1f96dc7e93448f961b05cde87075c6&quot; frameborder=&quot;0&quot; width=&quot;2556&quot; height=&quot;1917&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1917</height><width>2556</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1917</thumbnail_height><thumbnail_width>2556</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/da1f96dc7e93448f961b05cde87075c6-ef3371aad358af28.gif</thumbnail_url><duration>237.614</duration><title>Automate Failed Test Notices with Backflow</title><description>This Loom introduces a new Backflow feature that automatically generates communications when an assembly fails its most recent test or a location fails its most recent survey. Barak Sheehan demonstrates creating a new communication type with a trigger called failed test (for assemblies) and failed survey (for locations). The template setup includes a cadence based on the acceptance date, starting as soon as one day after acceptance and continuing until the assembly or location passes, at which point the system stops generating further notices. The template editor adds merge fields for compliance date, compliance reporter, acceptance date, and a compliance report issue table.</description></oembed>