<?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/f30b35129c39401ba80360388dcdeb6a&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/f30b35129c39401ba80360388dcdeb6a-cd07168d4e815827.gif</thumbnail_url><duration>182.308778</duration><title>4. Change Management - Running Manual Flows</title><description>In this video, I walk through the successful execution of our flow run, which has allowed us to create all necessary queues and statuses within our district instance. I also updated the environmental variable for a new status with an ID of 2250 and validated our priorities in the ITSM config IDs table. We have established a mapping where priority two is high, priority three is medium, and priority four is low. I confirmed that the priorities align correctly with our configurations, and I am leaving them as default. Please ensure to review the priorities in your own setups to maintain consistency.</description></oembed>