Just testing some Buzzsaw functionality. When a DWG file is synced from Vault to Buzzsaw, the Buzzsaw Windows app has the ability to generate DWF markup files, and attach this to the main file.
There are two options when saving this DWF markup:
1. DWF file is attached to the original DWG file. This markup DWF file does not seem to exisit anywhere in the Buzzsaw folder structure, but is maybe just hidden.
2. DWF file is saved as a separate file, and you can nominate which location to save it to.
Neither of these options allow the DWF file to be saved in to Vault automatically (unless you do a Add from Buzzsaw in the Vault Client).
The idea is that the design office releases a DWG, this is automatically pushed out to Buzzsaw. Buzzsaw recepient gets notification of upload (via folder notification), and views the DWG. He then marks-up the file, then this markup file is available for viewing by the design office, through Vault.
The workaround is that the design office retrieves the markups using Buzzsaw, but wanting to see if this can all be done via Vault.
Any suggestions or ideas about this workflow?
Solved! Go to Solution.
Hi - You might be able to set up a separate sync for the markup, or perhaps zip the DWG and markup and then sync that separately. I'd also suggest contacting the Buzzsaw support group directly to see if they have any other suggestions: http://autodesk.com/buzzsaw-support
Saving the DWF as a separate file will work as long as it is in the Project Sync mapping path. It will get pulled into Vault on a continuous sync, scheduled sync, or when a user selects the "sync now" button. Also, as this is performed by the job processor, it may take a few minutes for the sync to actually take place.
Please let me know if this helps.
Thanks for the suggestions Shana. I'm trying to design a workflow which has the absolute minimum of steps for the end-user - particularly on the Buzzsaw side. At this point, zipping the DWG with the markup, though simple, requires the user to go outside of Buzzsaw and manipulate the files there.
Thanks Adam, it did eventually sync up. The only downside to this is that in Buzzsaw, the separately saved markup file is not linked to the main file.