<?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/23c15a3356914b02a311c1f9ea42ea80&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/23c15a3356914b02a311c1f9ea42ea80-d4745693aeb5c1eb.gif</thumbnail_url><duration>124.779</duration><title>CxPlanner: Logic within Custom Fields for tasks</title><description>This Loom shows how to use advanced options for custom fields to bind fields together on tasks in CXPlan. Thomas creates example tasks such as Thomas A1 and Thomas B1 and demonstrates dropdown-based logic for custom fields like Priority (critical, medium, low) and Task type (Issue, IFI, Observation, Note). When Priority is set to critical, additional options appear to mark whether the PMO has been contacted. When Task type is set to Issue, options appear for issue origin, and when set to IFI, fields for the IFI and an IFI deadline appear, while Observation shows no additional fields.</description></oembed>