topic Betreff: Lifecycle change has to generate a new dwf in Vault Forum

Lifecycle change has to generate a new dwf

MarkusGreifeneder3360 — Wed, 18 Oct 2023 06:48:08 GMT

Hi!

We have some issues with dwf's showing old revision.

I understand the function of "Non Released Biased" and "Released Biases"

That's the information from A-Desk regarding this issue:

Visualization files in Vault do not match latest version in Inventor (autodesk.com)

But that means, when changing state to any released state a dwf creation has job has to be sent to job queue, in order to update the dwf to the lastest "Non Released Biased" and "Released Biases" states.

How can I configure this?

Not selectable in "Actions".

Do I have to use "Custom Job Types"? (If yes whats the name for dwf creation-job?)

Or is there a smarter way to generate a dwf-job when switching to a released state?

Betreff: Lifecycle change has to generate a new dwf

MarkusGreifeneder3360 — Wed, 18 Oct 2023 08:00:42 GMT

Hi, I already found the setting.

Transition => Actions => "Synchronize properties and update view using Job Server"

I think for correct dwf it's a must.

What's the disadvantage (except higher job prozessor traffic)

Betreff: Lifecycle change has to generate a new dwf

Gabriel_Watson — Wed, 18 Oct 2023 13:36:02 GMT

Sometimes the disadvantage is how many errors this can produce on your Job Processor queue. Things have slowly gotten a little better, especially if you select the option to retry failed jobs:
https://help.autodesk.com/view/VAULT/2024/ENU/?guid=GUID-0BA0E2A1-748B-4745-B8B0-C2CC7DB2EE5F

But keep in mind that some limitations will always exist. For example, just as 3D PDFs, DWFs will fail to generate if your assembly total size (all files involved) goes over 1 GB or so, after a (long-drawn waste of processing efforts!), and if your downstream users (like manufacturing) rely on these visualizations to work, you need to constantly monitor and remedy these failures manually, as some can keep the JP stuck in a loop.

Usually, I would pay extra attention whenever a release cycle for design teams was happening, so lots and lots of files those days would need to have DWFs generated. Definitely keep two or more JPs running in parallel if you have over a dozen designers on the team, and perhaps consider only configuring one to handle the DWFs if there aren't too many files being released (maybe... less than 200 a week, so one JP is enough and it would be the only one that could get stuck in that):
https://help.autodesk.com/view/VAULT/2024/ENU/?guid=GUID-9FE983AC-2E7C-488B-B767-0EAD42A82C5E

Other disadvantages would be security vulnerabilities (if not regularly updated, contained, and monitored), and the fact that every Windows Update might need a reboot (so you will have to make sure the JP machine and app are restarted). Oh, and of course, with more JPs you have to think of more licenses too...

Betreff: Lifecycle change has to generate a new dwf

MarkusGreifeneder3360 — Wed, 18 Oct 2023 13:46:29 GMT

Thank you for the input!

We already generate dfw with the check-in to publish to a lot of guys in the whole company via webclient.
But found to many discrepancies because ot the missing re-generation of the dwf after change state.

Because we have a lot of jobs runnning, we already have more JP, so I think the workload is balanced.
We will see how it works.