Item access rights are different but lifecycle-state are the same

[Anonymous]

Hello,

I've got some items in Vault Pro 2016, they all have the same lifecycle and status.

However some are locked (which is correct), some are not:

The only difference is that I imported the ones without lock with the import wizard. (the ones starting with test5_)

If I change the workflow to another state, then back to Work in Progress the Lock will be there (as I've done to test5_VM001.050).

I thought the rights only depended on lifecycle and state, does anyone know what's happening here?

Regards, Silvia

[bill.schwerin]

Security is applied when you enter a state.  

Is it possible that something like this happened?

WIP had no security when the items were imported.

WIP was then given security.

Items that entered WIP after that point, have the security setting applied to them.

[Anonymous]

I did the import again with the current security settings but I got the same result: no locked items.

[bill.schwerin · Accepted solution]

I ran some tests and then I talked to the guy that wrote this code.  

It looks like security was not required (or was too complicated) for the original import.

I can see how this will be a problem.  Can you add this to the idea station?

Please add exactly what you expect.  I'm thinking something like:

  Security associated with the last imported item version's state will be applied to the  item.  Security will  be applied to associated files.

It may still be complicated, but we should at least investigate this.

[Anonymous]

Thanks for your answer. I'll post this in the Idea's.

Do you know if the security is never applied or is this only the case when things are too complicated for the Import-wizard?

Regards, Silvia

[bill.schwerin]

I do not think that security is ever applied by Bulk Loader.  

I imagine that item import using csv or other methods behaves the same way.

The problem is that the normal code for applying life cycle security to an item can also apply security to associated files.  

Avoiding the file security would complicate the features and we may have decided to wait until it was requested.

[Jason.Courtemanche]

Hi @Anonymous,

I'm just checking in to see if you need more help with this. Did the suggestion that @bill.schwerin provided work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

Thanks,

Jason

[Jason.Courtemanche]

Hi @Anonymous,

I am checking back to see if my post or others helped you with your problem. Please add a post with how you decide to proceed and your results so other Community members may benefit.

Please hit the Accept as Solution button if a post or posts solves your issue or answers your question.

Regards,

Jason

[Anonymous · Accepted solution]

Thanks Jason, sorry for the delay, I placed this in the idea section:

https://forums.autodesk.com/t5/vault-ideas/vault-import-wizard-should-apply-security-to-items-accord...

[Jason.Courtemanche]

Hi @Anonymous,

Thank you for the follow-up, I will mark your post with the idea station link as the solution too so its easier for the community to find and show support.

Regards,

Jason