<?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/c7c729f408f04cc8857468daa6767746&quot; frameborder=&quot;0&quot; width=&quot;2226&quot; height=&quot;1669&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1669</height><width>2226</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1669</thumbnail_height><thumbnail_width>2226</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c7c729f408f04cc8857468daa6767746-67d05f978397fc1b.gif</thumbnail_url><duration>920.7217</duration><title>Exploring Variants in Scroll Document &amp;amp; Scroll Versions</title><description>In this video, I explored how the variant feature works in SQL documents and SQL versions, focusing on the concept of managing documentation for different product variants efficiently. I discussed how to use attributes to define variants based on customer needs, such as operating systems, and how to structure a common page tree in Confluence to streamline documentation efforts. I also compared the functionality of ScrollVersions and ScrollDocuments, highlighting the differences in metadata management and variant definitions. I encourage you to consider how these features can simplify your documentation process and enhance user experience by ensuring that relevant content is easily accessible. Please review the examples provided and think about how you can apply these concepts in your own work.</description></oembed>