{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/dec367a4489d47e3bc990d1910245edc\" frameborder=\"0\" width=\"1838\" height=\"1378\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1378,"width":1838,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1378,"thumbnail_width":1838,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/dec367a4489d47e3bc990d1910245edc-469e5fee97a6f125.gif","duration":528.519,"title":"V6 Training - Processing Signature Media Tasks and Proofs","description":"In this video, I walk you through the process of handling a signature media task when it gets submitted, particularly focusing on a scenario where we're adding it to an existing ticket. I demonstrate how to create a signature media folder in ZIFlow and match it with our Google Drive setup, ensuring consistency across platforms. Additionally, I show you how to manually create both the task and the proof, as this is not an automated submission. Please note that this process is essential for maintaining our workflow, especially when a new request doesn't include a signature media task. I encourage you to familiarize yourself with these steps for future reference."}