<?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/0f5365527cce4792a91f6292873ddb91&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/0f5365527cce4792a91f6292873ddb91-96737b51c679a707.gif</thumbnail_url><duration>201.323</duration><title>Map Context to Order Items Explained</title><description>This Loom introduces the “Map Context to Order Items” feature to resolve issues accessing data across different workflow contexts. It explains that workflows with multiple paths create separate contexts, such as order item context and an imposition activity context like Poster Cut and Stack Duplex, where generated filenames are not accessible to downstream order-level activities. The demo shows using the new activity with a key such as “file name” and mapping it to the plate PDF value, making it available in the order item context. This enables using the filename in activities like SFTP or creating XML nodes that require the file name.</description></oembed>