<?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/9441d6697d054ed688031c02e17380da&quot; frameborder=&quot;0&quot; width=&quot;2558&quot; height=&quot;1918&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1918</height><width>2558</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1918</thumbnail_height><thumbnail_width>2558</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9441d6697d054ed688031c02e17380da-9d1e51cc5ef86be6.gif</thumbnail_url><duration>419.179</duration><title>Backflow Replacement Workflow Update for Testers</title><description>This Loom provides an update to the Backflow replacement workflow in the SwiftComply tester and organization portals. On the tester side, each assembly row now includes Test or Replace buttons, and replacement reports show which assembly is being replaced, with options to correct the selection or mark the entry as not a replacement. Testers still enter new assembly details and test results as usual, then save and submit, after which the report is flagged as containing a replacement and awaits review. On the organization side, reviewers can view the old and new assemblies, choose whether to keep or remove the replaced assembly at the existing location and whether to set the replaced assembly inactive, and then accept, reject, or send back with notes for resubmission. Rejection deletes the new assembly automatically, marks the report as rejected, and does not affect the existing assembly.</description></oembed>