Latest Approver Property

[chris.downing]

Autodesk Vault has an 'Initial Approver' property but it would be more useful to have a 'Latest Approver' property, this could be used to map to the 'Checked By' or 'Approved By' properties in Inventor and used in title blocks and revision tables.  

I understand the 'Created By' property gets populated by the person who releases the file but then if using the Job Processor the Job Processor's user account name will override the 'Created By' property, this is why a 'Latest Approver' will be much more useful that the 'Created By' property. 

[ihayesjr]

@chris.downing 

You have the ability to create this custom property inside of Inventor, use a formula in Inventor to get the value from the "Checked by" or "Approved by" properties. Have you tried doing this?

[chris.downing]

@ihayesjr Thanks for the response. Yes i understand I can create custom properties but they would have to be populated manually or mapped to/from Inventor iProperties.  What I would like is a property that Vault automatically populates, you can see that Vault has a property ‘Initial Approver’ which automatically assigns the Vault username of the Approver in its value, it would more useful to have the latest approver user name not the initial approver username as the initial approver is only relevant for the first release. I hope my explanation helps. 

[Tim_Kreutzer]

Maybe a more flexible (but also more complex / harder to implement) solution would be the possibility to create new system properties, or rather "administrative properties" as an in-between of system and user properties? 

I am thinking of properties to which administrators can apply some kind of server sided rule  set on state change, or maybe a job, but which can not be  edited by users.

[RajSchmidt]

Chris,

I fully agree with you that we need this kind of property. It only gets complicated if you look at different companies with different needs:

• some want the last approver
• some want the person who initiated the change (i.e. the user who moved the document from Approved to WiP and thereby created the latest revision)
• some want the person who last modified (checked in) the document.

And for all these cases you need the timestamp as well. And this covers only a simple workflow.

Actually you have all this data already: It is attached not to the document but to the document’s versions (in the History tab). You could solve this with a custom job. At a transition you transfer the necessary data from the appropriate version into a field of the document.

Regards

[YounesYammouri]

@chris.downing , @RajSchmidt and @Tim_Kreutzer does the following idea address the exact need you have?

https://forums.autodesk.com/t5/vault-ideas/latest-released-date-property/idi-p/8005459

if yes this is already accepted idea and encourage you to join the Vault feedback community, try the current Vault alpha version posted (run Vault in Browser) and give us feedback.

Thanks

Younes 

[chris.downing]

Hi @YounesYammouri many thanks for your help but I'm afraid not, although it is similar. As well as the latest release date we need the 'Latest Approver' to go with the date. In my opinion and 20 years experience working in the engineering industry, this is far more relevent than 'Initial Approver'. 

Initial Approver

[YounesYammouri]

@chris.downing please give the Vault alpha in the Vault feedback community a try, you might be surprised what is available as properties maybe "Latest Approver" and "Latest Release Date" 🙂 and give us your feedback. 

https://feedback.autodesk.com/welcome/Vault

Best regars

Younes

[chris.downing]

will have a look now thanks @YounesYammouri 😀

[chris.downing]

This is perfect @YounesYammouri exactly what's needed, thanks!

[YounesYammouri]

This is implemented and available with Autodesk Vault 2022 Release.

[Marcin.Szklarek]

Hi!

Let me dwell on that is Latest Release Date working the same way ?

It seems it gests stuck in job processor when tried to map with date in title block.

[Senthil_Kumar]

Hi All,

I am reviving this topic since we got a new requirement now. Customer has 2 Release states. Pre-Release and Final-Release. 

File is changed to Pre-Release by User 1
Then changed to Final-Release by User 2

According to your workflow which value we should take for this property and why?

Option 1 – USER 1
Option 2 – USER 2

Please provide your input and if you can provide some explanation on why, it is highly appreciated. Thank you so much

[RajSchmidt]

Good morning @Senthil_Kumar , I would vote for User 2. After all, he is the one who gives the final “Go”.

[Senthil_Kumar]

Good morning @RajSchmidt . Thanks a lot for your feedback. Appreciate that.

[Senthil_Kumar]

@chris.downing  Do you have any preference on this? Appreciate your input. Thanks a lot.