releasing files = create visualisation file without property update

[Mark_Wigan]

the goal is to have dwf files generated for released state, when files are released from within vault explorer.

we have the present option to enable the "Action" to update properties and create visualisation file (as can be defined in the lifecycle management configurations). with this enabled, the property update and dwf creation then occurrs via the job processor running on one or more users machine overnight.

this presents a problem, in that there are numerous hurdles to overcome if wishing to update properties on released files, especially across a replicated bunch of servers.

i would very much like the option to enable the dwf creation (automatically via the state change) all by itself, without having the property update happen.

[ihayesjr]

Can you explain what hurdles there are to overcome and why this is a problem in a replicated environment?

[kimhendrix]

it is a problem, becuase once a file is RELEASED the sync job will almost always fail due to restriction and the file can not be written to, so we need to simply create a DWF

[Senthil_Kumar]

Thanks for sharing your Idea. We use this forum to guide product development and help users in the best way we can, based on voting. We occasionally merge Ideas or archive old ones to keep the forum working properly - it ensures there is room for people to review new Ideas and that the most relevant and meaningful ones can gain votes. We’re archiving this Idea because it's been on the board for well over 2 years and hasn't received many votes from the community. If you want to raise it again and try to gain more support, you're welcome to do so. We’ve found that pictures and mock-ups can help get concepts across and win more votes from other users. If you have questions or see a connection between this Idea and others, let us know - Vault Product Team.