<?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/780a41425cb643459ff4ae9a2721258a&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/780a41425cb643459ff4ae9a2721258a-2b0a336083dd5c45.gif</thumbnail_url><duration>542.409</duration><title>Introducing the 6.3 Release of Growdata Irrigate: Key Features and Improvements</title><description>The 6.3 release of GrowData Irrigate is here! This video goes over the following new features:
1. Schedule Cancellation - Users now have the ability to cancel irrigation schedules that were previously created and queued. This provides more control and flexibility when managing irrigation plans, especially in cases where environmental or operational changes require cancelling a program before or during execution.
2. Added Configuration for Valves Offset Override for Shifts per Program - Users can now define custom valve offsets (delay time) at a per-shift level within a program. This enables finer control of irrigation timing for each valve depending on its shift context, improving scheduling precision and water management.
3. Added Pagination for Shift Valve Offsets - To improve user experience and scalability, the shift valve offsets UI now includes pagination.
This is particularly useful when dealing with a large number of valves and shifts, preventing UI clutter and improving performance.
4. Fixed a Bug with Pagination UI Component Rendering at Large Page Counts - A bug was resolved where the pagination component failed to render
when dealing with thousands of entries. The fix ensures stability and usability even when the dataset exceeds typical UI thresholds.
5. Improved Performance on Azure Maps When Displaying Many Areas - Map rendering performance has been optimized to handle large numbers of area polygons. Previously, loading too many areas would slow down the UI significantly. The update introduces optimizations such as geo-clustering, lazy loading, or throttling.
6. Area Names in Azure Maps Render After a Certain Zoom Level -To prevent clutter and improve map readability, area labels now only appear after zooming in to a defined threshold level. This improves usability when navigating large-scale views and provides clarity when examining specific zones.</description></oembed>