Update vizualisation files in thin client

[johan.degreef]

What access do users need to send a command to "update visualization file" form the thin client? Now they get permission denied. Now they have 1 role "document consumer"

side question: Why are so many documents failing to have a dwf file ready to view in the thin client? Our job processor executes them, but only 50% are well generated, and the other half fail.

[gandhey]

Hello,

To run 'Update Visualization' command from thin client for a file (to add the job) - user needs atleast 'Document Editor (level 1)' role.

For the side question - are you saying the DWFs are generated but cannot be viewed properly in thin client OR the DWF creation jobs are failing ?

Regards,

Yogeshwar

(Vault team)

[gandhey]

Hello,

To run 'Update Visualization' command from thin client for a file (to add the job) - user needs at least 'Document Editor (level 1)' role.

For the side question - are you saying the DWFs are generated but cannot be viewed properly in thin client OR the DWF creation jobs are failing ?

Regards,

Yogeshwar

(Vault team)

[johan.degreef]

---

@gandhey wrote:

the DWF creation jobs are failing ?

(Vault team)

---

The last one

[Gabriel_Watson]

DWF generation causes a lot of issues indeed. I've always had to follow up the Job Queue and see what failed and how, then in some cases fix them and re-submit, or give up if they 100% will fail (usually for very large assemblies/drawings).

As you will learn, a lot of the times you can understand what you can do to fix the DWF export before re-submitting, all based on the error message at the Job Queue. I start by attempting a "Synchronize Properties" and "Update File References" on those files that failed to get the DWF, then if I have to (many times) I have to "show hidden files" and delete an existing/older or conflicting DWF already in the folder, to re-submit the task again and succeed.... lastly, you may need to request the users to check in their file again into Vault in some cases too, so the DWF generation won't fail. If you post here your Job Queue error I can probably give you more focused advice on what to try.

[elisa.farioli]

Hello,

I have the same issue, I've just modified the role for the viewer group with 'Document Editor (level 1)' .

They still cannot run "update visualisation" on Vault thin client 2022.

Any other idea?

thank you

[gandhey]

Hello @elisa.farioli ,

Can you check if the same user can initiate the DWF creation job from the Vault thick client ?

I am trying with 2022.3.1 stream and with a user just having document editor 1 role and able to initiate the DWF creation from thick and thin client.

Regards,

Yogeshwar

(Vault team)

[elisa.farioli]

Hi Gandhey,

thank you for your reply.

I logged into Vault pro 2022.2.2 and I found out the error. 

The user did not have access to the ipj, so I granted it.

Now he is able to update visualisation into Vault thin client.

Thank you

Kind regards

Elisa

[Frank.HallWQLC5]

Hey All,

I just want to address the comment above: "To run 'Update Visualization' command from thin client for a file (to add the job) - user needs at least 'Document Editor (level 1)' role."

A more cautious approach is only adding the 1 permission needed to "Update Visualization", rather than adding all the extra permissions that come with Document Editor (level 1). The steps to do this are shown below. In case the screengrab isn't available years from now: Goto Tools -> Administration -> Global Settings -> Manage Roles. Since the default Roles can't be edited, create a new Role and then add the Permission "Job Queue Add". This new role will then need to be assigned to the User(s) or Group(s) that would normally access the Thin Client (Vault online) with Read-only access.