I'm trying to log some information in a webservice extension when a file changes state. I subscribe to the Pre and Post events of UpdateFileLifecycleStateEvents. In most scenarios I can get exactly what I need and things are working well. I've run into a case where a vault has a property that requires a value. When the user tries to move a file from Review to Released and the property does not have a value, the Pre and Post events fire and look like the file has successfully transitioned to Released. After those events fire the Vault Client throws a dialog stating that the file cannot change to the specified state due to errors or restrictions. The restriction shown is "Some properties do not match pre-defined criteria of transition from 'For Review' to 'Released'; please ensure all properties are in compliance."
It seems to me that the Pre/Post for the UpdateFileLifecycleStateEvents shouldn't be firing in this case as the file doesn't actually change state. Am I missing something here?
Thanks.
Tom.
Solved! Go to Solution.
Solved by wayne.brill. Go to Solution.
Hi Tom,
I am able to recreate this behavior and logged a ticket with Vault Engineering. I am not finding a work around for it.
Thanks,
Wayne
Can't find what you're looking for? Ask the community or share your knowledge.