Sync updated lifecycle to files and items

[Chancellor.Kurre]

Currently if you change a state to be a released state the existing files in this state do not show as released files. These files only see this update after a change to another state. Our current workaround is to change the state to some temp state and back to realize the lifecycle update. A tool or option that does this without versioning the file would be useful.

[mrB_Young]

This doesn't sound right. You shouldn't have to be doing that.
Have you tried posting on the Vault Forum? And with some screenshots showing this behaviour.

[Chancellor.Kurre]

I haven't asked on the Vault forum because it has been so consistent for me. Multiple companies I work with experience something similar and it seems to show up any time I do major lifecycle work. In general, files seem to hold onto the lifecycle configuration that was present when they initially got to that state. 

[ihayesjr]

@Chancellor.Kurre 

Thank you for posting the idea, but I don't understand this request.

Can you please post a video illustrating what you are experiencing?

[vali_dobrea]

I belive this is happening also on our Vault...

We have used Autodesk Vault professional 2019 until august 2022 when we made the upgrade to 2023. Within 2023 I have made modification o the permissions for Approved state to better magage acces on groups of users that seems not to be applied to older files that were approved prior to the Vault upgrade.

Please see bellow one case  of a dwg file and previous permissions that we used while using vault 2019.

The modifications on current 2023 Vault permissions for the Approved state as seen bellow  are not applied on the the file. 

[ihayesjr]

@vali_dobrea 

What you are seeing is different than the idea. 

The idea is about the state. Your experience is about the security of the file in that state.

[Chancellor.Kurre]

@ihayesjr what @vali_dobrea has shown may have the same root cause. I am seeing this behavior as well. Whether it is permissions or another modification to that state, files are not seeing this change until they are moved to another state. 

[ihayesjr]

@Chancellor.Kurre 

That is the correct behavior. Vault will not change the existing state of the file until its state is toggled. This is required to keep property history and versioning. 

Permissions are different. Vault can change the file's permissions if the permissions in the state in the lifecycle definition are changed. However, these will depend on where it is changed in the definition is happening.

In @vali_dobrea case, the permissions are being modified at a lower level because the state is based on the Item, not the file.