<?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/d9489959b15a4b8b9ff400ffa08f36aa&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/d9489959b15a4b8b9ff400ffa08f36aa-9f92951988146d12.gif</thumbnail_url><duration>330.333333</duration><title>Day 14 - Workset Police - 02 Research</title><description>In today&apos;s video, I walk you through some essential coding tips for working with worksets, including how to retrieve them by name and change their parameters. I emphasize the importance of understanding that the workset ID needs to be converted into an integer for proper functionality. I also encourage you to utilize classes to keep your code organized as it grows, especially since you&apos;ll be defining various rules based on your unique workflows. Remember, you don&apos;t have to follow my approach exactly; adapt it to fit your standards. Lastly, I suggest using AI tools to help refine your code, especially if you&apos;re a beginner.</description></oembed>