As of Vault 2019.1, users who wish to locally update a missing or outdated visualization attachment require Delete permissions to be set to Allow, using Object Based security. This is because, the attachment file is deleted and re-created with each Update.
A work around is to use Job Processor with a dedicated User who has these permissions, but that relies on the speed of the JP, and most (probably) users who are updating "on the fly" like this need to see the visualization immediately. I would like to see some sort of setting, or permission override or.... something, that will allow all users to be able to use this function, regardless of their object based permissions.
Refer to >>this thread<< for more information.
What we tried: Creating a Category just for dwf files, with a lifecycle definition containing a single state. Then setting security on that State to: Everyone - Allow on Read, Modify & Delete. This works in theory, but DWF attachments have no lifecycle state assigned, and do not allow the state to be changed, therefore these security settings will not apply.
Show More