Proof decision data

[JustinWa2]

Hello!

Need a report that shows a proof name, the approvers on each stage, and the time it took for them to approve the proof.  I've tried writing a couple of different document version reports, but I can't seem to find a way to capture the time it took to approve.  Any suggestions?

Thanks!

[MoniqueEvans]

If you make a document version report you can use the following code to show the wait time in business days for proofs still pending. If you want to show the wait time for proofs with decisions you'll need to modify the equation slightly so that the two dates are entry date vs decision date instead of entry date vs today.

displayname=Wait Time
shortview=true
textmode=true
valueexpression=CONCAT(ROUND(WEEKDAYDIFF({entryDate},$$TODAY),1)," Days")
valueformat=HTML

[JustinWa2]

This is awesome, thanks so much!

I can't seem to figure out how to write the code to try the entry vs decision date.  Would you know how that should be written?

[nryan2]

I' curious how you got the SOCD icons to display in the "Preview" column. Is that a standard field?

[MoniqueEvans]

No, we were proofing a screenshot of the buttons to have an example for a quiz question so that's the asset needed for approval.

[Madalyn_Destafney]

Hi @MoniqueEvans! I can't figure out how to adjust this text mode to use in a column in a proof approval report. I've tried documentVersion:entry date and other variations. Would really like this in a proof approval report given that's where my other proof approval reports are. Thoughts?
I've looked around XL and can't find anything on this.

[Madalyn_Destafney]

@MoniqueEvans just kidding, I figured it out : ) 
If anyone wants to have a column showing wait time on a proof approval report, not a document version report, it's:

displayname=Wait Time
shortview=true
valueexpression=CONCAT(ROUND(WEEKDAYDIFF({proofCreationDate},$$TODAY),1)," Days")
valueformat=HTML

[kautuk_sahni]

@JustinWa2 just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!