Vault Professional 2026
Visualization files - essentially hidden DWFs - are generated by Vault either using job processor or locally.
Once Vault assigns them a category, usually something like 'base', I guess usually users don't care since the file is hidden anyway, they cannot be assigned another category using Vault UI. These files cannot be selected in the form where you change category.
My question is why Vault is designed like that? What was the reasoning behind such decision.
I'm attempting to implement a mechanism that would assign the DWF file the same category as its parent file. At the moment I realize that the only potential way to do it is via a custom job processor of some sort, because via API I'm able to change category of the hidden visualization file. And its even more tricky because I need to foresee a scenario where user changes category of an existing file, which would have to trigger reassignment of category of its DWF as well. But I started to question myself whether it actually make any sense to do it, maybe there's some solid reasoning why this is normally not possible in Vault and instead I should challenge my assignment.
